{"id":"CVE-2026-31689","aliases":["AZL-84404","BELL-CVE-2026-31689","DEBIAN-CVE-2026-31689","EUVD-2026-25886","GHSA-9qrw-cmg5-g8vq","MGASA-2026-0108","MGASA-2026-0110","OESA-2026-2581","OESA-2026-2582","ROOT-OS-DEBIAN-12-CVE-2026-31689","ROOT-OS-UBUNTU-2404-CVE-2026-31689","SUSE-SU-2026:24181-1","SUSE-SU-2026:24182-1","SUSE-SU-2026:24315-1","SUSE-SU-2026:24316-1","SUSE-SU-2026:4640-1","SUSE-SU-2026:4706-1","UBUNTU-CVE-2026-31689","USN-8567-1","USN-8574-1","USN-8574-2","USN-8574-3","USN-8595-1","USN-8595-2","USN-8595-3","USN-8596-1","USN-8606-1","USN-8607-1","USN-8608-1","USN-8609-1","USN-8619-1","USN-8665-1"],"status":"published","title":"EDAC/mc: Fix error path ordering in edac_mc_alloc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00115,"percentile":0.01532,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-476"],"published":"2026-04-27T17:34:27Z","modified":"2026-11-11T09:39:37Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.137.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.170-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.85-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.169","6.6.135","6.12.82","6.18.23","6.19.13"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.170-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.85-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.19.13-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu: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-1061.64~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1063.71~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1062.69~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1064.72~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-136.136~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1061.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-136.136.2~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1059.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1058.61~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-136.136~22.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1056.57~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-136.136"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1061.64"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1063.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1062.69"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1064.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1059.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1046.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1061.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-136.136.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1059.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1059.62.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1030.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1061.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","fixed_in":["6.8.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1033.34"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1028.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2050.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1056.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1061.64+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1063.71+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-136.136+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1064.72+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-nvidia","fixed_in":["7.0.0-1006.6"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.137.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.168-r0"},{"fixed":"6.1.170-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.81-r0"},{"fixed":"6.12.85-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":"5.19.0"},{"fixed":"6.1.169"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.135"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.82"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.23"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.13"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.170-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.85-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","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~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.19.13-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.10-1","6.18.12-1","6.18.12-1~bpo13+1","6.18.13-1","6.18.14-1","6.18.15-1","6.18.15-1~bpo13+1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18.8-1","6.18.9-1","6.18.9-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1","6.19-1~exp1","6.19.10-1","6.19.10-1~bpo13+1","6.19.11-1","6.19.11-1~bpo13+1","6.19.12-1","6.19.13-1~bpo13+1","6.19.2-1~exp1","6.19.3-1~exp1","6.19.4-1~exp1","6.19.5-1~exp1","6.19.6-1","6.19.6-2","6.19.6-2~bpo13+1","6.19.8-1","6.19.8-1~bpo13+1","6.19~rc4-1~exp1","6.19~rc5-1~exp1","6.19~rc6-1~exp1","6.19~rc7-1~exp1","6.19~rc8-1~exp1"]},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.137-1.mga9"}]}],"bundled":189},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.18-18.mga9"}]}],"bundled":189},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-90.mga9"}]}],"bundled":189},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.137-1.mga9"}]}],"bundled":189},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.1.14.152.oe2403sp1"}]}],"bundled":101},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.3.14.145.oe2403sp3"}]}],"bundled":150},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu: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.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1.159998.21.38"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"podman","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.2-160000.6.1"}]}],"bundled":479},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":479},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":479},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1.159998.21.38"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":473},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":479},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.53.1"}]}],"bundled":479},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_21","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.1"}]}],"bundled":508},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.78.1"}]}],"bundled":508},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.78.1"}]}],"bundled":508},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.78.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1.150700.17.47.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_22","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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.84.1"}]}],"bundled":508},{"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-1061.64~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","6.8.0-1057.60~22.04.1","6.8.0-1060.63~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-1063.71~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","6.8.0-1059.65~22.04.1","6.8.0-1062.69~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-1062.69~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","6.8.0-1058.65~22.04.1","6.8.0-1061.68~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-1064.72~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","6.8.0-1060.63~22.04.1","6.8.0-1063.69~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-136.136~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","6.8.0-124.124~22.04.1","6.8.0-134.134~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-1061.62~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","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~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-136.136.2~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","6.8.0-117.117.1~22.04.1","6.8.0-134.134.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-1059.62~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","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~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-1058.61~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","6.8.0-1054.55~22.04.1","6.8.0-1057.58~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-136.136~22.04.3"}]}],"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","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~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-1056.57~22.04.2"}]}],"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","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"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","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"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","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"]},{"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-1063.71"}]}],"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","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"]},{"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"}]}],"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","6.17.0-1021.21~24.04.1","6.17.0-1022.22"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"]},{"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"}]}],"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","6.8.0-1039.42"]},{"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-1064.72"}]}],"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","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"]},{"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"}]}],"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","6.17.0-1021.24~24.04.1","6.17.0-1022.25"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.67"}]}],"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","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"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","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"]},{"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"}]}],"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","6.17.0-41.41~24.04.1","6.17.0-42.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62"}]}],"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","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"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","6.8.0-117.117.1","6.8.0-134.134.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-1059.62"}]}],"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","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"]},{"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"}]}],"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","6.17.0-1031.31","6.17.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62.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","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"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","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"]},{"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"}]}],"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","6.17.0-1030.30","6.17.0-1032.32","6.17.0-1033.33"]},{"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-1058.61"}]}],"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","6.8.0-1054.55","6.8.0-1057.58"]},{"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"}]}],"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","6.17.0-1019.19~24.04.3","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.65"}]}],"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","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"]},{"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-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.8"}]}],"versions":["6.8.0-1005.5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"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","6.8.0-1032.33"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.33"}]}],"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","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1026.30"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"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","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"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","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"]},{"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"}]}],"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","6.17.0-1018.20~24.04.1","6.17.0-1019.22"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64+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","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+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-1063.71+fips2"}]}],"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","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+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-1064.72+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","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+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-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1006.6"}]}],"versions":["7.0.0-1005.5"]},{"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-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72~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","6.8.0-1060.63~22.04.1","6.8.0-1063.69~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57~22.04.2"}]}],"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","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"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","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72"}]}],"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","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.67"}]}],"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","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"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","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"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","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72+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","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2~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","6.8.0-117.117.1~22.04.1","6.8.0-134.134.1~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"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","6.8.0-117.117.1","6.8.0-134.134.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"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","6.8.0-1054.55","6.8.0-1057.58"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62~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","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62"}]}],"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","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"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","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"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","6.8.0-1032.33"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61~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","6.8.0-1054.55~22.04.1","6.8.0-1057.58~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"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","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64~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","6.8.0-1057.60~22.04.1","6.8.0-1060.63~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64+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","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+fips1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62~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","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62"}]}],"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","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62.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","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71~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","6.8.0-1059.65~22.04.1","6.8.0-1062.69~22.04.1"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71"}]}],"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","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"],"bundled":1205},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71+fips2"}]}],"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","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"],"bundled":914},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69~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","6.8.0-1058.65~22.04.1","6.8.0-1061.68~22.04.1"],"bundled":1206},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~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","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"],"bundled":1209},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.65"}]}],"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","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"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","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"],"bundled":912}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/aae95970fad2127a1bd49d8713c7cd0677dcd2d6","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/d3de72e2a2b9ee3a57734c1c068823e41a707715","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/d20e98c2df9354cc744431ad8ccbf49405b8b40f","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/87ce8ae511962e105bcb3534944208c6a9471ed9","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/75825648ce984ca4cebb28e4bd2bf8c3a7e837c5","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/51520e03e70d6c73e33ee7cbe0319767d05764fe","tags":["Patch","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31689","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-9qrw-cmg5-g8vq"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-31689","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31689.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-31689","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0108.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35459","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.131","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.132","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.133","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.134","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.135","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.136","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.137","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0110.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35460","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31512","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31516","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31518","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31532","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31533","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43262","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43503","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31400","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46190","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624181-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1222538","tags":["report"]},{"url":"https://bugzilla.suse.com/1254408","tags":["report"]},{"url":"https://bugzilla.suse.com/1258298","tags":["report"]},{"url":"https://bugzilla.suse.com/1260474","tags":["report"]},{"url":"https://bugzilla.suse.com/1263017","tags":["report"]},{"url":"https://bugzilla.suse.com/1263602","tags":["report"]},{"url":"https://bugzilla.suse.com/1263865","tags":["report"]},{"url":"https://bugzilla.suse.com/1264747","tags":["report"]},{"url":"https://bugzilla.suse.com/1264807","tags":["report"]},{"url":"https://bugzilla.suse.com/1266410","tags":["report"]},{"url":"https://bugzilla.suse.com/1266735","tags":["report"]},{"url":"https://bugzilla.suse.com/1266848","tags":["report"]},{"url":"https://bugzilla.suse.com/1267373","tags":["report"]},{"url":"https://bugzilla.suse.com/1267464","tags":["report"]},{"url":"https://bugzilla.suse.com/1267564","tags":["report"]},{"url":"https://bugzilla.suse.com/1267648","tags":["report"]},{"url":"https://bugzilla.suse.com/1267985","tags":["report"]},{"url":"https://bugzilla.suse.com/1269000","tags":["report"]},{"url":"https://bugzilla.suse.com/1269685","tags":["report"]},{"url":"https://bugzilla.suse.com/1269816","tags":["report"]},{"url":"https://bugzilla.suse.com/1271817","tags":["report"]},{"url":"https://bugzilla.suse.com/1271906","tags":["report"]},{"url":"https://bugzilla.suse.com/1272145","tags":["report"]},{"url":"https://bugzilla.suse.com/1272215","tags":["report"]},{"url":"https://bugzilla.suse.com/1272426","tags":["report"]},{"url":"https://bugzilla.suse.com/1272471","tags":["report"]},{"url":"https://bugzilla.suse.com/1272473","tags":["report"]},{"url":"https://bugzilla.suse.com/1272572","tags":["report"]},{"url":"https://bugzilla.suse.com/1272793","tags":["report"]},{"url":"https://bugzilla.suse.com/1272847","tags":["report"]},{"url":"https://bugzilla.suse.com/1272890","tags":["report"]},{"url":"https://bugzilla.suse.com/1273059","tags":["report"]},{"url":"https://bugzilla.suse.com/1273251","tags":["report"]},{"url":"https://bugzilla.suse.com/1273258","tags":["report"]},{"url":"https://bugzilla.suse.com/1273309","tags":["report"]},{"url":"https://bugzilla.suse.com/1273339","tags":["report"]},{"url":"https://bugzilla.suse.com/1273420","tags":["report"]},{"url":"https://bugzilla.suse.com/1273512","tags":["report"]},{"url":"https://bugzilla.suse.com/1273522","tags":["report"]},{"url":"https://bugzilla.suse.com/1273750","tags":["report"]},{"url":"https://bugzilla.suse.com/1273759","tags":["report"]},{"url":"https://bugzilla.suse.com/1273776","tags":["report"]},{"url":"https://bugzilla.suse.com/1273782","tags":["report"]},{"url":"https://bugzilla.suse.com/1273870","tags":["report"]},{"url":"https://bugzilla.suse.com/1273879","tags":["report"]},{"url":"https://bugzilla.suse.com/1273889","tags":["report"]},{"url":"https://bugzilla.suse.com/1273899","tags":["report"]},{"url":"https://bugzilla.suse.com/1273938","tags":["report"]},{"url":"https://bugzilla.suse.com/1273953","tags":["report"]},{"url":"https://bugzilla.suse.com/1273976","tags":["report"]},{"url":"https://bugzilla.suse.com/1273999","tags":["report"]},{"url":"https://bugzilla.suse.com/1274010","tags":["report"]},{"url":"https://bugzilla.suse.com/1274036","tags":["report"]},{"url":"https://bugzilla.suse.com/1274037","tags":["report"]},{"url":"https://bugzilla.suse.com/1274245","tags":["report"]},{"url":"https://bugzilla.suse.com/1274316","tags":["report"]},{"url":"https://bugzilla.suse.com/1274319","tags":["report"]},{"url":"https://bugzilla.suse.com/1274494","tags":["report"]},{"url":"https://bugzilla.suse.com/1274637","tags":["report"]},{"url":"https://bugzilla.suse.com/1274730","tags":["report"]},{"url":"https://bugzilla.suse.com/1274776","tags":["report"]},{"url":"https://bugzilla.suse.com/1274803","tags":["report"]},{"url":"https://bugzilla.suse.com/1274836","tags":["report"]},{"url":"https://bugzilla.suse.com/1274838","tags":["report"]},{"url":"https://bugzilla.suse.com/1274890","tags":["report"]},{"url":"https://bugzilla.suse.com/1275092","tags":["report"]},{"url":"https://bugzilla.suse.com/1275094","tags":["report"]},{"url":"https://bugzilla.suse.com/1275129","tags":["report"]},{"url":"https://bugzilla.suse.com/1275156","tags":["report"]},{"url":"https://bugzilla.suse.com/1275455","tags":["report"]},{"url":"https://bugzilla.suse.com/1275495","tags":["report"]},{"url":"https://bugzilla.suse.com/1275542","tags":["report"]},{"url":"https://bugzilla.suse.com/1275543","tags":["report"]},{"url":"https://bugzilla.suse.com/1275545","tags":["report"]},{"url":"https://bugzilla.suse.com/1275549","tags":["report"]},{"url":"https://bugzilla.suse.com/1275559","tags":["report"]},{"url":"https://bugzilla.suse.com/1275567","tags":["report"]},{"url":"https://bugzilla.suse.com/1275588","tags":["report"]},{"url":"https://bugzilla.suse.com/1275681","tags":["report"]},{"url":"https://bugzilla.suse.com/1275684","tags":["report"]},{"url":"https://bugzilla.suse.com/1275685","tags":["report"]},{"url":"https://bugzilla.suse.com/1275690","tags":["report"]},{"url":"https://bugzilla.suse.com/1275694","tags":["report"]},{"url":"https://bugzilla.suse.com/1275799","tags":["report"]},{"url":"https://bugzilla.suse.com/1275802","tags":["report"]},{"url":"https://bugzilla.suse.com/1275866","tags":["report"]},{"url":"https://bugzilla.suse.com/1275924","tags":["report"]},{"url":"https://bugzilla.suse.com/1275953","tags":["report"]},{"url":"https://bugzilla.suse.com/1275972","tags":["report"]},{"url":"https://bugzilla.suse.com/1275977","tags":["report"]},{"url":"https://bugzilla.suse.com/1275985","tags":["report"]},{"url":"https://bugzilla.suse.com/1276006","tags":["report"]},{"url":"https://bugzilla.suse.com/1276007","tags":["report"]},{"url":"https://bugzilla.suse.com/1276009","tags":["report"]},{"url":"https://bugzilla.suse.com/1276287","tags":["report"]},{"url":"https://bugzilla.suse.com/1276295","tags":["report"]},{"url":"https://bugzilla.suse.com/1276337","tags":["report"]},{"url":"https://bugzilla.suse.com/1276338","tags":["report"]},{"url":"https://bugzilla.suse.com/1276339","tags":["report"]},{"url":"https://bugzilla.suse.com/1276340","tags":["report"]},{"url":"https://bugzilla.suse.com/1276341","tags":["report"]},{"url":"https://bugzilla.suse.com/1276349","tags":["report"]},{"url":"https://bugzilla.suse.com/1276352","tags":["report"]},{"url":"https://bugzilla.suse.com/1276353","tags":["report"]},{"url":"https://bugzilla.suse.com/1276354","tags":["report"]},{"url":"https://bugzilla.suse.com/1276381","tags":["report"]},{"url":"https://bugzilla.suse.com/1276388","tags":["report"]},{"url":"https://bugzilla.suse.com/1276395","tags":["report"]},{"url":"https://bugzilla.suse.com/1276445","tags":["report"]},{"url":"https://bugzilla.suse.com/1276460","tags":["report"]},{"url":"https://bugzilla.suse.com/1276461","tags":["report"]},{"url":"https://bugzilla.suse.com/1276462","tags":["report"]},{"url":"https://bugzilla.suse.com/1276468","tags":["report"]},{"url":"https://bugzilla.suse.com/1276473","tags":["report"]},{"url":"https://bugzilla.suse.com/1276474","tags":["report"]},{"url":"https://bugzilla.suse.com/1276475","tags":["report"]},{"url":"https://bugzilla.suse.com/1276504","tags":["report"]},{"url":"https://bugzilla.suse.com/1276508","tags":["report"]},{"url":"https://bugzilla.suse.com/1276512","tags":["report"]},{"url":"https://bugzilla.suse.com/1276519","tags":["report"]},{"url":"https://bugzilla.suse.com/1276528","tags":["report"]},{"url":"https://bugzilla.suse.com/1276532","tags":["report"]},{"url":"https://bugzilla.suse.com/1276535","tags":["report"]},{"url":"https://bugzilla.suse.com/1276538","tags":["report"]},{"url":"https://bugzilla.suse.com/1276547","tags":["report"]},{"url":"https://bugzilla.suse.com/1276553","tags":["report"]},{"url":"https://bugzilla.suse.com/1276563","tags":["report"]},{"url":"https://bugzilla.suse.com/1276565","tags":["report"]},{"url":"https://bugzilla.suse.com/1276570","tags":["report"]},{"url":"https://bugzilla.suse.com/1276572","tags":["report"]},{"url":"https://bugzilla.suse.com/1276573","tags":["report"]},{"url":"https://bugzilla.suse.com/1276579","tags":["report"]},{"url":"https://bugzilla.suse.com/1276766","tags":["report"]},{"url":"https://bugzilla.suse.com/1276767","tags":["report"]},{"url":"https://bugzilla.suse.com/1276783","tags":["report"]},{"url":"https://bugzilla.suse.com/1276793","tags":["report"]},{"url":"https://bugzilla.suse.com/1276801","tags":["report"]},{"url":"https://bugzilla.suse.com/1276803","tags":["report"]},{"url":"https://bugzilla.suse.com/1276814","tags":["report"]},{"url":"https://bugzilla.suse.com/1276818","tags":["report"]},{"url":"https://bugzilla.suse.com/1276821","tags":["report"]},{"url":"https://bugzilla.suse.com/1276840","tags":["report"]},{"url":"https://bugzilla.suse.com/1276865","tags":["report"]},{"url":"https://bugzilla.suse.com/1276866","tags":["report"]},{"url":"https://bugzilla.suse.com/1276876","tags":["report"]},{"url":"https://bugzilla.suse.com/1276880","tags":["report"]},{"url":"https://bugzilla.suse.com/1276891","tags":["report"]},{"url":"https://bugzilla.suse.com/1276905","tags":["report"]},{"url":"https://bugzilla.suse.com/1276921","tags":["report"]},{"url":"https://bugzilla.suse.com/1276922","tags":["report"]},{"url":"https://bugzilla.suse.com/1276923","tags":["report"]},{"url":"https://bugzilla.suse.com/1276930","tags":["report"]},{"url":"https://bugzilla.suse.com/1277023","tags":["report"]},{"url":"https://bugzilla.suse.com/1277030","tags":["report"]},{"url":"https://bugzilla.suse.com/1277032","tags":["report"]},{"url":"https://bugzilla.suse.com/1277036","tags":["report"]},{"url":"https://bugzilla.suse.com/1277070","tags":["report"]},{"url":"https://bugzilla.suse.com/1277078","tags":["report"]},{"url":"https://bugzilla.suse.com/1277092","tags":["report"]},{"url":"https://bugzilla.suse.com/1277098","tags":["report"]},{"url":"https://bugzilla.suse.com/1277108","tags":["report"]},{"url":"https://bugzilla.suse.com/1277109","tags":["report"]},{"url":"https://bugzilla.suse.com/1277114","tags":["report"]},{"url":"https://bugzilla.suse.com/1277115","tags":["report"]},{"url":"https://bugzilla.suse.com/1277120","tags":["report"]},{"url":"https://bugzilla.suse.com/1277122","tags":["report"]},{"url":"https://bugzilla.suse.com/1277128","tags":["report"]},{"url":"https://bugzilla.suse.com/1277129","tags":["report"]},{"url":"https://bugzilla.suse.com/1277143","tags":["report"]},{"url":"https://bugzilla.suse.com/1277148","tags":["report"]},{"url":"https://bugzilla.suse.com/1277149","tags":["report"]},{"url":"https://bugzilla.suse.com/1277179","tags":["report"]},{"url":"https://bugzilla.suse.com/1277215","tags":["report"]},{"url":"https://bugzilla.suse.com/1277217","tags":["report"]},{"url":"https://bugzilla.suse.com/1277218","tags":["report"]},{"url":"https://bugzilla.suse.com/1277229","tags":["report"]},{"url":"https://bugzilla.suse.com/1277231","tags":["report"]},{"url":"https://bugzilla.suse.com/1277233","tags":["report"]},{"url":"https://bugzilla.suse.com/1277235","tags":["report"]},{"url":"https://bugzilla.suse.com/1277245","tags":["report"]},{"url":"https://bugzilla.suse.com/1277249","tags":["report"]},{"url":"https://bugzilla.suse.com/1277254","tags":["report"]},{"url":"https://bugzilla.suse.com/1277268","tags":["report"]},{"url":"https://bugzilla.suse.com/1277272","tags":["report"]},{"url":"https://bugzilla.suse.com/1277296","tags":["report"]},{"url":"https://bugzilla.suse.com/1277308","tags":["report"]},{"url":"https://bugzilla.suse.com/1277314","tags":["report"]},{"url":"https://bugzilla.suse.com/1277321","tags":["report"]},{"url":"https://bugzilla.suse.com/1277328","tags":["report"]},{"url":"https://bugzilla.suse.com/1277335","tags":["report"]},{"url":"https://bugzilla.suse.com/1277342","tags":["report"]},{"url":"https://bugzilla.suse.com/1277349","tags":["report"]},{"url":"https://bugzilla.suse.com/1277350","tags":["report"]},{"url":"https://bugzilla.suse.com/1277371","tags":["report"]},{"url":"https://bugzilla.suse.com/1277372","tags":["report"]},{"url":"https://bugzilla.suse.com/1277374","tags":["report"]},{"url":"https://bugzilla.suse.com/1277392","tags":["report"]},{"url":"https://bugzilla.suse.com/1277396","tags":["report"]},{"url":"https://bugzilla.suse.com/1277401","tags":["report"]},{"url":"https://bugzilla.suse.com/1277405","tags":["report"]},{"url":"https://bugzilla.suse.com/1277410","tags":["report"]},{"url":"https://bugzilla.suse.com/1277452","tags":["report"]},{"url":"https://bugzilla.suse.com/1277489","tags":["report"]},{"url":"https://bugzilla.suse.com/1277493","tags":["report"]},{"url":"https://bugzilla.suse.com/1277505","tags":["report"]},{"url":"https://bugzilla.suse.com/1277513","tags":["report"]},{"url":"https://bugzilla.suse.com/1277544","tags":["report"]},{"url":"https://bugzilla.suse.com/1277553","tags":["report"]},{"url":"https://bugzilla.suse.com/1277555","tags":["report"]},{"url":"https://bugzilla.suse.com/1277556","tags":["report"]},{"url":"https://bugzilla.suse.com/1277557","tags":["report"]},{"url":"https://bugzilla.suse.com/1277558","tags":["report"]},{"url":"https://bugzilla.suse.com/1277561","tags":["report"]},{"url":"https://bugzilla.suse.com/1277571","tags":["report"]},{"url":"https://bugzilla.suse.com/1277574","tags":["report"]},{"url":"https://bugzilla.suse.com/1277590","tags":["report"]},{"url":"https://bugzilla.suse.com/1277615","tags":["report"]},{"url":"https://bugzilla.suse.com/1277626","tags":["report"]},{"url":"https://bugzilla.suse.com/1277640","tags":["report"]},{"url":"https://bugzilla.suse.com/1277649","tags":["report"]},{"url":"https://bugzilla.suse.com/1277655","tags":["report"]},{"url":"https://bugzilla.suse.com/1277656","tags":["report"]},{"url":"https://bugzilla.suse.com/1277662","tags":["report"]},{"url":"https://bugzilla.suse.com/1277674","tags":["report"]},{"url":"https://bugzilla.suse.com/1277705","tags":["report"]},{"url":"https://bugzilla.suse.com/1277728","tags":["report"]},{"url":"https://bugzilla.suse.com/1277738","tags":["report"]},{"url":"https://bugzilla.suse.com/1277748","tags":["report"]},{"url":"https://bugzilla.suse.com/1277761","tags":["report"]},{"url":"https://bugzilla.suse.com/1277764","tags":["report"]},{"url":"https://bugzilla.suse.com/1277766","tags":["report"]},{"url":"https://bugzilla.suse.com/1277781","tags":["report"]},{"url":"https://bugzilla.suse.com/1277783","tags":["report"]},{"url":"https://bugzilla.suse.com/1277784","tags":["report"]},{"url":"https://bugzilla.suse.com/1277792","tags":["report"]},{"url":"https://bugzilla.suse.com/1277796","tags":["report"]},{"url":"https://bugzilla.suse.com/1277801","tags":["report"]},{"url":"https://bugzilla.suse.com/1277805","tags":["report"]},{"url":"https://bugzilla.suse.com/1277813","tags":["report"]},{"url":"https://bugzilla.suse.com/1277818","tags":["report"]},{"url":"https://bugzilla.suse.com/1277820","tags":["report"]},{"url":"https://bugzilla.suse.com/1277822","tags":["report"]},{"url":"https://bugzilla.suse.com/1277823","tags":["report"]},{"url":"https://bugzilla.suse.com/1277837","tags":["report"]},{"url":"https://bugzilla.suse.com/1277840","tags":["report"]},{"url":"https://bugzilla.suse.com/1277843","tags":["report"]},{"url":"https://bugzilla.suse.com/1277857","tags":["report"]},{"url":"https://bugzilla.suse.com/1277860","tags":["report"]},{"url":"https://bugzilla.suse.com/1277862","tags":["report"]},{"url":"https://bugzilla.suse.com/1277874","tags":["report"]},{"url":"https://bugzilla.suse.com/1277876","tags":["report"]},{"url":"https://bugzilla.suse.com/1277885","tags":["report"]},{"url":"https://bugzilla.suse.com/1277892","tags":["report"]},{"url":"https://bugzilla.suse.com/1277896","tags":["report"]},{"url":"https://bugzilla.suse.com/1277897","tags":["report"]},{"url":"https://bugzilla.suse.com/1277898","tags":["report"]},{"url":"https://bugzilla.suse.com/1277900","tags":["report"]},{"url":"https://bugzilla.suse.com/1277901","tags":["report"]},{"url":"https://bugzilla.suse.com/1277904","tags":["report"]},{"url":"https://bugzilla.suse.com/1277906","tags":["report"]},{"url":"https://bugzilla.suse.com/1277908","tags":["report"]},{"url":"https://bugzilla.suse.com/1277910","tags":["report"]},{"url":"https://bugzilla.suse.com/1277915","tags":["report"]},{"url":"https://bugzilla.suse.com/1277918","tags":["report"]},{"url":"https://bugzilla.suse.com/1278031","tags":["report"]},{"url":"https://bugzilla.suse.com/1278035","tags":["report"]},{"url":"https://bugzilla.suse.com/1278053","tags":["report"]},{"url":"https://bugzilla.suse.com/1278054","tags":["report"]},{"url":"https://bugzilla.suse.com/1278056","tags":["report"]},{"url":"https://bugzilla.suse.com/1278063","tags":["report"]},{"url":"https://bugzilla.suse.com/1278067","tags":["report"]},{"url":"https://bugzilla.suse.com/1278070","tags":["report"]},{"url":"https://bugzilla.suse.com/1278087","tags":["report"]},{"url":"https://bugzilla.suse.com/1278088","tags":["report"]},{"url":"https://bugzilla.suse.com/1278091","tags":["report"]},{"url":"https://bugzilla.suse.com/1278094","tags":["report"]},{"url":"https://bugzilla.suse.com/1278098","tags":["report"]},{"url":"https://bugzilla.suse.com/1278100","tags":["report"]},{"url":"https://bugzilla.suse.com/1278108","tags":["report"]},{"url":"https://bugzilla.suse.com/1278113","tags":["report"]},{"url":"https://bugzilla.suse.com/1278132","tags":["report"]},{"url":"https://bugzilla.suse.com/1278155","tags":["report"]},{"url":"https://bugzilla.suse.com/1278178","tags":["report"]},{"url":"https://bugzilla.suse.com/1278180","tags":["report"]},{"url":"https://bugzilla.suse.com/1278191","tags":["report"]},{"url":"https://bugzilla.suse.com/1278195","tags":["report"]},{"url":"https://bugzilla.suse.com/1278199","tags":["report"]},{"url":"https://bugzilla.suse.com/1278205","tags":["report"]},{"url":"https://bugzilla.suse.com/1278210","tags":["report"]},{"url":"https://bugzilla.suse.com/1278211","tags":["report"]},{"url":"https://bugzilla.suse.com/1278216","tags":["report"]},{"url":"https://bugzilla.suse.com/1278225","tags":["report"]},{"url":"https://bugzilla.suse.com/1278233","tags":["report"]},{"url":"https://bugzilla.suse.com/1278236","tags":["report"]},{"url":"https://bugzilla.suse.com/1278240","tags":["report"]},{"url":"https://bugzilla.suse.com/1278245","tags":["report"]},{"url":"https://bugzilla.suse.com/1278247","tags":["report"]},{"url":"https://bugzilla.suse.com/1278253","tags":["report"]},{"url":"https://bugzilla.suse.com/1278255","tags":["report"]},{"url":"https://bugzilla.suse.com/1278293","tags":["report"]},{"url":"https://bugzilla.suse.com/1278294","tags":["report"]},{"url":"https://bugzilla.suse.com/1278311","tags":["report"]},{"url":"https://bugzilla.suse.com/1278314","tags":["report"]},{"url":"https://bugzilla.suse.com/1278315","tags":["report"]},{"url":"https://bugzilla.suse.com/1278324","tags":["report"]},{"url":"https://bugzilla.suse.com/1278331","tags":["report"]},{"url":"https://bugzilla.suse.com/1278335","tags":["report"]},{"url":"https://bugzilla.suse.com/1278395","tags":["report"]},{"url":"https://bugzilla.suse.com/1278416","tags":["report"]},{"url":"https://bugzilla.suse.com/1278708","tags":["report"]},{"url":"https://bugzilla.suse.com/1278716","tags":["report"]},{"url":"https://bugzilla.suse.com/1278733","tags":["report"]},{"url":"https://bugzilla.suse.com/1279422","tags":["report"]},{"url":"https://bugzilla.suse.com/1279487","tags":["report"]},{"url":"https://bugzilla.suse.com/1279497","tags":["report"]},{"url":"https://bugzilla.suse.com/1279525","tags":["report"]},{"url":"https://bugzilla.suse.com/1279527","tags":["report"]},{"url":"https://bugzilla.suse.com/1279532","tags":["report"]},{"url":"https://bugzilla.suse.com/1279535","tags":["report"]},{"url":"https://bugzilla.suse.com/1279536","tags":["report"]},{"url":"https://bugzilla.suse.com/1279580","tags":["report"]},{"url":"https://bugzilla.suse.com/1279581","tags":["report"]},{"url":"https://bugzilla.suse.com/1279619","tags":["report"]},{"url":"https://bugzilla.suse.com/1279621","tags":["report"]},{"url":"https://bugzilla.suse.com/1279786","tags":["report"]},{"url":"https://bugzilla.suse.com/1279799","tags":["report"]},{"url":"https://bugzilla.suse.com/1279811","tags":["report"]},{"url":"https://bugzilla.suse.com/1279813","tags":["report"]},{"url":"https://bugzilla.suse.com/1279819","tags":["report"]},{"url":"https://bugzilla.suse.com/1279835","tags":["report"]},{"url":"https://bugzilla.suse.com/1279847","tags":["report"]},{"url":"https://bugzilla.suse.com/1279850","tags":["report"]},{"url":"https://bugzilla.suse.com/1279875","tags":["report"]},{"url":"https://bugzilla.suse.com/1279878","tags":["report"]},{"url":"https://bugzilla.suse.com/1279888","tags":["report"]},{"url":"https://bugzilla.suse.com/1280139","tags":["report"]},{"url":"https://bugzilla.suse.com/1280143","tags":["report"]},{"url":"https://bugzilla.suse.com/1280146","tags":["report"]},{"url":"https://bugzilla.suse.com/1280148","tags":["report"]},{"url":"https://bugzilla.suse.com/1280151","tags":["report"]},{"url":"https://bugzilla.suse.com/1280178","tags":["report"]},{"url":"https://bugzilla.suse.com/1280184","tags":["report"]},{"url":"https://bugzilla.suse.com/1280206","tags":["report"]},{"url":"https://bugzilla.suse.com/1280235","tags":["report"]},{"url":"https://bugzilla.suse.com/1280237","tags":["report"]},{"url":"https://bugzilla.suse.com/1280243","tags":["report"]},{"url":"https://bugzilla.suse.com/1280252","tags":["report"]},{"url":"https://bugzilla.suse.com/1280263","tags":["report"]},{"url":"https://bugzilla.suse.com/1280296","tags":["report"]},{"url":"https://bugzilla.suse.com/1280298","tags":["report"]},{"url":"https://bugzilla.suse.com/1280338","tags":["report"]},{"url":"https://bugzilla.suse.com/1280350","tags":["report"]},{"url":"https://bugzilla.suse.com/1280375","tags":["report"]},{"url":"https://bugzilla.suse.com/1280379","tags":["report"]},{"url":"https://bugzilla.suse.com/1280383","tags":["report"]},{"url":"https://bugzilla.suse.com/1280387","tags":["report"]},{"url":"https://bugzilla.suse.com/1280388","tags":["report"]},{"url":"https://bugzilla.suse.com/1280449","tags":["report"]},{"url":"https://bugzilla.suse.com/1280451","tags":["report"]},{"url":"https://bugzilla.suse.com/1280455","tags":["report"]},{"url":"https://bugzilla.suse.com/1280456","tags":["report"]},{"url":"https://bugzilla.suse.com/1280468","tags":["report"]},{"url":"https://bugzilla.suse.com/1280487","tags":["report"]},{"url":"https://bugzilla.suse.com/1280490","tags":["report"]},{"url":"https://bugzilla.suse.com/1280496","tags":["report"]},{"url":"https://bugzilla.suse.com/1280508","tags":["report"]},{"url":"https://bugzilla.suse.com/1280509","tags":["report"]},{"url":"https://bugzilla.suse.com/1280518","tags":["report"]},{"url":"https://bugzilla.suse.com/1280544","tags":["report"]},{"url":"https://bugzilla.suse.com/1280546","tags":["report"]},{"url":"https://bugzilla.suse.com/1280548","tags":["report"]},{"url":"https://bugzilla.suse.com/1280551","tags":["report"]},{"url":"https://bugzilla.suse.com/1280577","tags":["report"]},{"url":"https://bugzilla.suse.com/1280711","tags":["report"]},{"url":"https://bugzilla.suse.com/1280716","tags":["report"]},{"url":"https://bugzilla.suse.com/1280717","tags":["report"]},{"url":"https://bugzilla.suse.com/1280719","tags":["report"]},{"url":"https://bugzilla.suse.com/1280726","tags":["report"]},{"url":"https://bugzilla.suse.com/1280727","tags":["report"]},{"url":"https://bugzilla.suse.com/1280733","tags":["report"]},{"url":"https://bugzilla.suse.com/1280750","tags":["report"]},{"url":"https://bugzilla.suse.com/1280758","tags":["report"]},{"url":"https://bugzilla.suse.com/1280786","tags":["report"]},{"url":"https://bugzilla.suse.com/1280797","tags":["report"]},{"url":"https://bugzilla.suse.com/1280870","tags":["report"]},{"url":"https://bugzilla.suse.com/1280872","tags":["report"]},{"url":"https://bugzilla.suse.com/1280923","tags":["report"]},{"url":"https://bugzilla.suse.com/1280985","tags":["report"]},{"url":"https://bugzilla.suse.com/1280993","tags":["report"]},{"url":"https://bugzilla.suse.com/1281010","tags":["report"]},{"url":"https://bugzilla.suse.com/1281042","tags":["report"]},{"url":"https://bugzilla.suse.com/1281046","tags":["report"]},{"url":"https://bugzilla.suse.com/1281054","tags":["report"]},{"url":"https://bugzilla.suse.com/1281057","tags":["report"]},{"url":"https://bugzilla.suse.com/1281077","tags":["report"]},{"url":"https://bugzilla.suse.com/1281085","tags":["report"]},{"url":"https://bugzilla.suse.com/1281201","tags":["report"]},{"url":"https://bugzilla.suse.com/1281202","tags":["report"]},{"url":"https://bugzilla.suse.com/1281224","tags":["report"]},{"url":"https://bugzilla.suse.com/1281226","tags":["report"]},{"url":"https://bugzilla.suse.com/1281229","tags":["report"]},{"url":"https://bugzilla.suse.com/1281231","tags":["report"]},{"url":"https://bugzilla.suse.com/1281273","tags":["report"]},{"url":"https://bugzilla.suse.com/1281295","tags":["report"]},{"url":"https://bugzilla.suse.com/1281358","tags":["report"]},{"url":"https://bugzilla.suse.com/1281359","tags":["report"]},{"url":"https://bugzilla.suse.com/1281379","tags":["report"]},{"url":"https://bugzilla.suse.com/1281383","tags":["report"]},{"url":"https://bugzilla.suse.com/1281387","tags":["report"]},{"url":"https://bugzilla.suse.com/1281397","tags":["report"]},{"url":"https://bugzilla.suse.com/1281399","tags":["report"]},{"url":"https://bugzilla.suse.com/1281408","tags":["report"]},{"url":"https://bugzilla.suse.com/1281427","tags":["report"]},{"url":"https://bugzilla.suse.com/1281496","tags":["report"]},{"url":"https://bugzilla.suse.com/1281514","tags":["report"]},{"url":"https://bugzilla.suse.com/1281546","tags":["report"]},{"url":"https://bugzilla.suse.com/1281599","tags":["report"]},{"url":"https://bugzilla.suse.com/1281644","tags":["report"]},{"url":"https://bugzilla.suse.com/1281680","tags":["report"]},{"url":"https://bugzilla.suse.com/1281694","tags":["report"]},{"url":"https://bugzilla.suse.com/1281717","tags":["report"]},{"url":"https://bugzilla.suse.com/1281732","tags":["report"]},{"url":"https://bugzilla.suse.com/1281738","tags":["report"]},{"url":"https://bugzilla.suse.com/1281777","tags":["report"]},{"url":"https://bugzilla.suse.com/1281778","tags":["report"]},{"url":"https://bugzilla.suse.com/1281786","tags":["report"]},{"url":"https://bugzilla.suse.com/1281789","tags":["report"]},{"url":"https://bugzilla.suse.com/1281793","tags":["report"]},{"url":"https://bugzilla.suse.com/1281795","tags":["report"]},{"url":"https://bugzilla.suse.com/1281808","tags":["report"]},{"url":"https://bugzilla.suse.com/1281818","tags":["report"]},{"url":"https://bugzilla.suse.com/1281825","tags":["report"]},{"url":"https://bugzilla.suse.com/1281922","tags":["report"]},{"url":"https://bugzilla.suse.com/1281927","tags":["report"]},{"url":"https://bugzilla.suse.com/1281955","tags":["report"]},{"url":"https://bugzilla.suse.com/1281964","tags":["report"]},{"url":"https://bugzilla.suse.com/1281973","tags":["report"]},{"url":"https://bugzilla.suse.com/1281988","tags":["report"]},{"url":"https://bugzilla.suse.com/1281993","tags":["report"]},{"url":"https://bugzilla.suse.com/1281995","tags":["report"]},{"url":"https://bugzilla.suse.com/1281997","tags":["report"]},{"url":"https://bugzilla.suse.com/1282020","tags":["report"]},{"url":"https://bugzilla.suse.com/1282034","tags":["report"]},{"url":"https://bugzilla.suse.com/1282040","tags":["report"]},{"url":"https://bugzilla.suse.com/1282041","tags":["report"]},{"url":"https://bugzilla.suse.com/1282042","tags":["report"]},{"url":"https://bugzilla.suse.com/1282050","tags":["report"]},{"url":"https://bugzilla.suse.com/1282054","tags":["report"]},{"url":"https://bugzilla.suse.com/1282072","tags":["report"]},{"url":"https://bugzilla.suse.com/1282104","tags":["report"]},{"url":"https://bugzilla.suse.com/1282110","tags":["report"]},{"url":"https://bugzilla.suse.com/1282113","tags":["report"]},{"url":"https://bugzilla.suse.com/1282143","tags":["report"]},{"url":"https://bugzilla.suse.com/1282170","tags":["report"]},{"url":"https://bugzilla.suse.com/1282193","tags":["report"]},{"url":"https://bugzilla.suse.com/1282197","tags":["report"]},{"url":"https://bugzilla.suse.com/1282270","tags":["report"]},{"url":"https://bugzilla.suse.com/1282271","tags":["report"]},{"url":"https://bugzilla.suse.com/1282284","tags":["report"]},{"url":"https://bugzilla.suse.com/1282286","tags":["report"]},{"url":"https://bugzilla.suse.com/1282288","tags":["report"]},{"url":"https://bugzilla.suse.com/1282383","tags":["report"]},{"url":"https://bugzilla.suse.com/1282648","tags":["report"]},{"url":"https://bugzilla.suse.com/1282672","tags":["report"]},{"url":"https://bugzilla.suse.com/1282767","tags":["report"]},{"url":"https://bugzilla.suse.com/1282774","tags":["report"]},{"url":"https://bugzilla.suse.com/1282803","tags":["report"]},{"url":"https://bugzilla.suse.com/1282810","tags":["report"]},{"url":"https://bugzilla.suse.com/1282812","tags":["report"]},{"url":"https://bugzilla.suse.com/1282823","tags":["report"]},{"url":"https://bugzilla.suse.com/1282881","tags":["report"]},{"url":"https://bugzilla.suse.com/1282891","tags":["report"]},{"url":"https://bugzilla.suse.com/1282906","tags":["report"]},{"url":"https://bugzilla.suse.com/1282997","tags":["report"]},{"url":"https://bugzilla.suse.com/1283121","tags":["report"]},{"url":"https://bugzilla.suse.com/1283154","tags":["report"]},{"url":"https://bugzilla.suse.com/1283163","tags":["report"]},{"url":"https://bugzilla.suse.com/1283176","tags":["report"]},{"url":"https://bugzilla.suse.com/1283201","tags":["report"]},{"url":"https://bugzilla.suse.com/1283213","tags":["report"]},{"url":"https://bugzilla.suse.com/1283230","tags":["report"]},{"url":"https://bugzilla.suse.com/1283312","tags":["report"]},{"url":"https://bugzilla.suse.com/1283500","tags":["report"]},{"url":"https://bugzilla.suse.com/1283805","tags":["report"]},{"url":"https://bugzilla.suse.com/1283935","tags":["report"]},{"url":"https://bugzilla.suse.com/1283973","tags":["report"]},{"url":"https://bugzilla.suse.com/1284146","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72066","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-72098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89609","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-89644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97950","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98164","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624182-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1266008","tags":["report"]},{"url":"https://bugzilla.suse.com/1269532","tags":["report"]},{"url":"https://bugzilla.suse.com/1271955","tags":["report"]},{"url":"https://bugzilla.suse.com/1274920","tags":["report"]},{"url":"https://bugzilla.suse.com/1275540","tags":["report"]},{"url":"https://bugzilla.suse.com/1276277","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72084","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624315-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624316-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264640-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1250951","tags":["report"]},{"url":"https://bugzilla.suse.com/1261564","tags":["report"]},{"url":"https://bugzilla.suse.com/1261816","tags":["report"]},{"url":"https://bugzilla.suse.com/1267882","tags":["report"]},{"url":"https://bugzilla.suse.com/1272971","tags":["report"]},{"url":"https://bugzilla.suse.com/1273320","tags":["report"]},{"url":"https://bugzilla.suse.com/1274824","tags":["report"]},{"url":"https://bugzilla.suse.com/1274900","tags":["report"]},{"url":"https://bugzilla.suse.com/1275137","tags":["report"]},{"url":"https://bugzilla.suse.com/1275142","tags":["report"]},{"url":"https://bugzilla.suse.com/1275238","tags":["report"]},{"url":"https://bugzilla.suse.com/1275680","tags":["report"]},{"url":"https://bugzilla.suse.com/1275682","tags":["report"]},{"url":"https://bugzilla.suse.com/1275801","tags":["report"]},{"url":"https://bugzilla.suse.com/1275804","tags":["report"]},{"url":"https://bugzilla.suse.com/1275812","tags":["report"]},{"url":"https://bugzilla.suse.com/1275956","tags":["report"]},{"url":"https://bugzilla.suse.com/1276262","tags":["report"]},{"url":"https://bugzilla.suse.com/1276471","tags":["report"]},{"url":"https://bugzilla.suse.com/1276852","tags":["report"]},{"url":"https://bugzilla.suse.com/1276947","tags":["report"]},{"url":"https://bugzilla.suse.com/1277153","tags":["report"]},{"url":"https://bugzilla.suse.com/1277234","tags":["report"]},{"url":"https://bugzilla.suse.com/1277407","tags":["report"]},{"url":"https://bugzilla.suse.com/1277451","tags":["report"]},{"url":"https://bugzilla.suse.com/1277535","tags":["report"]},{"url":"https://bugzilla.suse.com/1277773","tags":["report"]},{"url":"https://bugzilla.suse.com/1277845","tags":["report"]},{"url":"https://bugzilla.suse.com/1278215","tags":["report"]},{"url":"https://bugzilla.suse.com/1278709","tags":["report"]},{"url":"https://bugzilla.suse.com/1279590","tags":["report"]},{"url":"https://bugzilla.suse.com/1280239","tags":["report"]},{"url":"https://bugzilla.suse.com/1280299","tags":["report"]},{"url":"https://bugzilla.suse.com/1280309","tags":["report"]},{"url":"https://bugzilla.suse.com/1280384","tags":["report"]},{"url":"https://bugzilla.suse.com/1280927","tags":["report"]},{"url":"https://bugzilla.suse.com/1280969","tags":["report"]},{"url":"https://bugzilla.suse.com/1281660","tags":["report"]},{"url":"https://bugzilla.suse.com/1281682","tags":["report"]},{"url":"https://bugzilla.suse.com/1281683","tags":["report"]},{"url":"https://bugzilla.suse.com/1281845","tags":["report"]},{"url":"https://bugzilla.suse.com/1282003","tags":["report"]},{"url":"https://bugzilla.suse.com/1282013","tags":["report"]},{"url":"https://bugzilla.suse.com/1282975","tags":["report"]},{"url":"https://bugzilla.suse.com/1283130","tags":["report"]},{"url":"https://bugzilla.suse.com/1283489","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98030","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264706-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-31689","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-31689","tags":["report"]},{"url":"https://git.kernel.org/linus/51520e03e70d6c73e33ee7cbe0319767d05764fe","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8567-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8596-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8606-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8607-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8608-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8609-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8619-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8665-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-21709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-62626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71288","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-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","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-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53354","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-43185","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-45972","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-46260","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-2026-64018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64587","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-31689","title":"EDAC/mc: Fix error path ordering in edac_mc_alloc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T17:34:27.793Z","modified":"2026-05-11T22:13:44.271Z","updated_at":"2026-11-02T14:19:50.92611Z"}],"euvd":[{"id":"EUVD-2026-25886","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T17:34:27Z","modified":"2026-05-11T22:13:44Z","updated_at":"2026-11-02T19:04:43.980793Z"}],"ghsa":[{"id":"GHSA-9qrw-cmg5-g8vq","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T18:32:09Z","modified":"2026-05-06T21:32:35Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T15:07:55.830667Z"}],"nvd":[{"id":"CVE-2026-31689","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T18:16:54.387Z","modified":"2026-06-17T10:34:14.72Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-476"],"updated_at":"2026-11-02T14:12:16.252509Z"}],"osv":[{"id":"BELL-CVE-2026-31689","status":"published","published":"2026-04-28T06:14:32.2043Z","modified":"2026-06-25T07:18:36.845191069Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:23.572955Z"},{"id":"DEBIAN-CVE-2026-31689","description":"In the Linux kernel, the following vulnerability has been resolved:  EDAC/mc: Fix error path ordering in edac_mc_alloc()  When the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path will call put_device() which will end up calling the device's release function.  However, the init ordering is wrong such that device_initialize() happens *after* the failed allocation and thus the device itself and the release function pointer are not initialized yet when they're called:    MCE: In-kernel MCE decoding enabled.   ------------[ cut here ]------------   kobject: '(null)': is not initialized, yet kobject_put() is being called.   WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd   CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)   RIP: 0010:kobject_put   Call Trace:    \u003cTASK\u003e    edac_mc_alloc+0xbe/0xe0 [edac_core]    amd64_edac_init+0x7a4/0xff0 [amd64_edac]    ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]    do_one_initcall    ...  Reorder the calling sequence so that the device is initialized and thus the release function pointer is properly set before it can be used.  This was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T18:16:54.387Z","modified":"2026-10-01T03:02:35.996321997Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:54.232518Z"},{"id":"OESA-2026-2581","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\nnet: mvpp2: Prevent parser TCAM memory corruption\n\nProtect the parser TCAM/SRAM memory, and the cached (shadow) SRAM\ninformation, from concurrent modifications.\n\nBoth the TCAM and SRAM tables are indirectly accessed by configuring\nan index register that selects the row to read or write to. This means\nthat operations must be atomic in order to, e.g., avoid spreading\nwrites across multiple rows. Since the shadow SRAM array is used to\nfind free rows in the hardware table, it must also be protected in\norder to avoid TOCTOU errors where multiple cores allocate the same\nrow.\n\nThis issue was detected in a situation where `mvpp2_set_rx_mode()` ran\nconcurrently on two CPUs. In this particular case the\nMVPP2_PE_MAC_UC_PROMISCUOUS entry was corrupted, causing the\nclassifier unit to drop all incoming unicast - indicated by the\n`rx_classifier_drops` counter.(CVE-2025-22060)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix NULL pointer in can_accept_new_subflow\n\nWhen testing valkey benchmark tool with MPTCP, the kernel panics in\n\u0026apos;mptcp_can_accept_new_subflow\u0026apos; because subflow_req-\u0026gt;msk is NULL.\n\nCall trace:\n\n  mptcp_can_accept_new_subflow (./net/mptcp/subflow.c:63 (discriminator 4)) (P)\n  subflow_syn_recv_sock (./net/mptcp/subflow.c:854)\n  tcp_check_req (./net/ipv4/tcp_minisocks.c:863)\n  tcp_v4_rcv (./net/ipv4/tcp_ipv4.c:2268)\n  ip_protocol_deliver_rcu (./net/ipv4/ip_input.c:207)\n  ip_local_deliver_finish (./net/ipv4/ip_input.c:234)\n  ip_local_deliver (./net/ipv4/ip_input.c:254)\n  ip_rcv_finish (./net/ipv4/ip_input.c:449)\n  ...\n\nAccording to the debug log, the same req received two SYN-ACK in a very\nshort time, very likely because the client retransmits the syn ack due\nto multiple reasons.\n\nEven if the packets are transmitted with a relevant time interval, they\ncan be processed by the server on different CPUs concurrently). The\n\u0026apos;subflow_req-\u0026gt;msk\u0026apos; ownership is transferred to the subflow the first,\nand there will be a risk of a null pointer dereference here.\n\nThis patch fixes this issue by moving the \u0026apos;subflow_req-\u0026gt;msk\u0026apos; under the\n`own_req == true` conditional.\n\nNote that the !msk check in subflow_hmac_valid() can be dropped, because\nthe same check already exists under the own_req mpj branch where the\ncode has been moved to.(CVE-2025-23145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmISDN: hfcpci: Fix warning when deleting uninitialized timer\n\nWith CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads\nto the following splat:\n\n[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0\n[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0\n[  250.218775] Modules linked in: hfcpci(-) mISDN_core\n[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)\n[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0\n[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d\n[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286\n[  250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95\n[  250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0\n[  250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39\n[  250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001\n[  250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8\n[  250.232454] FS:  00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:0000000000000000\n[  250.233851] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  250.234856] CR2: 00007f32090a7421 CR3: 0000000004d63000 CR4: 00000000000006f0\n[  250.236117] Call Trace:\n[  250.236599]  \u0026lt;TASK\u0026gt;\n[  250.236967]  ? trace_irq_enable.constprop.0+0xd4/0x130\n[  250.237920]  debug_object_assert_init+0x1f6/0x310\n[  250.238762]  ? __pfx_debug_object_assert_init+0x10/0x10\n[  250.239658]  ? __lock_acquire+0xdea/0x1c70\n[  250.240369]  __try_to_del_timer_sync+0x69/0x140\n[  250.241172]  ? __pfx___try_to_del_timer_sync+0x10/0x10\n[  250.242058]  ? __timer_delete_sync+0xc6/0x120\n[  250.242842]  ? lock_acquire+0x30/0x80\n[  250.243474]  ? __timer_delete_sync+0xc6/0x120\n[  250.244262]  __timer_delete_sync+0x98/0x120\n[  250.245015]  HFC_cleanup+0x10/0x20 [hfcpci]\n[  250.245704]  __do_sys_delete_module+0x348/0x510\n[  250.246461]  ? __pfx___do_sys_delete_module+0x10/0x10\n[  250.247338]  do_syscall_64+0xc1/0x360\n[  250.247924]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix this by initializing hfc_tl timer with DEFINE_TIMER macro.\nAlso, use mod_timer instead of manual timeout update.(CVE-2025-39833)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Add support for Van Gogh SoC\n\nThe ROG Xbox Ally (non-X) SoC features a similar architecture to the\nSteam Deck. While the Steam Deck supports S3 (s2idle causes a crash),\nthis support was dropped by the Xbox Ally which only S0ix suspend.\n\nSince the handler is missing here, this causes the device to not suspend\nand the AMD GPU driver to crash while trying to resume afterwards due to\na power hang.(CVE-2025-68334)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: Move team device type change at the end of team_port_add\n\nAttempting to add a port device that is already up will expectedly fail,\nbut not before modifying the team device header_ops.\n\nIn the case of the syzbot reproducer the gre0 device is\nalready in state UP when it attempts to add it as a\nport device of team0, this fails but before that\nheader_ops-\u0026gt;create of team0 is changed from eth_header to ipgre_header\nin the call to team_dev_type_check_change.\n\nLater when we end up in ipgre_header() struct ip_tunnel* points to nonsense\nas the private data of the device still holds a struct team.\n\nExample sequence of iproute2 commands to reproduce the hang/BUG():\nip link add dev team0 type team\nip link add dev gre0 type gre\nip link set dev gre0 up\nip link set dev gre0 master team0\nip link set dev team0 up\nping -I team0 1.1.1.1\n\nMove team_dev_type_check_change down where all other checks have passed\nas it changes the dev type with no way to restore it in case\none of the checks that follow it fail.\n\nAlso make sure to preserve the origial mtu assignment:\n  - If port_dev is not the same type as dev, dev takes mtu from port_dev\n  - If port_dev is the same type as dev, port_dev takes mtu from dev\n\nThis is done by adding a conditional before the call to dev_set_mtu\nto prevent it from assigning port_dev-\u0026gt;mtu = dev-\u0026gt;mtu and instead\nletting team_dev_type_check_change assign dev-\u0026gt;mtu = port_dev-\u0026gt;mtu.\nThe conditional is needed because the patch moves the call to\nteam_dev_type_check_change past dev_set_mtu.\n\nTesting:\n  - team device driver in-tree selftests\n  - Add/remove various devices as slaves of team device\n  - syzbot(CVE-2025-68340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: asix: validate PHY address before use\n\nThe ASIX driver reads the PHY address from the USB device via\nasix_read_phy_addr(). A malicious or faulty device can return an\ninvalid address (\u0026gt;= PHY_MAX_ADDR), which causes a warning in\nmdiobus_get_phy():\n\n  addr 207 out of range\n  WARNING: drivers/net/phy/mdio_bus.c:76\n\nValidate the PHY address in asix_read_phy_addr() and remove the\nnow-redundant check in ax88172a.c.(CVE-2025-71094)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_gre: make ip6gre_header() robust\n\nOver the years, syzbot found many ways to crash the kernel\nin ip6gre_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 ip6gre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff8a1d69a8 len:136 put:40 head:ffff888059bc7000 data:ffff888059bc6fe8 tail:0x70 end:0x6c0 dev:team0\n------------[ cut here ]------------\n kernel BUG at net/core/skbuff.c:213 !\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  ip6gre_header+0xc8/0x790 net/ipv6/ip6_gre.c:1371\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  neigh_output include/net/neighbour.h:556 [inline]\n  ip6_finish_output2+0xfb3/0x1480 net/ipv6/ip6_output.c:136\n __ip6_finish_output net/ipv6/ip6_output.c:-1 [inline]\n  ip6_finish_output+0x234/0x7d0 net/ipv6/ip6_output.c:220\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(CVE-2025-71098)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: add VLAN id validation before using\n\nCurrently, the VLAN id may be used without validation when\nreceive a VLAN configuration mailbox from VF. The length of\nvlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause\nout-of-bounds memory access once the VLAN id is bigger than\nor equal to VLAN_N_VID.\n\nTherefore, VLAN id needs to be checked to ensure it is within\nthe range of VLAN_N_VID.(CVE-2025-71112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix string copying in parse_apply_sb_mount_options()\n\nstrscpy_pad() can\u0026apos;t be used to copy a non-NUL-term string into a NUL-term\nstring of possibly bigger size.  Commit 0efc5990bca5 (\u0026quot;string.h: Introduce\nmemtostr() and memtostr_pad()\u0026quot;) provides additional information in that\nregard.  So if this happens, the following warning is observed:\n\nstrnlen: detected buffer overflow: 65 byte read of buffer size 64\nWARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032\nModules linked in:\nCPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __fortify_panic+0x1f/0x30 lib/string_helpers.c:1039\n strnlen include/linux/fortify-string.h:235 [inline]\n sized_strscpy include/linux/fortify-string.h:309 [inline]\n parse_apply_sb_mount_options fs/ext4/super.c:2504 [inline]\n __ext4_fill_super fs/ext4/super.c:5261 [inline]\n ext4_fill_super+0x3c35/0xad00 fs/ext4/super.c:5706\n get_tree_bdev_flags+0x387/0x620 fs/super.c:1636\n vfs_get_tree+0x93/0x380 fs/super.c:1814\n do_new_mount fs/namespace.c:3553 [inline]\n path_mount+0x6ae/0x1f70 fs/namespace.c:3880\n do_mount fs/namespace.c:3893 [inline]\n __do_sys_mount fs/namespace.c:4103 [inline]\n __se_sys_mount fs/namespace.c:4080 [inline]\n __x64_sys_mount+0x280/0x300 fs/namespace.c:4080\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x64/0x140 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nSince userspace is expected to provide s_mount_opts field to be at most 63\ncharacters long with the ending byte being NUL-term, use a 64-byte buffer\nwhich matches the size of s_mount_opts, so that strscpy_pad() does its job\nproperly.  Return with error if the user still managed to provide a\nnon-NUL-term string here.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-71123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb-\u0026gt;vma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb-\u0026gt;vma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb-\u0026gt;vma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer\u0026apos;s vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb-\u0026gt;vma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u0026gt;vma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn\u0026apos;t matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)(CVE-2025-71130)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmc91x: fix broken irq-context in PREEMPT_RT\n\nWhen smc91x.c is built with PREEMPT_RT, the following splat occurs\nin FVP_RevC:\n\n[   13.055000] smc91x LNRO0003:00 eth0: link up, 10Mbps, half-duplex, lpa 0x0000\n[   13.062137] BUG: workqueue leaked atomic, lock or RCU: kworker/2:1[106]\n[   13.062137]      preempt=0x00000000 lock=0-\u0026gt;0 RCU=0-\u0026gt;1 workfn=mld_ifc_work\n[   13.062266] C\n** replaying previous printk message **\n[   13.062266] CPU: 2 UID: 0 PID: 106 Comm: kworker/2:1 Not tainted 6.18.0-dirty #179 PREEMPT_{RT,(full)}\n[   13.062353] Hardware name:  , BIOS\n[   13.062382] Workqueue: mld mld_ifc_work\n[   13.062469] Call trace:\n[   13.062494]  show_stack+0x24/0x40 (C)\n[   13.062602]  __dump_stack+0x28/0x48\n[   13.062710]  dump_stack_lvl+0x7c/0xb0\n[   13.062818]  dump_stack+0x18/0x34\n[   13.062926]  process_scheduled_works+0x294/0x450\n[   13.063043]  worker_thread+0x260/0x3d8\n[   13.063124]  kthread+0x1c4/0x228\n[   13.063235]  ret_from_fork+0x10/0x20\n\nThis happens because smc_special_trylock() disables IRQs even on PREEMPT_RT,\nbut smc_special_unlock() does not restore IRQs on PREEMPT_RT.\nThe reason is that smc_special_unlock() calls spin_unlock_irqrestore(),\nand rcu_read_unlock_bh() in __dev_queue_xmit() cannot invoke\nrcu_read_unlock() through __local_bh_enable_ip() when current-\u0026gt;softirq_disable_cnt becomes zero.\n\nTo address this issue, replace smc_special_trylock() with spin_trylock_irqsave().(CVE-2025-71132)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: avoid chain re-validation if possible\n\nHamza Mahfooz reports cpu soft lock-ups in\nnft_chain_validate():\n\n watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [iptables-nft-re:37547]\n[..]\n RIP: 0010:nft_chain_validate+0xcb/0x110 [nf_tables]\n[..]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_immediate_validate+0x36/0x50 [nf_tables]\n  nft_chain_validate+0xc9/0x110 [nf_tables]\n  nft_table_validate+0x6b/0xb0 [nf_tables]\n  nf_tables_validate+0x8b/0xa0 [nf_tables]\n  nf_tables_commit+0x1df/0x1eb0 [nf_tables]\n[..]\n\nCurrently nf_tables will traverse the entire table (chain graph), starting\nfrom the entry points (base chains), exploring all possible paths\n(chain jumps).  But there are cases where we could avoid revalidation.\n\nConsider:\n1  input -\u0026gt; j2 -\u0026gt; j3\n2  input -\u0026gt; j2 -\u0026gt; j3\n3  input -\u0026gt; j1 -\u0026gt; j2 -\u0026gt; j3\n\nThen the second rule does not need to revalidate j2, and, by extension j3,\nbecause this was already checked during validation of the first rule.\nWe need to validate it only for rule 3.\n\nThis is needed because chain loop detection also ensures we do not exceed\nthe jump stack: Just because we know that j2 is cycle free, its last jump\nmight now exceed the allowed stack size.  We also need to update all\nreachable chains with the new largest observed call depth.\n\nCare has to be taken to revalidate even if the chain depth won\u0026apos;t be an\nissue: chain validation also ensures that expressions are not called from\ninvalid base chains.  For example, the masquerade expression can only be\ncalled from NAT postrouting base chains.\n\nTherefore we also need to keep record of the base chain context (type,\nhooknum) and revalidate if the chain becomes reachable from a different\nhook location.(CVE-2025-71160)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix deadlock in wait_current_trans() due to ignored transaction type\n\nWhen wait_current_trans() is called during start_transaction(), it\ncurrently waits for a blocked transaction without considering whether\nthe given transaction type actually needs to wait for that particular\ntransaction state. The btrfs_blocked_trans_types[] array already defines\nwhich transaction types should wait for which transaction states, but\nthis check was missing in wait_current_trans().\n\nThis can lead to a deadlock scenario involving two transactions and\npending ordered extents:\n\n  1. Transaction A is in TRANS_STATE_COMMIT_DOING state\n\n  2. A worker processing an ordered extent calls start_transaction()\n     with TRANS_JOIN\n\n  3. join_transaction() returns -EBUSY because Transaction A is in\n     TRANS_STATE_COMMIT_DOING\n\n  4. Transaction A moves to TRANS_STATE_UNBLOCKED and completes\n\n  5. A new Transaction B is created (TRANS_STATE_RUNNING)\n\n  6. The ordered extent from step 2 is added to Transaction B\u0026apos;s\n     pending ordered extents\n\n  7. Transaction B immediately starts commit by another task and\n     enters TRANS_STATE_COMMIT_START\n\n  8. The worker finally reaches wait_current_trans(), sees Transaction B\n     in TRANS_STATE_COMMIT_START (a blocked state), and waits\n     unconditionally\n\n  9. However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START\n     according to btrfs_blocked_trans_types[]\n\n  10. Transaction B is waiting for pending ordered extents to complete\n\n  11. Deadlock: Transaction B waits for ordered extent, ordered extent\n      waits for Transaction B\n\nThis can be illustrated by the following call stacks:\n  CPU0                              CPU1\n                                    btrfs_finish_ordered_io()\n                                      start_transaction(TRANS_JOIN)\n                                        join_transaction()\n                                          # -EBUSY (Transaction A is\n                                          # TRANS_STATE_COMMIT_DOING)\n  # Transaction A completes\n  # Transaction B created\n  # ordered extent added to\n  # Transaction B\u0026apos;s pending list\n  btrfs_commit_transaction()\n    # Transaction B enters\n    # TRANS_STATE_COMMIT_START\n    # waiting for pending ordered\n    # extents\n                                        wait_current_trans()\n                                          # waits for Transaction B\n                                          # (should not wait!)\n\nTask bstore_kv_sync in btrfs_commit_transaction waiting for ordered\nextents:\n\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  btrfs_commit_transaction+0xbf7/0xda0 [btrfs]\n  btrfs_sync_file+0x342/0x4d0 [btrfs]\n  __x64_sys_fdatasync+0x4b/0x80\n  do_syscall_64+0x33/0x40\n  entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nTask kworker in wait_current_trans waiting for transaction commit:\n\n  Workqueue: btrfs-syno_nocow btrfs_work_helper [btrfs]\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  wait_current_trans+0xb0/0x110 [btrfs]\n  start_transaction+0x346/0x5b0 [btrfs]\n  btrfs_finish_ordered_io.isra.0+0x49b/0x9c0 [btrfs]\n  btrfs_work_helper+0xe8/0x350 [btrfs]\n  process_one_work+0x1d3/0x3c0\n  worker_thread+0x4d/0x3e0\n  kthread+0x12d/0x150\n  ret_from_fork+0x1f/0x30\n\nFix this by passing the transaction type to wait_current_trans() and\nchecking btrfs_blocked_trans_types[cur_trans-\u0026gt;state] against the given\ntype before deciding to wait. This ensures that transaction types which\nare allowed to join during certain blocked states will not unnecessarily\nwait and cause deadlocks.(CVE-2025-71194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/sva: invalidate stale IOTLB entries for kernel address space\n\nIntroduce a new IOMMU interface to flush IOTLB paging cache entries for\nthe CPU kernel address space.  This interface is invoked from the x86\narchitecture code that manages combined user and kernel page tables,\nspecifically before any kernel page table page is freed and reused.\n\nThis addresses the main issue with vfree() which is a common occurrence\nand can be triggered by unprivileged users.  While this resolves the\nprimary problem, it doesn\u0026apos;t address some extremely rare case related to\nmemory unplug of memory that was present as reserved memory at boot, which\ncannot be triggered by unprivileged users.  The discussion can be found at\nthe link below.\n\nEnable SVA on x86 architecture since the IOMMU can now receive\nnotification to flush the paging cache before freeing the CPU kernel page\ntable pages.(CVE-2025-71202)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naudit: add fchmodat2() to change attributes class\n\nfchmodat2(), introduced in version 6.6 is currently not in the change\nattribute class of audit. Calling fchmodat2() to change a file\nattribute in the same fashion than chmod() or fchmodat() will bypass\naudit rules such as:\n\n-w /tmp/test -p rwa -k test_rwa\n\nThe current patch adds fchmodat2() to the change attributes class.(CVE-2025-71239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: fix possible UAF in macvlan_forward_source()\n\nAdd RCU protection on (struct macvlan_source_entry)-\u0026gt;vlan.\n\nWhenever macvlan_hash_del_source() is called, we must clear\nentry-\u0026gt;vlan pointer before RCU grace period starts.\n\nThis allows macvlan_forward_source() to skip over\nentries queued for freeing.\n\nNote that macvlan_dev are already RCU protected, as they\nare embedded in a standard netdev (netdev_priv(ndev)).\n\nhttps: //lore.kernel.org/netdev/(CVE-2026-23001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: ensure safe queue release with state management\n\nDirectly calling `put_queue` carries risks since it cannot\nguarantee that resources of `uacce_queue` have been fully released\nbeforehand. So adding a `stop_queue` operation for the\nUACCE_CMD_PUT_Q command and leaving the `put_queue` operation to\nthe final resource release ensures safety.\n\nQueue states are defined as follows:\n- UACCE_Q_ZOMBIE: Initial state\n- UACCE_Q_INIT: After opening `uacce`\n- UACCE_Q_STARTED: After `start` is issued via `ioctl`\n\nWhen executing `poweroff -f` in virt while accelerator are still\nworking, `uacce_fops_release` and `uacce_remove` may execute\nconcurrently. This can cause `uacce_put_queue` within\n`uacce_fops_release` to access a NULL `ops` pointer. Therefore, add\nstate checks to prevent accessing freed pointers.(CVE-2026-23063)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Enforce that teql can only be used as root qdisc\n\nDesign intent of teql is that it is only supposed to be used as root qdisc.\nWe need to check for that constraint.\n\nAlthough not important, I will describe the scenario that unearthed this\nissue for the curious.\n\nGangMin Kim \u0026lt;(CVE-2026-23074)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64/fpsimd: signal: Fix restoration of SVE context\n\nWhen SME is supported, Restoring SVE signal context can go wrong in a\nfew ways, including placing the task into an invalid state where the\nkernel may read from out-of-bounds memory (and may potentially take a\nfatal fault) and/or may kill the task with a SIGKILL.\n\n(1) Restoring a context with SVE_SIG_FLAG_SM set can place the task into\n    an invalid state where SVCR.SM is set (and sve_state is non-NULL)\n    but TIF_SME is clear, consequently resuting in out-of-bounds memory\n    reads and/or killing the task with SIGKILL.\n\n    This can only occur in unusual (but legitimate) cases where the SVE\n    signal context has either been modified by userspace or was saved in\n    the context of another task (e.g. as with CRIU), as otherwise the\n    presence of an SVE signal context with SVE_SIG_FLAG_SM implies that\n    TIF_SME is already set.\n\n    While in this state, task_fpsimd_load() will NOT configure SMCR_ELx\n    (leaving some arbitrary value configured in hardware) before\n    restoring SVCR and attempting to restore the streaming mode SVE\n    registers from memory via sve_load_state(). As the value of\n    SMCR_ELx.LEN may be larger than the task\u0026apos;s streaming SVE vector\n    length, this may read memory outside of the task\u0026apos;s allocated\n    sve_state, reading unrelated data and/or triggering a fault.\n\n    While this can result in secrets being loaded into streaming SVE\n    registers, these values are never exposed. As TIF_SME is clear,\n    fpsimd_bind_task_to_cpu() will configure CPACR_ELx.SMEN to trap EL0\n    accesses to streaming mode SVE registers, so these cannot be\n    accessed directly at EL0. As fpsimd_save_user_state() verifies the\n    live vector length before saving (S)SVE state to memory, no secret\n    values can be saved back to memory (and hence cannot be observed via\n    ptrace, signals, etc).\n\n    When the live vector length doesn\u0026apos;t match the expected vector length\n    for the task, fpsimd_save_user_state() will send a fatal SIGKILL\n    signal to the task. Hence the task may be killed after executing\n    userspace for some period of time.\n\n(2) Restoring a context with SVE_SIG_FLAG_SM clear does not clear the\n    task\u0026apos;s SVCR.SM. If SVCR.SM was set prior to restoring the context,\n    then the task will be left in streaming mode unexpectedly, and some\n    register state will be combined inconsistently, though the task will\n    be left in legitimate state from the kernel\u0026apos;s PoV.\n\n    This can only occur in unusual (but legitimate) cases where ptrace\n    has been used to set SVCR.SM after entry to the sigreturn syscall,\n    as syscall entry clears SVCR.SM.\n\n    In these cases, the the provided SVE register data will be loaded\n    into the task\u0026apos;s sve_state using the non-streaming SVE vector length\n    and the FPSIMD registers will be merged into this using the\n    streaming SVE vector length.\n\nFix (1) by setting TIF_SME when setting SVCR.SM. This also requires\nensuring that the task\u0026apos;s sme_state has been allocated, but as this could\ncontain live ZA state, it should not be zeroed. Fix (2) by clearing\nSVCR.SM when restoring a SVE signal context with SVE_SIG_FLAG_SM clear.\n\nFor consistency, I\u0026apos;ve pulled the manipulation of SVCR, TIF_SVE, TIF_SME,\nand fp_type earlier, immediately after the allocation of\nsve_state/sme_state, before the restore of the actual register state.\nThis makes it easier to ensure that these are always modified\nconsistently, even if a fault is taken while reading the register data\nfrom the signal context. I do not expect any software to depend on the\nexact state restored when a fault is taken while reading the context.(CVE-2026-23102)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix race of truncate and swap entry split\n\nThe helper for shmem swap freeing is not handling the order of swap\nentries correctly.  It uses xa_cmpxchg_irq to erase the swap entry, but it\ngets the entry order before that using xa_get_order without lock\nprotection, and it may get an outdated order value if the entry is split\nor changed in other ways after the xa_get_order and before the\nxa_cmpxchg_irq.\n\nAnd besides, the order could grow and be larger than expected, and cause\ntruncation to erase data beyond the end border.  For example, if the\ntarget entry and following entries are swapped in or freed, then a large\nfolio was added in place and swapped out, using the same entry, the\nxa_cmpxchg_irq will still succeed, it\u0026apos;s very unlikely to happen though.\n\nTo fix that, open code the Xarray cmpxchg and put the order retrieval and\nvalue checking in the same critical section.  Also, ensure the order won\u0026apos;t\nexceed the end border, skip it if the entry goes across the border.\n\nSkipping large swap entries crosses the end border is safe here.  Shmem\ntruncate iterates the range twice, in the first iteration,\nfind_lock_entries already filtered such entries, and shmem will swapin the\nentries that cross the end border and partially truncate the folio (split\nthe folio or at least zero part of it).  So in the second loop here, if we\nsee a swap entry that crosses the end order, it must at least have its\ncontent erased already.\n\nI observed random swapoff hangs and kernel panics when stress testing\nZSWAP with shmem.  After applying this patch, all problems are gone.(CVE-2026-23161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/umad: Reject negative data_len in ib_umad_write\n\nib_umad_write computes data_len from user-controlled count and the\nMAD header sizes. With a mismatched user MAD header size and RMPP\nheader length, data_len can become negative and reach ib_create_send_mad().\nThis can make the padding calculation exceed the segment size and trigger\nan out-of-bounds memset in alloc_send_rmpp_list().\n\nAdd an explicit check to reject negative data_len before creating the\nsend buffer.\n\nKASAN splat:\n[  211.363464] BUG: KASAN: slab-out-of-bounds in ib_create_send_mad+0xa01/0x11b0\n[  211.364077] Write of size 220 at addr ffff88800c3fa1f8 by task spray_thread/102\n[  211.365867] ib_create_send_mad+0xa01/0x11b0\n[  211.365887] ib_umad_write+0x853/0x1c80(CVE-2026-23243)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix memory allocation in nvme_pr_read_keys()\n\nnvme_pr_read_keys() takes num_keys from userspace and uses it to\ncalculate the allocation size for rse via struct_size(). The upper\nlimit is PR_KEYS_MAX (64K).\n\nA malicious or buggy userspace can pass a large num_keys value that\nresults in a 4MB allocation attempt at most, causing a warning in\nthe page allocator when the order exceeds MAX_PAGE_ORDER.\n\nTo fix this, use kvzalloc() instead of kzalloc().\n\nThis bug has the same reasoning and fix with the patch below:\nhttps://lore.kernel.org/linux-block/(CVE-2026-23244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: unconditionally bump set-\u0026gt;nelems before insertion\n\nIn case that the set is full, a new element gets published then removed\nwithout waiting for the RCU grace period, while RCU reader can be\nwalking over it already.\n\nTo address this issue, add the element transaction even if set is full,\nbut toggle the set_full flag to report -ENFILE so the abort path safely\nunwinds the set to its previous state.\n\nAs for element updates, decrement set-\u0026gt;nelems to restore it.\n\nA simpler fix is to call synchronize_rcu() in the error path.\nHowever, with a large batch adding elements to already maxed-out set,\nthis could cause noticeable slowdown of such batches.(CVE-2026-23272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kaweth: validate USB endpoints\n\nThe kaweth driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs\n\nWhen shrinking the number of real tx queues,\nnetif_set_real_num_tx_queues() calls qdisc_reset_all_tx_gt() to flush\nqdiscs for queues which will no longer be used.\n\nqdisc_reset_all_tx_gt() currently serializes qdisc_reset() with\nqdisc_lock(). However, for lockless qdiscs, the dequeue path is\nserialized by qdisc_run_begin/end() using qdisc-\u0026gt;seqlock instead, so\nqdisc_reset() can run concurrently with __qdisc_run() and free skbs\nwhile they are still being dequeued, leading to UAF.\n\nThis can easily be reproduced on e.g. virtio-net by imposing heavy\ntraffic while frequently changing the number of queue pairs:\n\n  iperf3 -ub0 -c $peer -t 0 \u0026amp;\n  while :; do\n    ethtool -L eth0 combined 1\n    ethtool -L eth0 combined 2\n  done\n\nWith KASAN enabled, this leads to reports like:\n\n  BUG: KASAN: slab-use-after-free in __qdisc_run+0x133f/0x1760\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   __qdisc_run+0x133f/0x1760\n   __dev_queue_xmit+0x248f/0x3550\n   ip_finish_output2+0xa42/0x2110\n   ip_output+0x1a7/0x410\n   ip_send_skb+0x2e6/0x480\n   udp_send_skb+0xb0a/0x1590\n   udp_sendmsg+0x13c9/0x1fc0\n   ...\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 1270 on cpu 5 at 44.558414s:\n   ...\n   alloc_skb_with_frags+0x84/0x7c0\n   sock_alloc_send_pskb+0x69a/0x830\n   __ip_append_data+0x1b86/0x48c0\n   ip_make_skb+0x1e8/0x2b0\n   udp_sendmsg+0x13a6/0x1fc0\n   ...\n\n  Freed by task 1306 on cpu 3 at 44.558445s:\n   ...\n   kmem_cache_free+0x117/0x5e0\n   pfifo_fast_reset+0x14d/0x580\n   qdisc_reset+0x9e/0x5f0\n   netif_set_real_num_tx_queues+0x303/0x840\n   virtnet_set_channels+0x1bf/0x260 [virtio_net]\n   ethnl_set_channels+0x684/0xae0\n   ethnl_default_set_doit+0x31a/0x890\n   ...\n\nSerialize qdisc_reset_all_tx_gt() against the lockless dequeue path by\ntaking qdisc-\u0026gt;seqlock for TCQ_F_NOLOCK qdiscs, matching the\nserialization model already used by dev_reset_queue().\n\nAdditionally clear QDISC_STATE_NON_EMPTY after reset so the qdisc state\nreflects an empty queue, avoiding needless re-scheduling.(CVE-2026-23340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check\n\ncdc_ncm_rx_verify_ndp16() validates that the NDP header and its DPE\nentries fit within the skb. The first check correctly accounts for\nndpoffset:\n\n  if ((ndpoffset + sizeof(struct usb_cdc_ncm_ndp16)) \u0026gt; skb_in-\u0026gt;len)\n\nbut the second check omits it:\n\n  if ((sizeof(struct usb_cdc_ncm_ndp16) +\n       ret * (sizeof(struct usb_cdc_ncm_dpe16))) \u0026gt; skb_in-\u0026gt;len)\n\nThis validates the DPE array size against the total skb length as if\nthe NDP were at offset 0, rather than at ndpoffset. When the NDP is\nplaced near the end of the NTB (large wNdpIndex), the DPE entries can\nextend past the skb data buffer even though the check passes.\ncdc_ncm_rx_fixup() then reads out-of-bounds memory when iterating\nthe DPE array.\n\nAdd ndpoffset to the nframes bounds check and use struct_size_t() to\nexpress the NDP-plus-DPE-array size more clearly.(CVE-2026-23448)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2026-23473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix krb5 mount with username option\n\nCustomer reported that some of their krb5 mounts were failing against\na single server as the client was trying to mount the shares with\nwrong credentials.  It turned out the client was reusing SMB session\nfrom first mount to try mounting the other shares, even though a\ndifferent username= option had been specified to the other mounts.\n\nBy using username mount option along with sec=krb5 to search for\nprincipals from keytab is supported by cifs.upcall(8) since\ncifs-utils-4.8.  So fix this by matching username mount option in\nmatch_session() even with Kerberos.\n\nFor example, the second mount below should fail with -ENOKEY as there\nis no \u0026apos;foobar\u0026apos; principal in keytab (/etc/krb5.keytab).  The client\nends up reusing SMB session from first mount to perform the second\none, which is wrong.\n\n```\n$ ktutil\nktutil:  add_entry -password -p testuser -k 1 -e aes256-cts\nPassword for (CVE-2026-31392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/rmap: fix incorrect pte restoration for lazyfree folios\n\nWe batch unmap anonymous lazyfree folios by folio_unmap_pte_batch.  If the\nbatch has a mix of writable and non-writable bits, we may end up setting\nthe entire batch writable.  Fix this by respecting writable bit during\nbatching.\n\nAlthough on a successful unmap of a lazyfree folio, the soft-dirty bit is\nlost, preserve it on pte restoration by respecting the bit during\nbatching, to make the fix consistent w.r.t both writable bit and\nsoft-dirty bit.\n\nI was able to write the below reproducer and crash the kernel. \nExplanation of reproducer (set 64K mTHP to always):\n\nFault in a 64K large folio.  Split the VMA at mid-point with\nMADV_DONTFORK.  fork() - parent points to the folio with 8 writable ptes\nand 8 non-writable ptes.  Merge the VMAs with MADV_DOFORK so that\nfolio_unmap_pte_batch() can determine all the 16 ptes as a batch.  Do\nMADV_FREE on the range to mark the folio as lazyfree.  Write to the memory\nto dirty the pte, eventually rmap will dirty the folio.  Then trigger\nreclaim, we will hit the pte restoration path, and the kernel will crash\nwith the trace given below.\n\nThe BUG happens at:\n\n\tBUG_ON(atomic_inc_return(\u0026amp;ptc-\u0026gt;anon_map_count) \u0026gt; 1 \u0026amp;\u0026amp; rw);\n\nThe code path is asking for anonymous page to be mapped writable into the\npagetable.  The BUG_ON() firing implies that such a writable page has been\nmapped into the pagetables of more than one process, which breaks\nanonymous memory/CoW semantics.\n\n[   21.134473] kernel BUG at mm/page_table_check.c:118!\n[   21.134497] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[   21.135917] Modules linked in:\n[   21.136085] CPU: 1 UID: 0 PID: 1735 Comm: dup-lazyfree Not tainted 7.0.0-rc1-00116-g018018a17770 #1028 PREEMPT\n[   21.136858] Hardware name: linux,dummy-virt (DT)\n[   21.137019] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[   21.137308] pc : page_table_check_set+0x28c/0x2a8\n[   21.137607] lr : page_table_check_set+0x134/0x2a8\n[   21.137885] sp : ffff80008a3b3340\n[   21.138124] x29: ffff80008a3b3340 x28: fffffdffc3d14400 x27: ffffd1a55e03d000\n[   21.138623] x26: 0040000000000040 x25: ffffd1a55f7dd000 x24: 0000000000000001\n[   21.139045] x23: 0000000000000001 x22: 0000000000000001 x21: ffffd1a55f217f30\n[   21.139629] x20: 0000000000134521 x19: 0000000000134519 x18: 005c43e000040000\n[   21.140027] x17: 0001400000000000 x16: 0001700000000000 x15: 000000000000ffff\n[   21.140578] x14: 000000000000000c x13: 005c006000000000 x12: 0000000000000020\n[   21.140828] x11: 0000000000000000 x10: 005c000000000000 x9 : ffffd1a55c079ee0\n[   21.141077] x8 : 0000000000000001 x7 : 005c03e000040000 x6 : 000000004000ffff\n[   21.141490] x5 : ffff00017fffce00 x4 : 0000000000000001 x3 : 0000000000000002\n[   21.141741] x2 : 0000000000134510 x1 : 0000000000000000 x0 : ffff0000c08228c0\n[   21.141991] Call trace:\n[   21.142093]  page_table_check_set+0x28c/0x2a8 (P)\n[   21.142265]  __page_table_check_ptes_set+0x144/0x1e8\n[   21.142441]  __set_ptes_anysz.constprop.0+0x160/0x1a8\n[   21.142766]  contpte_set_ptes+0xe8/0x140\n[   21.142907]  try_to_unmap_one+0x10c4/0x10d0\n[   21.143177]  rmap_walk_anon+0x100/0x250\n[   21.143315]  try_to_unmap+0xa0/0xc8\n[   21.143441]  shrink_folio_list+0x59c/0x18a8\n[   21.143759]  shrink_lruvec+0x664/0xbf0\n[   21.144043]  shrink_node+0x218/0x878\n[   21.144285]  __node_reclaim.constprop.0+0x98/0x338\n[   21.144763]  user_proactive_reclaim+0x2a4/0x340\n[   21.145056]  reclaim_store+0x3c/0x60\n[   21.145216]  dev_attr_store+0x20/0x40\n[   21.145585]  sysfs_kf_write+0x84/0xa8\n[   21.145835]  kernfs_fop_write_iter+0x130/0x1c8\n[   21.145994]  vfs_write+0x2b8/0x368\n[   21.146119]  ksys_write+0x70/0x110\n[   21.146240]  __arm64_sys_write+0x24/0x38\n[   21.146380]  invoke_syscall+0x50/0x120\n[   21.146513]  el0_svc_common.constprop.0+0x48/0xf8\n[   21.146679]  do_el0_svc+0x28/0x40\n[   21.146798]  el0_svc+0x34/0x110\n[   21.146926]  el0t\n---truncated---(CVE-2026-31398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_fw: fix NULL pointer dereference on shared blocks\n\nThe old-method path in fw_classify() calls tcf_block_q() and\ndereferences q-\u0026gt;handle.  Shared blocks leave block-\u0026gt;q NULL, causing a\nNULL deref when an empty cls_fw filter is attached to a shared block\nand a packet with a nonzero major skb mark is classified.\n\nReject the configuration in fw_change() when the old method (no\nTCA_OPTIONS) is used on a shared block, since fw_classify()\u0026apos;s\nold-method path needs block-\u0026gt;q which is NULL for shared blocks.\n\nThe fixed null-ptr-deref calling stack:\n KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\n RIP: 0010:fw_classify (net/sched/cls_fw.c:81)\n Call Trace:\n  tcf_classify (./include/net/tc_wrapper.h:197 net/sched/cls_api.c:1764 net/sched/cls_api.c:1860)\n  tc_run (net/core/dev.c:4401)\n  __dev_queue_xmit (net/core/dev.c:4535 net/core/dev.c:4790)(CVE-2026-31421)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_flow: fix NULL pointer dereference on shared blocks\n\nflow_change() calls tcf_block_q() and dereferences q-\u0026gt;handle to derive\na default baseclass.  Shared blocks leave block-\u0026gt;q NULL, causing a NULL\nderef when a flow filter without a fully qualified baseclass is created\non a shared block.\n\nCheck tcf_block_shared() before accessing block-\u0026gt;q and return -EINVAL\nfor shared blocks.  This avoids the null-deref shown below:\n\n=======================================================================\nKASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\nRIP: 0010:flow_change (net/sched/cls_flow.c:508)\nCall Trace:\n tc_new_tfilter (net/sched/cls_api.c:2432)\n rtnetlink_rcv_msg (net/core/rtnetlink.c:6980)\n [...]\n=======================================================================(CVE-2026-31422)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skb: fix cross-cache free of KFENCE-allocated skb head\n\nSKB_SMALL_HEAD_CACHE_SIZE is intentionally set to a non-power-of-2\nvalue (e.g. 704 on x86_64) to avoid collisions with generic kmalloc\nbucket sizes. This ensures that skb_kfree_head() can reliably use\nskb_end_offset to distinguish skb heads allocated from\nskb_small_head_cache vs. generic kmalloc caches.\n\nHowever, when KFENCE is enabled, kfence_ksize() returns the exact\nrequested allocation size instead of the slab bucket size. If a caller\n(e.g. bpf_test_init) allocates skb head data via kzalloc() and the\nrequested size happens to equal SKB_SMALL_HEAD_CACHE_SIZE, then\nslab_build_skb() -\u0026gt; ksize() returns that exact value. After subtracting\nskb_shared_info overhead, skb_end_offset ends up matching\nSKB_SMALL_HEAD_HEADROOM, causing skb_kfree_head() to incorrectly free\nthe object to skb_small_head_cache instead of back to the original\nkmalloc cache, resulting in a slab cross-cache free:\n\n  kmem_cache_free(skbuff_small_head): Wrong slab cache. Expected\n  skbuff_small_head but got kmalloc-1k\n\nFix this by always calling kfree(head) in skb_kfree_head(). This keeps\nthe free path generic and avoids allocator-specific misclassification\nfor KFENCE objects.(CVE-2026-31429)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nX.509: Fix out-of-bounds access when parsing extensions\n\nLeo reports an out-of-bounds access when parsing a certificate with\nempty Basic Constraints or Key Usage extension because the first byte of\nthe extension is read before checking its length.  Fix it.\n\nThe bug can be triggered by an unprivileged user by submitting a\nspecially crafted certificate to the kernel through the keyrings(7) API.\nLeo has demonstrated this with a proof-of-concept program responsibly\ndisclosed off-list.(CVE-2026-31430)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix memory leak when a wq is reset\n\nidxd_wq_disable_cleanup() which is called from the reset path for a\nworkqueue, sets the wq type to NONE, which for other parts of the\ndriver mean that the wq is empty (all its resources were released).\n\nOnly set the wq type to NONE after its resources are released.(CVE-2026-31441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix possible invalid memory access after FLR\n\nIn the case that the first Function Level Reset (FLR) concludes\ncorrectly, but in the second FLR the scratch area for the saved\nconfiguration cannot be allocated, it\u0026apos;s possible for a invalid memory\naccess to happen.\n\nAlways set the deallocated scratch area to NULL after FLR completes.(CVE-2026-31442)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix use-after-free in update_super_work when racing with umount\n\nCommit b98535d09179 (\u0026quot;ext4: fix bug_on in start_this_handle during umount\nfilesystem\u0026quot;) moved ext4_unregister_sysfs() before flushing s_sb_upd_work\nto prevent new error work from being queued via /proc/fs/ext4/xx/mb_groups\nreads during unmount. However, this introduced a use-after-free because\nupdate_super_work calls ext4_notify_error_sysfs() -\u0026gt; sysfs_notify() which\naccesses the kobject\u0026apos;s kernfs_node after it has been freed by kobject_del()\nin ext4_unregister_sysfs():\n\n  update_super_work                ext4_put_super\n  -----------------                --------------\n                                   ext4_unregister_sysfs(sb)\n                                     kobject_del(\u0026amp;sbi-\u0026gt;s_kobj)\n                                       __kobject_del()\n                                         sysfs_remove_dir()\n                                           kobj-\u0026gt;sd = NULL\n                                         sysfs_put(sd)\n                                           kernfs_put()  // RCU free\n  ext4_notify_error_sysfs(sbi)\n    sysfs_notify(\u0026amp;sbi-\u0026gt;s_kobj)\n      kn = kobj-\u0026gt;sd              // stale pointer\n      kernfs_get(kn)             // UAF on freed kernfs_node\n                                   ext4_journal_destroy()\n                                     flush_work(\u0026amp;sbi-\u0026gt;s_sb_upd_work)\n\nInstead of reordering the teardown sequence, fix this by making\next4_notify_error_sysfs() detect that sysfs has already been torn down\nby checking s_kobj.state_in_sysfs, and skipping the sysfs_notify() call\nin that case. A dedicated mutex (s_error_notify_mutex) serializes\next4_notify_error_sysfs() against kobject_del() in ext4_unregister_sysfs()\nto prevent TOCTOU races where the kobject could be deleted between the\nstate_in_sysfs check and the sysfs_notify() call.(CVE-2026-31446)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: validate p_idx bounds in ext4_ext_correct_indexes\n\next4_ext_correct_indexes() walks up the extent tree correcting\nindex entries when the first extent in a leaf is modified. Before\naccessing path[k].p_idx-\u0026gt;ei_block, there is no validation that\np_idx falls within the valid range of index entries for that\nlevel.\n\nIf the on-disk extent header contains a corrupted or crafted\neh_entries value, p_idx can point past the end of the allocated\nbuffer, causing a slab-out-of-bounds read.\n\nFix this by validating path[k].p_idx against EXT_LAST_INDEX() at\nboth access sites: before the while loop and inside it. Return\n-EFSCORRUPTED if the index pointer is out of range, consistent\nwith how other bounds violations are handled in the ext4 extent\ntree code.(CVE-2026-31449)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: publish jinode after initialization\n\next4_inode_attach_jinode() publishes ei-\u0026gt;jinode to concurrent users.\nIt used to set ei-\u0026gt;jinode before jbd2_journal_init_jbd_inode(),\nallowing a reader to observe a non-NULL jinode with i_vfs_inode\nstill unset.\n\nThe fast commit flush path can then pass this jinode to\njbd2_wait_inode_data(), which dereferences i_vfs_inode-\u0026gt;i_mapping and\nmay crash.\n\nBelow is the crash I observe:\n```\nBUG: unable to handle page fault for address: 000000010beb47f4\nPGD 110e51067 P4D 110e51067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\nRIP: 0010:xas_find_marked+0x3d/0x2e0\nCode: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f \u0026lt;49\u0026gt; 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02\nRSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246\nRAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003\nRDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10\nRBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec\nR10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000\nR13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88\nFS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;TASK\u0026gt;\nfilemap_get_folios_tag+0x87/0x2a0\n__filemap_fdatawait_range+0x5f/0xd0\n? srso_alias_return_thunk+0x5/0xfbef5\n? __schedule+0x3e7/0x10c0\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? cap_safe_nice+0x37/0x70\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\nfilemap_fdatawait_range_keep_errors+0x12/0x40\next4_fc_commit+0x697/0x8b0\n? ext4_file_write_iter+0x64b/0x950\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? vfs_write+0x356/0x480\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\next4_sync_file+0xf7/0x370\ndo_fsync+0x3b/0x80\n? syscall_trace_enter+0x108/0x1d0\n__x64_sys_fdatasync+0x16/0x20\ndo_syscall_64+0x62/0x2c0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\n...\n```\n\nFix this by initializing the jbd2_inode first.\nUse smp_wmb() and WRITE_ONCE() to publish ei-\u0026gt;jinode after\ninitialization. Readers use READ_ONCE() to fetch the pointer.(CVE-2026-31450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: replace BUG_ON with proper error handling in ext4_read_inline_folio\n\nReplace BUG_ON() with proper error handling when inline data size\nexceeds PAGE_SIZE. This prevents kernel panic and allows the system to\ncontinue running while properly reporting the filesystem corruption.\n\nThe error is logged via ext4_error_inode(), the buffer head is released\nto prevent memory leak, and -EFSCORRUPTED is returned to indicate\nfilesystem corruption.(CVE-2026-31451)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: convert inline data to extents when truncate exceeds inline size\n\nAdd a check in ext4_setattr() to convert files from inline data storage\nto extent-based storage when truncate() grows the file size beyond the\ninline capacity. This prevents the filesystem from entering an\ninconsistent state where the inline data flag is set but the file size\nexceeds what can be stored inline.\n\nWithout this fix, the following sequence causes a kernel BUG_ON():\n\n1. Mount filesystem with inode that has inline flag set and small size\n2. truncate(file, 50MB) - grows size but inline flag remains set\n3. sendfile() attempts to write data\n4. ext4_write_inline_data() hits BUG_ON(write_size \u0026gt; inline_capacity)\n\nThe crash occurs because ext4_write_inline_data() expects inline storage\nto accommodate the write, but the actual inline capacity (~60 bytes for\ni_block + ~96 bytes for xattrs) is far smaller than the file size and\nwrite request.\n\nThe fix checks if the new size from setattr exceeds the inode\u0026apos;s actual\ninline capacity (EXT4_I(inode)-\u0026gt;i_inline_size) and converts the file to\nextent-based storage before proceeding with the size change.\n\nThis addresses the root cause by ensuring the inline data flag and file\nsize remain consistent during truncate operations.(CVE-2026-31452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: add GFP_NOIO in the bio completion if needed\n\nThe bio completion path in the process context (e.g. dm-verity)\nwill directly call into decompression rather than trigger another\nworkqueue context for minimal scheduling latencies, which can\nthen call vm_map_ram() with GFP_KERNEL.\n\nDue to insufficient memory, vm_map_ram() may generate memory\nswapping I/O, which can cause submit_bio_wait to deadlock\nin some scenarios.\n\nTrimmed down the call stack, as follows:\n\nf2fs_submit_read_io\n  submit_bio                      //bio_list is initialized.\n    mmc_blk_mq_recovery\n      z_erofs_endio\n        vm_map_ram\n          __pte_alloc_kernel\n            __alloc_pages_direct_reclaim\n              shrink_folio_list\n                __swap_writepage\n                  submit_bio_wait  //bio_list is non-NULL, hang!!!\n\nUse memalloc_noio_{save,restore}() to wrap up this path.(CVE-2026-31467)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n\nA UAF issue occurs when the virtio_net driver is configured with napi_tx=N\nand the device\u0026apos;s IFF_XMIT_DST_RELEASE flag is cleared\n(e.g., during the configuration of tc route filter rules).\n\nWhen IFF_XMIT_DST_RELEASE is removed from the net_device, the network stack\nexpects the driver to hold the reference to skb-\u0026gt;dst until the packet\nis fully transmitted and freed. In virtio_net with napi_tx=N,\nskbs may remain in the virtio transmit ring for an extended period.\n\nIf the network namespace is destroyed while these skbs are still pending,\nthe corresponding dst_ops structure has freed. When a subsequent packet\nis transmitted, free_old_xmit() is triggered to clean up old skbs.\nIt then calls dst_release() on the skb associated with the stale dst_entry.\nSince the dst_ops (referenced by the dst_entry) has already been freed,\na UAF kernel paging request occurs.\n\nfix it by adds skb_dst_drop(skb) in start_xmit to explicitly release\nthe dst reference before the skb is queued in virtio_net.\n\nCall Trace:\n Unable to handle kernel paging request at virtual address ffff80007e150000\n CPU: 2 UID: 0 PID: 6236 Comm: ping Kdump: loaded Not tainted 7.0.0-rc1+ #6 PREEMPT\n  ...\n  percpu_counter_add_batch+0x3c/0x158 lib/percpu_counter.c:98 (P)\n  dst_release+0xe0/0x110  net/core/dst.c:177\n  skb_release_head_state+0xe8/0x108 net/core/skbuff.c:1177\n  sk_skb_reason_drop+0x54/0x2d8 net/core/skbuff.c:1255\n  dev_kfree_skb_any_reason+0x64/0x78 net/core/dev.c:3469\n  napi_consume_skb+0x1c4/0x3a0 net/core/skbuff.c:1527\n  __free_old_xmit+0x164/0x230  drivers/net/virtio_net.c:611 [virtio_net]\n  free_old_xmit drivers/net/virtio_net.c:1081 [virtio_net]\n  start_xmit+0x7c/0x530 drivers/net/virtio_net.c:3329 [virtio_net]\n  ...\n\nReproduction Steps:\nNETDEV=\u0026quot;enp3s0\u0026quot;\n\nconfig_qdisc_route_filter() {\n    tc qdisc del dev $NETDEV root\n    tc qdisc add dev $NETDEV root handle 1: prio\n    tc filter add dev $NETDEV parent 1:0 \\\n\tprotocol ip prio 100 route to 100 flowid 1:1\n    ip route add 192.168.1.100/32 dev $NETDEV realm 100\n}\n\ntest_ns() {\n    ip netns add testns\n    ip link set $NETDEV netns testns\n    ip netns exec testns ifconfig $NETDEV  10.0.32.46/24\n    ip netns exec testns ping -c 1 10.0.32.1\n    ip netns del testns\n}\n\nconfig_qdisc_route_filter\n\ntest_ns\nsleep 2\ntest_ns(CVE-2026-31469)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: use generic driver_override infrastructure\n\nWhen a driver is probed through __driver_attach(), the bus\u0026apos; match()\ncallback is called without the device lock held, thus accessing the\ndriver_override field without a lock, which can cause a UAF.\n\nFix this by using the driver-core driver_override infrastructure taking\ncare of proper locking internally.\n\nNote that calling match() from __driver_attach() without the device lock\nheld is intentional. [1]\n\nAlso note that we do not enable the driver_override feature of struct\nbus_type, as SPI - in contrast to most other buses - passes \u0026quot;\u0026quot; to\nsysfs_emit() when the driver_override pointer is NULL. Thus, printing\n\u0026quot;\\n\u0026quot; instead of \u0026quot;(null)\\n\u0026quot;.(CVE-2026-31487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: use netlink policy range checks\n\nReplace manual range and mask validations with netlink policy\nannotations in ctnetlink code paths, so that the netlink core rejects\ninvalid values early and can generate extack errors.\n\n- CTA_PROTOINFO_TCP_STATE: reject values \u0026gt; TCP_CONNTRACK_SYN_SENT2 at\n  policy level, removing the manual \u0026gt;= TCP_CONNTRACK_MAX check.\n- CTA_PROTOINFO_TCP_WSCALE_ORIGINAL/REPLY: reject values \u0026gt; TCP_MAX_WSCALE\n  (14). The normal TCP option parsing path already clamps to this value,\n  but the ctnetlink path accepted 0-255, causing undefined behavior when\n  used as a u32 shift count.\n- CTA_FILTER_ORIG_FLAGS/REPLY_FLAGS: use NLA_POLICY_MASK with\n  CTA_FILTER_F_ALL, removing the manual mask checks.\n- CTA_EXPECT_FLAGS: use NLA_POLICY_MASK with NF_CT_EXPECT_MASK, adding\n  a new mask define grouping all valid expect flags.\n\nExtracted from a broader nf-next patch by Florian Westphal, scoped to\nctnetlink for the fixes tree.(CVE-2026-31495)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conntrack_expect: skip expectations in other netns via proc\n\nSkip expectations that do not reside in this netns.\n\nSimilar to e77e6ff502ea (\u0026quot;netfilter: conntrack: do not dump other netns\u0026apos;s\nconntrack entries via proc\u0026quot;).(CVE-2026-31496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop\n\nl2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED\nstate to support L2CAP reconfiguration (e.g. MTU changes). However,\nsince both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from\nthe initial configuration, the reconfiguration path falls through to\nl2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and\nretrans_list without freeing the previous allocations and sets\nchan-\u0026gt;sdu to NULL without freeing the existing skb. This leaks all\npreviously allocated ERTM resources.\n\nAdditionally, l2cap_parse_conf_req() does not validate the minimum\nvalue of remote_mps derived from the RFC max_pdu_size option. A zero\nvalue propagates to l2cap_segment_sdu() where pdu_len becomes zero,\ncausing the while loop to never terminate since len is never\ndecremented, exhausting all available memory.\n\nFix the double-init by skipping l2cap_ertm_init() and\nl2cap_chan_ready() when the channel is already in BT_CONNECTED state,\nwhile still allowing the reconfiguration parameters to be updated\nthrough l2cap_parse_conf_req(). Also add a pdu_len zero check in\nl2cap_segment_sdu() as a safeguard.(CVE-2026-31498)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix deadlock in l2cap_conn_del()\n\nl2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer\nand id_addr_timer while holding conn-\u0026gt;lock. However, the work functions\nl2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire\nconn-\u0026gt;lock, creating a potential AB-BA deadlock if the work is already\nexecuting when l2cap_conn_del() takes the lock.\n\nMove the work cancellations before acquiring conn-\u0026gt;lock and use\ndisable_delayed_work_sync() to additionally prevent the works from\nbeing rearmed after cancellation, consistent with the pattern used in\nhci_conn_del().(CVE-2026-31499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix out-of-bounds writes in iavf_get_ethtool_stats()\n\niavf incorrectly uses real_num_tx_queues for ETH_SS_STATS. Since the\nvalue could change in runtime, we should use num_tx_queues instead.\n\nMoreover iavf_get_ethtool_stats() uses num_active_queues while\niavf_get_sset_count() and iavf_get_stat_strings() use\nreal_num_tx_queues, which triggers out-of-bounds writes when we do\n\u0026quot;ethtool -L\u0026quot; and \u0026quot;ethtool -S\u0026quot; simultaneously [1].\n\nFor example when we change channels from 1 to 8, Thread 3 could be\nscheduled before Thread 2, and out-of-bounds writes could be triggered\nin Thread 3:\n\nThread 1 (ethtool -L)       Thread 2 (work)        Thread 3 (ethtool -S)\niavf_set_channels()\n...\niavf_alloc_queues()\n-\u0026gt; num_active_queues = 8\niavf_schedule_finish_config()\n                                                   iavf_get_sset_count()\n                                                   real_num_tx_queues: 1\n                                                   -\u0026gt; buffer for 1 queue\n                                                   iavf_get_ethtool_stats()\n                                                   num_active_queues: 8\n                                                   -\u0026gt; out-of-bounds!\n                            iavf_finish_config()\n                            -\u0026gt; real_num_tx_queues = 8\n\nUse immutable num_tx_queues in all related functions to avoid the issue.\n\n[1]\n BUG: KASAN: vmalloc-out-of-bounds in iavf_add_one_ethtool_stat+0x200/0x270\n Write of size 8 at addr ffffc900031c9080 by task ethtool/5800\n\n CPU: 1 UID: 0 PID: 5800 Comm: ethtool Not tainted 6.19.0-enjuk-08403-g8137e3db7f1c #241 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x6f/0xb0\n  print_report+0x170/0x4f3\n  kasan_report+0xe1/0x180\n  iavf_add_one_ethtool_stat+0x200/0x270\n  iavf_get_ethtool_stats+0x14c/0x2e0\n  __dev_ethtool+0x3d0c/0x5830\n  dev_ethtool+0x12d/0x270\n  dev_ioctl+0x53c/0xe30\n  sock_do_ioctl+0x1a9/0x270\n  sock_ioctl+0x3d4/0x5e0\n  __x64_sys_ioctl+0x137/0x1c0\n  do_syscall_64+0xf3/0x690\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n RIP: 0033:0x7f7da0e6e36d\n ...\n  \u0026lt;/TASK\u0026gt;\n\n The buggy address belongs to a 1-page vmalloc region starting at 0xffffc900031c9000 allocated at __dev_ethtool+0x3cc9/0x5830\n The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000\n index:0xffff88813a013de0 pfn:0x13a013\n flags: 0x200000000000000(node=0|zone=2)\n raw: 0200000000000000 0000000000000000 dead000000000122 0000000000000000\n raw: ffff88813a013de0 0000000000000000 00000001ffffffff 0000000000000000\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffffc900031c8f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n \u0026gt;ffffc900031c9080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n                    ^\n  ffffc900031c9100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9180: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8(CVE-2026-31505)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb\n\nBefore using sk pointer, check if it is null.\n\nFix the following:\n\n KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267]\n CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025\n Workqueue: events l2cap_info_timeout\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n veth0_macvtap: entered promiscuous mode\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __kasan_check_byte+0x12/0x40\n  lock_acquire+0x79/0x2e0\n  lock_sock_nested+0x48/0x100\n  ? l2cap_sock_ready_cb+0x46/0x160\n  l2cap_sock_ready_cb+0x46/0x160\n  l2cap_conn_start+0x779/0xff0\n  ? __pfx_l2cap_conn_start+0x10/0x10\n  ? l2cap_info_timeout+0x60/0xa0\n  ? __pfx___mutex_lock+0x10/0x10\n  l2cap_info_timeout+0x68/0xa0\n  ? process_scheduled_works+0xa8d/0x18c0\n  process_scheduled_works+0xb6e/0x18c0\n  ? __pfx_process_scheduled_works+0x10/0x10\n  ? assign_work+0x3d5/0x5e0\n  worker_thread+0xa53/0xfc0\n  kthread+0x388/0x470\n  ? __pfx_worker_thread+0x10/0x10\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x51e/0xb90\n  ? __pfx_ret_from_fork+0x10/0x10\n veth1_macvtap: entered promiscuous mode\n  ? __switch_to+0xc7d/0x1450\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\n Modules linked in:\n ---[ end trace 0000000000000000 ]---\n batman_adv: batadv0: Interface activated: batadv_slave_0\n batman_adv: batadv0: Interface activated: batadv_slave_1\n netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n ieee80211 phy39: Selected rate control algorithm \u0026apos;minstrel_ht\u0026apos;\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Kernel panic - not syncing: Fatal exception(CVE-2026-31510)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete\n\nThis fixes the condition checking so mgmt_pending_valid is executed\nwhenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd)\nwould kfree(cmd) without unlinking it from the list first, leaving a\ndangling pointer. Any subsequent list traversal (e.g.,\nmgmt_pending_foreach during __mgmt_power_off, or another\nmgmt_pending_valid call) would dereference freed memory.(CVE-2026-31511)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n\nl2cap_ecred_data_rcv() reads the SDU length field from skb-\u0026gt;data using\nget_unaligned_le16() without first verifying that skb contains at least\nL2CAP_SDULEN_SIZE (2) bytes. When skb-\u0026gt;len is less than 2, this reads\npast the valid data in the skb.\n\nThe ERTM reassembly path correctly calls pskb_may_pull() before reading\nthe SDU length (l2cap_reassemble_sdu, L2CAP_SAR_START case). Apply the\nsame validation to the Enhanced Credit Based Flow Control data path.(CVE-2026-31512)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: prevent policy_hthresh.work from racing with netns teardown\n\nA XFRM_MSG_NEWSPDINFO request can queue the per-net work item\npolicy_hthresh.work onto the system workqueue.\n\nThe queued callback, xfrm_hash_rebuild(), retrieves the enclosing\nstruct net via container_of(). If the net namespace is torn down\nbefore that work runs, the associated struct net may already have\nbeen freed, and xfrm_hash_rebuild() may then dereference stale memory.\n\nxfrm_policy_fini() already flushes policy_hash_work during teardown,\nbut it does not synchronize policy_hthresh.work.\n\nSynchronize policy_hthresh.work in xfrm_policy_fini() as well, so the\nqueued work cannot outlive the net namespace teardown and access a\nfreed struct net.(CVE-2026-31516)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nesp: fix skb leak with espintcp and async crypto\n\nWhen the TX queue for espintcp is full, esp_output_tail_tcp will\nreturn an error and not free the skb, because with synchronous crypto,\nthe common xfrm output code will drop the packet for us.\n\nWith async crypto (esp_output_done), we need to drop the skb when\nesp_output_tail_tcp returns an error.(CVE-2026-31518)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN\n\nThe BPF interpreter\u0026apos;s signed 32-bit division and modulo handlers use\nthe kernel abs() macro on s32 operands. The abs() macro documentation\n(include/linux/math.h) explicitly states the result is undefined when\nthe input is the type minimum. When DST contains S32_MIN (0x80000000),\nabs((s32)DST) triggers undefined behavior and returns S32_MIN unchanged\non arm64/x86. This value is then sign-extended to u64 as\n0xFFFFFFFF80000000, causing do_div() to compute the wrong result.\n\nThe verifier\u0026apos;s abstract interpretation (scalar32_min_max_sdiv) computes\nthe mathematically correct result for range tracking, creating a\nverifier/interpreter mismatch that can be exploited for out-of-bounds\nmap value access.\n\nIntroduce abs_s32() which handles S32_MIN correctly by casting to u32\nbefore negating, avoiding signed overflow entirely. Replace all 8\nabs((s32)...) call sites in the interpreter\u0026apos;s sdiv32/smod32 handlers.\n\ns32 is the only affected case -- the s64 division/modulo handlers do\nnot use abs().(CVE-2026-31525)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Make sure to use pmu_ctx-\u0026gt;pmu for groups\n\nOliver reported that x86_pmu_del() ended up doing an out-of-bound memory access\nwhen group_sched_in() fails and needs to roll back.\n\nThis *should* be handled by the transaction callbacks, but he found that when\nthe group leader is a software event, the transaction handlers of the wrong PMU\nare used. Despite the move_group case in perf_event_open() and group_sched_in()\nusing pmu_ctx-\u0026gt;pmu.\n\nTurns out, inherit uses event-\u0026gt;pmu to clone the events, effectively undoing the\nmove_group case for all inherited contexts. Fix this by also making inherit use\npmu_ctx-\u0026gt;pmu, ensuring all inherited counters end up in the same pmu context.\n\nSimilarly, __perf_event_read() should use equally use pmu_ctx-\u0026gt;pmu for the\ngroup case.(CVE-2026-31528)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw: fix ro-\u0026gt;uniq use-after-free in raw_rcv()\n\nraw_release() unregisters raw CAN receive filters via can_rx_unregister(),\nbut receiver deletion is deferred with call_rcu(). This leaves a window\nwhere raw_rcv() may still be running in an RCU read-side critical section\nafter raw_release() frees ro-\u0026gt;uniq, leading to a use-after-free of the\npercpu uniq storage.\n\nMove free_percpu(ro-\u0026gt;uniq) out of raw_release() and into a raw-specific\nsocket destructor. can_rx_unregister() takes an extra reference to the\nsocket and only drops it from the RCU callback, so freeing uniq from\nsk_destruct ensures the percpu area is not released until the relevant\ncallbacks have drained.\n\n[mkl: applied manually](CVE-2026-31532)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: fix use-after-free in -EBUSY error path of tls_do_encryption\n\nThe -EBUSY handling in tls_do_encryption(), introduced by commit\n859054147318 (\u0026quot;net: tls: handle backlogging of crypto requests\u0026quot;), has\na use-after-free due to double cleanup of encrypt_pending and the\nscatterlist entry.\n\nWhen crypto_aead_encrypt() returns -EBUSY, the request is enqueued to\nthe cryptd backlog and the async callback tls_encrypt_done() will be\ninvoked upon completion. That callback unconditionally restores the\nscatterlist entry (sge-\u0026gt;offset, sge-\u0026gt;length) and decrements\nctx-\u0026gt;encrypt_pending. However, if tls_encrypt_async_wait() returns an\nerror, the synchronous error path in tls_do_encryption() performs the\nsame cleanup again, double-decrementing encrypt_pending and\ndouble-restoring the scatterlist.\n\nThe double-decrement corrupts the encrypt_pending sentinel (initialized\nto 1), making tls_encrypt_async_wait() permanently skip the wait for\npending async callbacks. A subsequent sendmsg can then free the\ntls_rec via bpf_exec_tx_verdict() while a cryptd callback is still\npending, resulting in a use-after-free when the callback fires on the\nfreed record.\n\nFix this by skipping the synchronous cleanup when the -EBUSY async\nwait returns an error, since the callback has already handled\nencrypt_pending and sge restoration.(CVE-2026-31533)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gt: Check set_default_submission() before deferencing\n\nWhen the i915 driver firmware binaries are not present, the\nset_default_submission pointer is not set. This pointer is\ndereferenced during suspend anyways.\n\nAdd a check to make sure it is set before dereferencing.\n\n[   23.289926] PM: suspend entry (deep)\n[   23.293558] Filesystems sync: 0.000 seconds\n[   23.298010] Freezing user space processes\n[   23.302771] Freezing user space processes completed (elapsed 0.000 seconds)\n[   23.309766] OOM killer disabled.\n[   23.313027] Freezing remaining freezable tasks\n[   23.318540] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)\n[   23.342038] serial 00:05: disabled\n[   23.345719] serial 00:02: disabled\n[   23.349342] serial 00:01: disabled\n[   23.353782] sd 0:0:0:0: [sda] Synchronizing SCSI cache\n[   23.358993] sd 1:0:0:0: [sdb] Synchronizing SCSI cache\n[   23.361635] ata1.00: Entering standby power mode\n[   23.368863] ata2.00: Entering standby power mode\n[   23.445187] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[   23.452194] #PF: supervisor instruction fetch in kernel mode\n[   23.457896] #PF: error_code(0x0010) - not-present page\n[   23.463065] PGD 0 P4D 0\n[   23.465640] Oops: Oops: 0010 [#1] SMP NOPTI\n[   23.469869] CPU: 8 UID: 0 PID: 211 Comm: kworker/u48:18 Tainted: G S      W           6.19.0-rc4-00020-gf0b9d8eb98df #10 PREEMPT(voluntary)\n[   23.482512] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN\n[   23.496511] Workqueue: async async_run_entry_fn\n[   23.501087] RIP: 0010:0x0\n[   23.503755] Code: Unable to access opcode bytes at 0xffffffffffffffd6.\n[   23.510324] RSP: 0018:ffffb4a60065fca8 EFLAGS: 00010246\n[   23.515592] RAX: 0000000000000000 RBX: ffff9f428290e000 RCX: 000000000000000f\n[   23.522765] RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffff9f428290e000\n[   23.529937] RBP: ffff9f4282907070 R08: ffff9f4281130428 R09: 00000000ffffffff\n[   23.537111] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f42829070f8\n[   23.544284] R13: ffff9f4282906028 R14: ffff9f4282900000 R15: ffff9f4282906b68\n[   23.551457] FS:  0000000000000000(0000) GS:ffff9f466b2cf000(0000) knlGS:0000000000000000\n[   23.559588] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   23.565365] CR2: ffffffffffffffd6 CR3: 000000031c230001 CR4: 0000000000f70ef0\n[   23.572539] PKRU: 55555554\n[   23.575281] Call Trace:\n[   23.577770]  \u0026lt;TASK\u0026gt;\n[   23.579905]  intel_engines_reset_default_submission+0x42/0x60\n[   23.585695]  __intel_gt_unset_wedged+0x191/0x200\n[   23.590360]  intel_gt_unset_wedged+0x20/0x40\n[   23.594675]  gt_sanitize+0x15e/0x170\n[   23.598290]  i915_gem_suspend_late+0x6b/0x180\n[   23.602692]  i915_drm_suspend_late+0x35/0xf0\n[   23.607008]  ? __pfx_pci_pm_suspend_late+0x10/0x10\n[   23.611843]  dpm_run_callback+0x78/0x1c0\n[   23.615817]  device_suspend_late+0xde/0x2e0\n[   23.620037]  async_suspend_late+0x18/0x30\n[   23.624082]  async_run_entry_fn+0x25/0xa0\n[   23.628129]  process_one_work+0x15b/0x380\n[   23.632182]  worker_thread+0x2a5/0x3c0\n[   23.635973]  ? __pfx_worker_thread+0x10/0x10\n[   23.640279]  kthread+0xf6/0x1f0\n[   23.643464]  ? __pfx_kthread+0x10/0x10\n[   23.647263]  ? __pfx_kthread+0x10/0x10\n[   23.651045]  ret_from_fork+0x131/0x190\n[   23.654837]  ? __pfx_kthread+0x10/0x10\n[   23.658634]  ret_from_fork_asm+0x1a/0x30\n[   23.662597]  \u0026lt;/TASK\u0026gt;\n[   23.664826] Modules linked in:\n[   23.667914] CR2: 0000000000000000\n[   23.671271] ------------[ cut here ]------------\n\n(cherry picked from commit daa199abc3d3d1740c9e3a2c3e9216ae5b447cad)(CVE-2026-31540)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/platform/uv: Handle deconfigured sockets\n\nWhen a socket is deconfigured, it\u0026apos;s mapped to SOCK_EMPTY (0xffff). This causes\na panic while allocating UV hub info structures.\n\nFix this by using NUMA_NO_NODE, allowing UV hub info structures to be\nallocated on valid nodes.(CVE-2026-31542)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix NULL deref in bond_debug_rlb_hash_show\n\nrlb_clear_slave intentionally keeps RLB hash-table entries on\nthe rx_hashtbl_used_head list with slave set to NULL when no\nreplacement slave is available. However, bond_debug_rlb_hash_show\nvisites client_info-\u0026gt;slave without checking if it\u0026apos;s NULL.\n\nOther used-list iterators in bond_alb.c already handle this NULL-slave\nstate safely:\n\n- rlb_update_client returns early on !client_info-\u0026gt;slave\n- rlb_req_update_slave_clients, rlb_clear_slave, and rlb_rebalance\ncompare slave values before visiting\n- lb_req_update_subnet_clients continues if slave is NULL\n\nThe following NULL deref crash can be trigger in\nbond_debug_rlb_hash_show:\n\n[    1.289791] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    1.292058] RIP: 0010:bond_debug_rlb_hash_show (drivers/net/bonding/bond_debugfs.c:41)\n[    1.293101] RSP: 0018:ffffc900004a7d00 EFLAGS: 00010286\n[    1.293333] RAX: 0000000000000000 RBX: ffff888102b48200 RCX: ffff888102b48204\n[    1.293631] RDX: ffff888102b48200 RSI: ffffffff839daad5 RDI: ffff888102815078\n[    1.293924] RBP: ffff888102815078 R08: ffff888102b4820e R09: 0000000000000000\n[    1.294267] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100f929c0\n[    1.294564] R13: ffff888100f92a00 R14: 0000000000000001 R15: ffffc900004a7ed8\n[    1.294864] FS:  0000000001395380(0000) GS:ffff888196e75000(0000) knlGS:0000000000000000\n[    1.295239] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    1.295480] CR2: 0000000000000000 CR3: 0000000102adc004 CR4: 0000000000772ef0\n[    1.295897] Call Trace:\n[    1.296134]  seq_read_iter (fs/seq_file.c:231)\n[    1.296341]  seq_read (fs/seq_file.c:164)\n[    1.296493]  full_proxy_read (fs/debugfs/file.c:378 (discriminator 1))\n[    1.296658]  vfs_read (fs/read_write.c:572)\n[    1.296981]  ksys_read (fs/read_write.c:717)\n[    1.297132]  do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n[    1.297325]  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\nAdd a NULL check and print \u0026quot;(none)\u0026quot; for entries with no assigned slave.(CVE-2026-31546)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Clear stale exiting pointer in futex_lock_pi() retry path\n\nFuzzying/stressing futexes triggered:\n\n    WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524\n\nWhen futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY\nand stores a refcounted task pointer in \u0026apos;exiting\u0026apos;.\n\nAfter wait_for_owner_exiting() consumes that reference, the local pointer\nis never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a\ndifferent error, the bogus pointer is passed to wait_for_owner_exiting().\n\n  CPU0\t\t\t     CPU1\t\t       CPU2\n  futex_lock_pi(uaddr)\n  // acquires the PI futex\n  exit()\n    futex_cleanup_begin()\n      futex_state = EXITING;\n\t\t\t     futex_lock_pi(uaddr)\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t attach_to_pi_owner()\n\t\t\t\t   // observes EXITING\n\t\t\t\t   *exiting = owner;  // takes ref\n\t\t\t\t   return -EBUSY\n\t\t\t       wait_for_owner_exiting(-EBUSY, owner)\n\t\t\t\t put_task_struct();   // drops ref\n\t\t\t       // exiting still points to owner\n\t\t\t       goto retry;\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t lock_pi_update_atomic()\n\t\t\t\t   cmpxchg(uaddr)\n\t\t\t\t\t*uaddr ^= WAITERS // whatever\n\t\t\t\t   // value changed\n\t\t\t\t return -EAGAIN;\n\t\t\t       wait_for_owner_exiting(-EAGAIN, exiting) // stale\n\t\t\t\t WARN_ON_ONCE(exiting)\n\nFix this by resetting upon retry, essentially aligning it with requeue_pi.(CVE-2026-31555)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib\n\namdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence\nfrom amdgpu_ib_schedule(). This fence is used to wait for job\ncompletion.\n\nCurrently, the code drops the fence reference using dma_fence_put()\nbefore calling dma_fence_wait().\n\nIf dma_fence_put() releases the last reference, the fence may be\nfreed before dma_fence_wait() is called. This can lead to a\nuse-after-free.\n\nFix this by waiting on the fence first and releasing the reference\nonly after dma_fence_wait() completes.\n\nFixes the below:\ndrivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory \u0026apos;f\u0026apos; (line 696)\n\n(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)(CVE-2026-31566)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: gw: fix OOB heap access in cgw_csum_crc8_rel()\n\ncgw_csum_crc8_rel() correctly computes bounds-safe indices via calc_idx():\n\n    int from = calc_idx(crc8-\u0026gt;from_idx, cf-\u0026gt;len);\n    int to   = calc_idx(crc8-\u0026gt;to_idx,   cf-\u0026gt;len);\n    int res  = calc_idx(crc8-\u0026gt;result_idx, cf-\u0026gt;len);\n\n    if (from \u0026lt; 0 || to \u0026lt; 0 || res \u0026lt; 0)\n        return;\n\nHowever, the loop and the result write then use the raw s8 fields directly\ninstead of the computed variables:\n\n    for (i = crc8-\u0026gt;from_idx; ...)        /* BUG: raw negative index */\n    cf-\u0026gt;data[crc8-\u0026gt;result_idx] = ...;    /* BUG: raw negative index */\n\nWith from_idx = to_idx = result_idx = -64 on a 64-byte CAN FD frame,\ncalc_idx(-64, 64) = 0 so the guard passes, but the loop iterates with\ni = -64, reading cf-\u0026gt;data[-64], and the write goes to cf-\u0026gt;data[-64].\nThis write might end up to 56 (7.0-rc) or 40 (\u0026lt;= 6.19) bytes before the\nstart of the canfd_frame on the heap.\n\nThe companion function cgw_csum_xor_rel() uses `from`/`to`/`res`\ncorrectly throughout; fix cgw_csum_crc8_rel() to match.\n\nConfirmed with KASAN on linux-7.0-rc2:\n  BUG: KASAN: slab-out-of-bounds in cgw_csum_crc8_rel+0x515/0x5b0\n  Read of size 1 at addr ffff8880076619c8 by task poc_cgw_oob/62\n\nTo configure the can-gw crc8 checksums CAP_NET_ADMIN is needed.(CVE-2026-31570)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION\n\nDrop the WARN in sev_pin_memory() on npages overflowing an int, as the\nWARN is comically trivially to trigger from userspace, e.g. by doing:\n\n  struct kvm_enc_region range = {\n          .addr = 0,\n          .size = -1ul,\n  };\n\n  __vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, \u0026amp;range);\n\nNote, the checks in sev_mem_enc_register_region() that presumably exist to\nverify the incoming address+size are completely worthless, as both \u0026quot;addr\u0026quot;\nand \u0026quot;size\u0026quot; are u64s and SEV is 64-bit only, i.e. they _can\u0026apos;t_ be greater\nthan ULONG_MAX.  That wart will be cleaned up in the near future.\n\n\tif (range-\u0026gt;addr \u0026gt; ULONG_MAX || range-\u0026gt;size \u0026gt; ULONG_MAX)\n\t\treturn -EINVAL;\n\nOpportunistically add a comment to explain why the code calculates the\nnumber of pages the \u0026quot;hard\u0026quot; way, e.g. instead of just shifting @ulen.(CVE-2026-31590)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup\n\nDisable the delayed work before clearing BAR mappings and doorbells to\navoid running the handler after resources have been torn down.\n\n  Unable to handle kernel paging request at virtual address ffff800083f46004\n  [...]\n  Internal error: Oops: 0000000096000007 [#1]  SMP\n  [...]\n  Call trace:\n   epf_ntb_cmd_handler+0x54/0x200 [pci_epf_vntb] (P)\n   process_one_work+0x154/0x3b0\n   worker_thread+0x2c8/0x400\n   kthread+0x148/0x210\n   ret_from_fork+0x10/0x20(CVE-2026-31595)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU: Fix FPDSS on Zen1\n\nZen1\u0026apos;s hardware divider can leave, under certain circumstances, partial\nresults from previous operations.  Those results can be leaked by\nanother, attacker thread.\n\nFix that with a chicken bit.(CVE-2026-31628)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: proc: size address buffers for %pISpc output\n\nThe AF_RXRPC procfs helpers format local and remote socket addresses into\nfixed 50-byte stack buffers with \u0026quot;%pISpc\u0026quot;.\n\nThat is too small for the longest current-tree IPv6-with-port form the\nformatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a\ndotted-quad tail not only for v4mapped addresses, but also for ISATAP\naddresses via ipv6_addr_is_isatap().\n\nAs a result, a case such as\n\n  [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535\n\nis possible with the current formatter. That is 50 visible characters, so\n51 bytes including the trailing NUL, which does not fit in the existing\nchar[50] buffers used by net/rxrpc/proc.c.\n\nSize the buffers from the formatter\u0026apos;s maximum textual form and switch the\ncall sites to scnprintf().\n\nChanges since v1:\n- correct the changelog to cite the actual maximum current-tree case\n  explicitly\n- frame the proof around the ISATAP formatting path instead of the earlier\n  mapped-v4 example(CVE-2026-31630)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmmc: vub300: fix NULL-deref on disconnect\n\nMake sure to deregister the controller before dropping the reference to\nthe driver data on disconnect to avoid NULL-pointer dereferences or\nuse-after-free.(CVE-2026-31651)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: fix use-after-free in timeout object destroy\n\nnft_ct_timeout_obj_destroy() frees the timeout object with kfree()\nimmediately after nf_ct_untimeout(), without waiting for an RCU grace\nperiod. Concurrent packet processing on other CPUs may still hold\nRCU-protected references to the timeout object obtained via\nrcu_dereference() in nf_ct_timeout_data().\n\nAdd an rcu_head to struct nf_ct_timeout and use kfree_rcu() to defer\nfreeing until after an RCU grace period, matching the approach already\nused in nfnetlink_cttimeout.c.\n\nKASAN report:\n BUG: KASAN: slab-use-after-free in nf_conntrack_tcp_packet+0x1381/0x29d0\n Read of size 4 at addr ffff8881035fe19c by task exploit/80\n\n Call Trace:\n  nf_conntrack_tcp_packet+0x1381/0x29d0\n  nf_conntrack_in+0x612/0x8b0\n  nf_hook_slow+0x70/0x100\n  __ip_local_out+0x1b2/0x210\n  tcp_sendmsg_locked+0x722/0x1580\n  __sys_sendto+0x2d8/0x320\n\n Allocated by task 75:\n  nft_ct_timeout_obj_init+0xf6/0x290\n  nft_obj_init+0x107/0x1b0\n  nf_tables_newobj+0x680/0x9c0\n  nfnetlink_rcv_batch+0xc29/0xe00\n\n Freed by task 26:\n  nft_obj_destroy+0x3f/0xa0\n  nf_tables_trans_destroy_work+0x51c/0x5c0\n  process_one_work+0x2c4/0x5a0(CVE-2026-31665)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: uinput - fix circular locking dependency with ff-core\n\nA lockdep circular locking dependency warning can be triggered\nreproducibly when using a force-feedback gamepad with uinput (for\nexample, playing ELDEN RING under Wine with a Flydigi Vader 5\ncontroller):\n\n  ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex\n\nThe cycle is caused by four lock acquisition paths:\n\n1. ff upload: input_ff_upload() holds ff-\u0026gt;mutex and calls\n   uinput_dev_upload_effect() -\u0026gt; uinput_request_submit() -\u0026gt;\n   uinput_request_send(), which acquires udev-\u0026gt;mutex.\n\n2. device create: uinput_ioctl_handler() holds udev-\u0026gt;mutex and calls\n   uinput_create_device() -\u0026gt; input_register_device(), which acquires\n   input_mutex.\n\n3. device register: input_register_device() holds input_mutex and\n   calls kbd_connect() -\u0026gt; input_register_handle(), which acquires\n   dev-\u0026gt;mutex.\n\n4. evdev release: evdev_release() calls input_flush_device() under\n   dev-\u0026gt;mutex, which calls input_ff_flush() acquiring ff-\u0026gt;mutex.\n\nFix this by introducing a new state_lock spinlock to protect\nudev-\u0026gt;state and udev-\u0026gt;dev access in uinput_request_send() instead of\nacquiring udev-\u0026gt;mutex.  The function only needs to atomically check\ndevice state and queue an input event into the ring buffer via\nuinput_dev_event() -- both operations are safe under a spinlock\n(ktime_get_ts64() and wake_up_interruptible() do not sleep).  This\nbreaks the ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex link since a spinlock is a leaf in\nthe lock ordering and cannot form cycles with mutexes.\n\nTo keep state transitions visible to uinput_request_send(), protect\nwrites to udev-\u0026gt;state in uinput_create_device() and\nuinput_destroy_device() with the same state_lock spinlock.\n\nAdditionally, move init_completion(\u0026amp;request-\u0026gt;done) from\nuinput_request_send() to uinput_request_submit() before\nuinput_request_reserve_slot().  Once the slot is allocated,\nuinput_flush_requests() may call complete() on it at any time from\nthe destroy path, so the completion must be initialised before the\nrequest becomes visible.\n\nLock ordering after the fix:\n\n  ff-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex (no back-edge)(CVE-2026-31667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_netem: fix out-of-bounds access in packet corruption\n\nIn netem_enqueue(), the packet corruption logic uses\nget_random_u32_below(skb_headlen(skb)) to select an index for\nmodifying skb-\u0026gt;data. When an AF_PACKET TX_RING sends fully non-linear\npackets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.\n\nPassing 0 to get_random_u32_below() takes the variable-ceil slow path\nwhich returns an unconstrained 32-bit random integer. Using this\nunconstrained value as an offset into skb-\u0026gt;data results in an\nout-of-bounds memory access.\n\nFix this by verifying skb_headlen(skb) is non-zero before attempting\nto corrupt the linear data area. Fully non-linear packets will silently\nbypass the corruption logic.(CVE-2026-31675)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - limit RX SG extraction by receive buffer budget\n\nMake af_alg_get_rsgl() limit each RX scatterlist extraction to the\nremaining receive buffer budget.\n\naf_alg_get_rsgl() currently uses af_alg_readable() only as a gate\nbefore extracting data into the RX scatterlist. Limit each extraction\nto the remaining af_alg_rcvbuf(sk) budget so that receive-side\naccounting matches the amount of data attached to the request.\n\nIf skcipher cannot obtain enough RX space for at least one chunk while\nmore data remains to be processed, reject the recvmsg call instead of\nrounding the request length down to zero.(CVE-2026-31677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: defer tunnel netdev_put to RCU release\n\novs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already\ndetached the device. Dropping the netdev reference in destroy can race\nwith concurrent readers that still observe vport-\u0026gt;dev.\n\nDo not release vport-\u0026gt;dev in ovs_netdev_tunnel_destroy(). Instead, let\nvport_netdev_free() drop the reference from the RCU callback, matching\nthe non-tunnel destroy path and avoiding additional synchronization\nunder RTNL.(CVE-2026-31678)\n\nIn the Linux kernel, a memory out-of-bounds access vulnerability exists in the act_csum module\u0026apos;s tcf_csum_act() function when processing nested VLAN headers. When an skb still carries in-payload VLAN tags, the function walks nested VLAN headers directly from skb-\u0026gt;data. The current code reads vlan-\u0026gt;h_vlan_encapsulated_proto and then pulls VLAN_HLEN bytes without first ensuring that the full VLAN header is present in the linear area. If only part of an inner VLAN header is linearized, accessing h_vlan_encapsulated_proto reads past the linear area, and the following skb_pull(VLAN_HLEN) may violate skb invariants.(CVE-2026-31684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ip6t_eui64: reject invalid MAC header for all packets\n\n`eui64_mt6()` derives a modified EUI-64 from the Ethernet source address\nand compares it with the low 64 bits of the IPv6 source address.\n\nThe existing guard only rejects an invalid MAC header when\n`par-\u0026gt;fragoff != 0`. For packets with `par-\u0026gt;fragoff == 0`, `eui64_mt6()`\ncan still reach `eth_hdr(skb)` even when the MAC header is not valid.\n\nFix this by removing the `par-\u0026gt;fragoff != 0` condition so that packets\nwith an invalid MAC header are rejected before accessing `eth_hdr(skb)`.(CVE-2026-31685)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u0026gt;pvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device\u0026apos;s release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they\u0026apos;re called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: \u0026apos;(null)\u0026apos;: is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.(CVE-2026-31689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy ID to userspace if PSP command failed\n\nWhen retrieving the ID for the CPU, don\u0026apos;t attempt to copy the ID blob to\nuserspace if the firmware command failed.  If the failure was due to an\ninvalid length, i.e. the userspace buffer+length was too small, copying\nthe number of bytes _firmware_ requires will overflow the kernel-allocated\nbuffer and leak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 64 at addr ffff8881867f5960 by task syz.0.906/24388\n\n  CPU: 130 UID: 0 PID: 24388 Comm: syz.0.906 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_get_id2+0x361/0x490 ../drivers/crypto/ccp/sev-dev.c:2222\n   sev_ioctl+0x25f/0x490 ../drivers/crypto/ccp/sev-dev.c:2575\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy PDH cert to userspace if PSP command failed\n\nWhen retrieving the PDH cert, don\u0026apos;t attempt to copy the blobs to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff8885c4ab8aa0 by task syz.0.186/21033\n\n  CPU: 51 UID: 0 PID: 21033 Comm: syz.0.186 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc.                                                       Arcadia_IT_80/Arcadia_IT_80, BIOS 34.84.12-0 11/17/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pdh_export+0x3d3/0x7c0 ../drivers/crypto/ccp/sev-dev.c:2347\n   sev_ioctl+0x2a2/0x490 ../drivers/crypto/ccp/sev-dev.c:2568\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31698)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy CSR to userspace if PSP command failed\n\nWhen retrieving the PEK CSR, don\u0026apos;t attempt to copy the blob to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff898144612e20 by task syz.9.219/21405\n\n  CPU: 14 UID: 0 PID: 21405 Comm: syz.9.219 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pek_csr+0x31f/0x590 ../drivers/crypto/ccp/sev-dev.c:1872\n   sev_ioctl+0x3a4/0x490 ../drivers/crypto/ccp/sev-dev.c:2562\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path\n\nsmb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL\nand the default QUERY_INFO path.  The QUERY_INFO branch clamps\nqi.input_buffer_length to the server-reported OutputBufferLength and then\ncopies qi.input_buffer_length bytes from qi_rsp-\u0026gt;Buffer to userspace, but\nit never verifies that the flexible-array payload actually fits within\nrsp_iov[1].iov_len.\n\nA malicious server can return OutputBufferLength larger than the actual\nQUERY_INFO response, causing copy_to_user() to walk past the response\nbuffer and expose adjacent kernel heap to userspace.\n\nGuard the QUERY_INFO copy with a bounds check on the actual Buffer\npayload.  Use struct_size(qi_rsp, Buffer, qi.input_buffer_length)\nrather than an open-coded addition so the guard cannot overflow on\n32-bit builds.(CVE-2026-31708)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: validate ND option lengths in vxlan_na_create\n\nvxlan_na_create() walks ND options according to option-provided\nlengths. A malformed option can make the parser advance beyond the\ncomputed option span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31738)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: fix NULL pointer dereference in ep_queue\n\nWhen the gadget endpoint is disabled or not yet configured, the ep-\u0026gt;desc\npointer can be NULL. This leads to a NULL pointer dereference when\n__cdns3_gadget_ep_queue() is called, causing a kernel crash.\n\nAdd a check to return -ESHUTDOWN if ep-\u0026gt;desc is NULL, which is the\nstandard return code for unconfigured endpoints.\n\nThis prevents potential crashes when ep_queue is called on endpoints\nthat are not ready.(CVE-2026-31755)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: move wake reason storage into validated event handlers\n\nhci_store_wake_reason() is called from hci_event_packet() immediately\nafter stripping the HCI event header but before hci_event_func()\nenforces the per-event minimum payload length from hci_ev_table.\nThis means a short HCI event frame can reach bacpy() before any bounds\ncheck runs.\n\nRather than duplicating skb parsing and per-event length checks inside\nhci_store_wake_reason(), move wake-address storage into the individual\nevent handlers after their existing event-length validation has\nsucceeded. Convert hci_store_wake_reason() into a small helper that only\nstores an already-validated bdaddr while the caller holds hci_dev_lock().\nUse the same helper after hci_event_func() with a NULL address to\npreserve the existing unexpected-wake fallback semantics when no\nvalidated event handler records a wake address.\n\nAnnotate the helper with __must_hold(\u0026amp;hdev-\u0026gt;lock) and add\nlockdep_assert_held(\u0026amp;hdev-\u0026gt;lock) so future call paths keep the lock\ncontract explicit.\n\nCall the helper from hci_conn_request_evt(), hci_conn_complete_evt(),\nhci_sync_conn_complete_evt(), le_conn_complete_evt(),\nhci_le_adv_report_evt(), hci_le_ext_adv_report_evt(),\nhci_le_direct_adv_report_evt(), hci_le_pa_sync_established_evt(), and\nhci_le_past_received_evt().(CVE-2026-31771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: SMP: derive legacy responder STK authentication from MITM state\n\nThe legacy responder path in smp_random() currently labels the stored\nSTK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH.\nThat reflects what the local service requested, not what the pairing\nflow actually achieved.\n\nFor Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear\nand the resulting STK should remain unauthenticated even if the local\nside requested HIGH security. Use the established MITM state when\nstoring the responder STK so the key metadata matches the pairing result.\n\nThis also keeps the legacy path aligned with the Secure Connections code,\nwhich already treats JUST_WORKS/JUST_CFM as unauthenticated.(CVE-2026-31773)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler()\n\nThe memcpy function assumes the dynamic array notif-\u0026gt;matches is at least\nas large as the number of bytes to copy. Otherwise, results-\u0026gt;matches may\ncontain unwanted data. To guarantee safety, extend the validation in one\nof the checks to ensure sufficient packet length.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2026-31779)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ioc32: stop speculation on the drm_compat_ioctl path\n\nThe drm compat ioctl path takes a user controlled pointer, and then\ndereferences it into a table of function pointers, the signature method\nof spectre problems.  Fix this up by calling array_index_nospec() on the\nindex to the function pointer list.(CVE-2026-31781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: validate LTK enc_size on load\n\nLoad Long Term Keys stores the user-provided enc_size and later uses\nit to size fixed-size stack operations when replying to LE LTK\nrequests. An enc_size larger than the 16-byte key buffer can therefore\noverflow the reply stack buffer.\n\nReject oversized enc_size values while validating the management LTK\nrecord so invalid keys never reach the stored key state.(CVE-2026-43020)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: use skb_header_pointer() for TCPv4 GSO frag_off check\n\nSyzbot reported a KMSAN uninit-value warning in gso_features_check()\ncalled from netif_skb_features() [1].\n\ngso_features_check() reads iph-\u0026gt;frag_off to decide whether to clear\nmangleid_features. Accessing the IPv4 header via ip_hdr()/inner_ip_hdr()\ncan rely on skb header offsets that are not always safe for direct\ndereference on packets injected from PF_PACKET paths.\n\nUse skb_header_pointer() for the TCPv4 frag_off check so the header read\nis robust whether data is already linear or needs copying.\n\n[1] https://syzkaller.appspot.com/bug?extid=1543a7d954d9c6d00407(CVE-2026-43036)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak\n\nWhen processing Router Advertisements with user options the kernel\nbuilds an RTM_NEWNDUSEROPT netlink message. The nduseroptmsg struct\nhas three padding fields that are never zeroed and can leak kernel data\n\nThe fix is simple, just zeroes the padding fields.(CVE-2026-43040)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af-alg - fix NULL pointer dereference in scatterwalk\n\nThe AF_ALG interface fails to unmark the end of a Scatter/Gather List (SGL)\nwhen chaining a new af_alg_tsgl structure. If a sendmsg() fills an SGL\nexactly to MAX_SGL_ENTS, the last entry is marked as the end. A subsequent\nsendmsg() allocates a new SGL and chains it, but fails to clear the end\nmarker on the previous SGL\u0026apos;s last data entry.\n\nThis causes the crypto scatterwalk to hit a premature end, returning NULL\non sg_next() and leading to a kernel panic during dereference.\n\nFix this by explicitly unmarking the end of the previous SGL when\nperforming sg_chain() in af_alg_alloc_tsgl().(CVE-2026-43043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix not releasing workqueue on .release()\n\nThe workqueue associated with an DSA/IAA device is not released when\nthe object is freed.(CVE-2026-43064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Skip discovery table for offline dies\n\nThis warning can be triggered if NUMA is disabled and the system\nboots with fewer CPUs than the number of CPUs in die 0.\n\nWARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]\n\nCurrently, the discovery table continues to be parsed even if all CPUs\nin the associated die are offline.  This can lead to an array overflow\nat \u0026quot;pmu-\u0026gt;boxes[die] = box\u0026quot; in uncore_pci_pmu_register(), which may\ntrigger the warning above or cause other issues.(CVE-2026-43079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/smp: Add check for kcalloc() failure in parse_thread_groups()\n\nAs kcalloc() may fail, check its return value to avoid a NULL pointer\ndereference when passing it to of_property_read_u32_array().(CVE-2026-43148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE\n\nThe arch definition of cpumask_of_node() cannot handle NUMA_NO_NODE -\nwhich is a valid index - so add a check for this.(CVE-2026-43212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fiemap page fault fix\n\nIn gfs2_fiemap(), we are calling iomap_fiemap() while holding the inode\nglock.  This can lead to recursive glock taking if the fiemap buffer is\nmemory mapped to the same inode and accessing it triggers a page fault.\n\nFix by disabling page faults for iomap_fiemap() and faulting in the\nbuffer by hand if necessary.\n\nFixes xfstest generic/742.(CVE-2026-43262)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: supply snapshot context in ceph_zero_partial_object()\n\nThe ceph_zero_partial_object function was missing proper snapshot\ncontext for its OSD write operations, which could lead to data\ninconsistencies in snapshots.\n\nReproducer:\n../src/vstart.sh --new -x --localhost --bluestore\n./bin/ceph auth caps client.fs_a mds \u0026apos;allow rwps fsname=a\u0026apos; mon \u0026apos;allow r fsname=a\u0026apos; osd \u0026apos;allow rw tag cephfs data=a\u0026apos;\nmount -t ceph (CVE-2026-43273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipa: fix event ring index not programmed for IPA v5.0+\n\nFor IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to\nCH_C_CNTXT_1. The v5.0 register definition intended to define this\nfield in the CH_C_CNTXT_1 fmask array but used the old identifier of\nERINDEX instead of CH_ERINDEX.\n\nWithout a valid event ring, GSI channels could never signal transfer\ncompletions. This caused gsi_channel_trans_quiesce() to block\nforever in wait_for_completion().\n\nAt least for IPA v5.2 this resolves an issue seen where runtime\nsuspend, system suspend, and remoteproc stop all hanged forever. It\nalso meant the IPA data path was completely non functional.(CVE-2026-43345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix memory leaks in ceph_mdsc_build_path()\n\nAdd __putname() calls to error code paths that did not free the \u0026quot;path\u0026quot;\npointer obtained by __getname().  If ownership of this pointer is not\npassed to the caller via path_info.path, the function must free it\nbefore returning.(CVE-2026-43419)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Limit the length of unkillable synchronous timeouts\n\nThe usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in\nusbcore allow unlimited timeout durations.  And since they use\nuninterruptible waits, this leaves open the possibility of hanging a\ntask for an indefinitely long time, with no way to kill it short of\nunplugging the target device.\n\nTo prevent this sort of problem, enforce a maximum limit on the length\nof these unkillable timeouts.  The limit chosen here, somewhat\narbitrarily, is 60 seconds.  On many systems (although not all) this\nis short enough to avoid triggering the kernel\u0026apos;s hung-task detector.\n\nIn addition, clear up the ambiguity of negative timeout values by\ntreating them the same as 0, i.e., using the maximum allowed timeout.(CVE-2026-43428)\n\nIn the Linux kernel, the following vulnerability has been resolved:  crypto: pcrypt - Fix handling of MAY_BACKLOG requests  MAY_BACKLOG requests can return EBUSY.  Handle them by checking for that value and filtering out EINPROGRESS notifications.  The Linux kernel CVE team has assigned CVE-2026-43493 to this issue.(CVE-2026-43493)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skbuff: propagate shared-frag marker through frag-transfer helpers\n\nTwo frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail\nto propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()-\u0026gt;flags when\nmoving frags from source to destination.  __pskb_copy_fclone() defers\nthe rest of the shinfo metadata to skb_copy_header() after copying\nfrag descriptors, but that helper only carries over gso_{size,segs,\ntype} and never touches skb_shinfo()-\u0026gt;flags; skb_shift() moves frag\ndescriptors directly and leaves flags untouched.  As a result, the\ndestination skb keeps a reference to the same externally-owned or\npage-cache-backed pages while reporting skb_has_shared_frag() as\nfalse.\n\nThe mismatch is harmful in any in-place writer that uses\nskb_has_shared_frag() to decide whether shared pages must be detoured\nthrough skb_cow_data().  ESP input is one such writer (esp4.c,\nesp6.c), and a single nft \u0026apos;dup to \u0026lt;local\u0026gt;\u0026apos; rule -- or any other\nnf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()\u0026apos;d\nskb in esp_input() with the marker stripped, letting an unprivileged\nuser write into the page cache of a root-owned read-only file via\nauthencesn-ESN stray writes.\n\nSet SKBFL_SHARED_FRAG on the destination whenever frag descriptors\nwere actually moved from the source.  skb_copy() and skb_copy_expand()\nshare skb_copy_header() too but linearize all paged data into freshly\nallocated head storage and emerge with nr_frags == 0, so\nskb_has_shared_frag() returns false on its own; they need no change.\n\nThe same omission exists in skb_gro_receive() and skb_gro_receive_list().\nThe former moves the incoming skb\u0026apos;s frag descriptors into the\naccumulator\u0026apos;s last sub-skb via two paths (a direct frag-move loop and\nthe head_frag + memcpy path); the latter chains the incoming skb whole\nonto p\u0026apos;s frag_list.  Downstream skb_segment() reads only\nskb_shinfo(p)-\u0026gt;flags, and skb_segment_list() reuses each sub-skb\u0026apos;s\nshinfo as the nskb -- both p and lp must carry the marker.\n\nThe same omission also exists in tcp_clone_payload(), which builds an\nMTU probe skb by moving frag descriptors from skbs on sk_write_queue\ninto a freshly allocated nskb.  The helper falls into the same family\nand warrants the same fix for consistency; no TCP TX-side in-place\nwriter is currently known to reach a user page through this gap, but\na future consumer depending on the marker would regress silently.\n\nThe same omission exists in skb_segment(): the per-iteration flag\nmerge takes only head_skb\u0026apos;s flag, and the inner switch that rebinds\nfrag_skb to list_skb on head_skb-frags exhaustion does not fold the\nnew frag_skb\u0026apos;s flag into nskb.  Fold frag_skb\u0026apos;s flag at both sites\nso segments drawing frags from frag_list members carry the marker.(CVE-2026-43503)","status":"published","published":"2026-06-05T11:11:31Z","modified":"2026-08-18T01:20:04.18419257Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"OESA-2026-2582","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmISDN: hfcpci: Fix warning when deleting uninitialized timer\n\nWith CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads\nto the following splat:\n\n[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0\n[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0\n[  250.218775] Modules linked in: hfcpci(-) mISDN_core\n[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)\n[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0\n[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d\n[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286\n[  250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95\n[  250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0\n[  250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39\n[  250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001\n[  250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8\n[  250.232454] FS:  00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:0000000000000000\n[  250.233851] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  250.234856] CR2: 00007f32090a7421 CR3: 0000000004d63000 CR4: 00000000000006f0\n[  250.236117] Call Trace:\n[  250.236599]  \u0026lt;TASK\u0026gt;\n[  250.236967]  ? trace_irq_enable.constprop.0+0xd4/0x130\n[  250.237920]  debug_object_assert_init+0x1f6/0x310\n[  250.238762]  ? __pfx_debug_object_assert_init+0x10/0x10\n[  250.239658]  ? __lock_acquire+0xdea/0x1c70\n[  250.240369]  __try_to_del_timer_sync+0x69/0x140\n[  250.241172]  ? __pfx___try_to_del_timer_sync+0x10/0x10\n[  250.242058]  ? __timer_delete_sync+0xc6/0x120\n[  250.242842]  ? lock_acquire+0x30/0x80\n[  250.243474]  ? __timer_delete_sync+0xc6/0x120\n[  250.244262]  __timer_delete_sync+0x98/0x120\n[  250.245015]  HFC_cleanup+0x10/0x20 [hfcpci]\n[  250.245704]  __do_sys_delete_module+0x348/0x510\n[  250.246461]  ? __pfx___do_sys_delete_module+0x10/0x10\n[  250.247338]  do_syscall_64+0xc1/0x360\n[  250.247924]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix this by initializing hfc_tl timer with DEFINE_TIMER macro.\nAlso, use mod_timer instead of manual timeout update.(CVE-2025-39833)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Add support for Van Gogh SoC\n\nThe ROG Xbox Ally (non-X) SoC features a similar architecture to the\nSteam Deck. While the Steam Deck supports S3 (s2idle causes a crash),\nthis support was dropped by the Xbox Ally which only S0ix suspend.\n\nSince the handler is missing here, this causes the device to not suspend\nand the AMD GPU driver to crash while trying to resume afterwards due to\na power hang.(CVE-2025-68334)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: Move team device type change at the end of team_port_add\n\nAttempting to add a port device that is already up will expectedly fail,\nbut not before modifying the team device header_ops.\n\nIn the case of the syzbot reproducer the gre0 device is\nalready in state UP when it attempts to add it as a\nport device of team0, this fails but before that\nheader_ops-\u0026gt;create of team0 is changed from eth_header to ipgre_header\nin the call to team_dev_type_check_change.\n\nLater when we end up in ipgre_header() struct ip_tunnel* points to nonsense\nas the private data of the device still holds a struct team.\n\nExample sequence of iproute2 commands to reproduce the hang/BUG():\nip link add dev team0 type team\nip link add dev gre0 type gre\nip link set dev gre0 up\nip link set dev gre0 master team0\nip link set dev team0 up\nping -I team0 1.1.1.1\n\nMove team_dev_type_check_change down where all other checks have passed\nas it changes the dev type with no way to restore it in case\none of the checks that follow it fail.\n\nAlso make sure to preserve the origial mtu assignment:\n  - If port_dev is not the same type as dev, dev takes mtu from port_dev\n  - If port_dev is the same type as dev, port_dev takes mtu from dev\n\nThis is done by adding a conditional before the call to dev_set_mtu\nto prevent it from assigning port_dev-\u0026gt;mtu = dev-\u0026gt;mtu and instead\nletting team_dev_type_check_change assign dev-\u0026gt;mtu = port_dev-\u0026gt;mtu.\nThe conditional is needed because the patch moves the call to\nteam_dev_type_check_change past dev_set_mtu.\n\nTesting:\n  - team device driver in-tree selftests\n  - Add/remove various devices as slaves of team device\n  - syzbot(CVE-2025-68340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb-\u0026gt;vma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb-\u0026gt;vma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb-\u0026gt;vma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer\u0026apos;s vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb-\u0026gt;vma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u0026gt;vma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn\u0026apos;t matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)(CVE-2025-71130)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix deadlock in wait_current_trans() due to ignored transaction type\n\nWhen wait_current_trans() is called during start_transaction(), it\ncurrently waits for a blocked transaction without considering whether\nthe given transaction type actually needs to wait for that particular\ntransaction state. The btrfs_blocked_trans_types[] array already defines\nwhich transaction types should wait for which transaction states, but\nthis check was missing in wait_current_trans().\n\nThis can lead to a deadlock scenario involving two transactions and\npending ordered extents:\n\n  1. Transaction A is in TRANS_STATE_COMMIT_DOING state\n\n  2. A worker processing an ordered extent calls start_transaction()\n     with TRANS_JOIN\n\n  3. join_transaction() returns -EBUSY because Transaction A is in\n     TRANS_STATE_COMMIT_DOING\n\n  4. Transaction A moves to TRANS_STATE_UNBLOCKED and completes\n\n  5. A new Transaction B is created (TRANS_STATE_RUNNING)\n\n  6. The ordered extent from step 2 is added to Transaction B\u0026apos;s\n     pending ordered extents\n\n  7. Transaction B immediately starts commit by another task and\n     enters TRANS_STATE_COMMIT_START\n\n  8. The worker finally reaches wait_current_trans(), sees Transaction B\n     in TRANS_STATE_COMMIT_START (a blocked state), and waits\n     unconditionally\n\n  9. However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START\n     according to btrfs_blocked_trans_types[]\n\n  10. Transaction B is waiting for pending ordered extents to complete\n\n  11. Deadlock: Transaction B waits for ordered extent, ordered extent\n      waits for Transaction B\n\nThis can be illustrated by the following call stacks:\n  CPU0                              CPU1\n                                    btrfs_finish_ordered_io()\n                                      start_transaction(TRANS_JOIN)\n                                        join_transaction()\n                                          # -EBUSY (Transaction A is\n                                          # TRANS_STATE_COMMIT_DOING)\n  # Transaction A completes\n  # Transaction B created\n  # ordered extent added to\n  # Transaction B\u0026apos;s pending list\n  btrfs_commit_transaction()\n    # Transaction B enters\n    # TRANS_STATE_COMMIT_START\n    # waiting for pending ordered\n    # extents\n                                        wait_current_trans()\n                                          # waits for Transaction B\n                                          # (should not wait!)\n\nTask bstore_kv_sync in btrfs_commit_transaction waiting for ordered\nextents:\n\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  btrfs_commit_transaction+0xbf7/0xda0 [btrfs]\n  btrfs_sync_file+0x342/0x4d0 [btrfs]\n  __x64_sys_fdatasync+0x4b/0x80\n  do_syscall_64+0x33/0x40\n  entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nTask kworker in wait_current_trans waiting for transaction commit:\n\n  Workqueue: btrfs-syno_nocow btrfs_work_helper [btrfs]\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  wait_current_trans+0xb0/0x110 [btrfs]\n  start_transaction+0x346/0x5b0 [btrfs]\n  btrfs_finish_ordered_io.isra.0+0x49b/0x9c0 [btrfs]\n  btrfs_work_helper+0xe8/0x350 [btrfs]\n  process_one_work+0x1d3/0x3c0\n  worker_thread+0x4d/0x3e0\n  kthread+0x12d/0x150\n  ret_from_fork+0x1f/0x30\n\nFix this by passing the transaction type to wait_current_trans() and\nchecking btrfs_blocked_trans_types[cur_trans-\u0026gt;state] against the given\ntype before deciding to wait. This ensures that transaction types which\nare allowed to join during certain blocked states will not unnecessarily\nwait and cause deadlocks.(CVE-2025-71194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: fix possible UAF in macvlan_forward_source()\n\nAdd RCU protection on (struct macvlan_source_entry)-\u0026gt;vlan.\n\nWhenever macvlan_hash_del_source() is called, we must clear\nentry-\u0026gt;vlan pointer before RCU grace period starts.\n\nThis allows macvlan_forward_source() to skip over\nentries queued for freeing.\n\nNote that macvlan_dev are already RCU protected, as they\nare embedded in a standard netdev (netdev_priv(ndev)).\n\nhttps: //lore.kernel.org/netdev/(CVE-2026-23001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Enforce that teql can only be used as root qdisc\n\nDesign intent of teql is that it is only supposed to be used as root qdisc.\nWe need to check for that constraint.\n\nAlthough not important, I will describe the scenario that unearthed this\nissue for the curious.\n\nGangMin Kim \u0026lt;(CVE-2026-23074)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: fix hugetlb_pmd_shared()\n\nPatch series \u0026quot;mm/hugetlb: fixes for PMD table sharing (incl.  using\nmmu_gather)\u0026quot;, v3.\n\nOne functional fix, one performance regression fix, and two related\ncomment fixes.\n\nI cleaned up my prototype I recently shared [1] for the performance fix,\ndeferring most of the cleanups I had in the prototype to a later point. \nWhile doing that I identified the other things.\n\nThe goal of this patch set is to be backported to stable trees \u0026quot;fairly\u0026quot;\neasily. At least patch #1 and #4.\n\nPatch #1 fixes hugetlb_pmd_shared() not detecting any sharing\nPatch #2 + #3 are simple comment fixes that patch #4 interacts with.\nPatch #4 is a fix for the reported performance regression due to excessive\nIPI broadcasts during fork()+exit().\n\nThe last patch is all about TLB flushes, IPIs and mmu_gather.\nRead: complicated\n\nThere are plenty of cleanups in the future to be had + one reasonable\noptimization on x86. But that\u0026apos;s all out of scope for this series.\n\nRuntime tested, with a focus on fixing the performance regression using\nthe original reproducer [2] on x86.\n\n\nThis patch (of 4):\n\nWe switched from (wrongly) using the page count to an independent shared\ncount.  Now, shared page tables have a refcount of 1 (excluding\nspeculative references) and instead use ptdesc-\u0026gt;pt_share_count to identify\nsharing.\n\nWe didn\u0026apos;t convert hugetlb_pmd_shared(), so right now, we would never\ndetect a shared PMD table as such, because sharing/unsharing no longer\ntouches the refcount of a PMD table.\n\nPage migration, like mbind() or migrate_pages() would allow for migrating\nfolios mapped into such shared PMD tables, even though the folios are not\nexclusive.  In smaps we would account them as \u0026quot;private\u0026quot; although they are\n\u0026quot;shared\u0026quot;, and we would be wrongly setting the PM_MMAP_EXCLUSIVE in the\npagemap interface.\n\nFix it by properly using ptdesc_pmd_is_shared() in hugetlb_pmd_shared().(CVE-2026-23100)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: secure_seq: add back ports to TS offset\n\nThis reverts 28ee1b746f49 (\u0026quot;secure_seq: downgrade to per-host timestamp offsets\u0026quot;)\n\ntcp_tw_recycle went away in 2017.\n\nZhouyan Deng reported off-path TCP source port leakage via\nSYN cookie side-channel that can be fixed in multiple ways.\n\nOne of them is to bring back TCP ports in TS offset randomization.\n\nAs a bonus, we perform a single siphash() computation\nto provide both an ISN and a TS offset.(CVE-2026-23247)\n\nIn the Linux kernel, a vulnerability exists in the AppArmor module\u0026apos;s unpack_pdb function. The vulnerability occurs due to failure to validate that DFA start states are within bounds, which can lead to out-of-bound reads. An attacker can exploit this vulnerability through specially crafted policy files, potentially leading to information disclosure or system crashes.(CVE-2026-23269)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: unconditionally bump set-\u0026gt;nelems before insertion\n\nIn case that the set is full, a new element gets published then removed\nwithout waiting for the RCU grace period, while RCU reader can be\nwalking over it already.\n\nTo address this issue, add the element transaction even if set is full,\nbut toggle the set_full flag to report -ENFILE so the abort path safely\nunwinds the set to its previous state.\n\nAs for element updates, decrement set-\u0026gt;nelems to restore it.\n\nA simpler fix is to call synchronize_rcu() in the error path.\nHowever, with a large batch adding elements to already maxed-out set,\nthis could cause noticeable slowdown of such batches.(CVE-2026-23272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kaweth: validate USB endpoints\n\nThe kaweth driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs\n\nWhen shrinking the number of real tx queues,\nnetif_set_real_num_tx_queues() calls qdisc_reset_all_tx_gt() to flush\nqdiscs for queues which will no longer be used.\n\nqdisc_reset_all_tx_gt() currently serializes qdisc_reset() with\nqdisc_lock(). However, for lockless qdiscs, the dequeue path is\nserialized by qdisc_run_begin/end() using qdisc-\u0026gt;seqlock instead, so\nqdisc_reset() can run concurrently with __qdisc_run() and free skbs\nwhile they are still being dequeued, leading to UAF.\n\nThis can easily be reproduced on e.g. virtio-net by imposing heavy\ntraffic while frequently changing the number of queue pairs:\n\n  iperf3 -ub0 -c $peer -t 0 \u0026amp;\n  while :; do\n    ethtool -L eth0 combined 1\n    ethtool -L eth0 combined 2\n  done\n\nWith KASAN enabled, this leads to reports like:\n\n  BUG: KASAN: slab-use-after-free in __qdisc_run+0x133f/0x1760\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   __qdisc_run+0x133f/0x1760\n   __dev_queue_xmit+0x248f/0x3550\n   ip_finish_output2+0xa42/0x2110\n   ip_output+0x1a7/0x410\n   ip_send_skb+0x2e6/0x480\n   udp_send_skb+0xb0a/0x1590\n   udp_sendmsg+0x13c9/0x1fc0\n   ...\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 1270 on cpu 5 at 44.558414s:\n   ...\n   alloc_skb_with_frags+0x84/0x7c0\n   sock_alloc_send_pskb+0x69a/0x830\n   __ip_append_data+0x1b86/0x48c0\n   ip_make_skb+0x1e8/0x2b0\n   udp_sendmsg+0x13a6/0x1fc0\n   ...\n\n  Freed by task 1306 on cpu 3 at 44.558445s:\n   ...\n   kmem_cache_free+0x117/0x5e0\n   pfifo_fast_reset+0x14d/0x580\n   qdisc_reset+0x9e/0x5f0\n   netif_set_real_num_tx_queues+0x303/0x840\n   virtnet_set_channels+0x1bf/0x260 [virtio_net]\n   ethnl_set_channels+0x684/0xae0\n   ethnl_default_set_doit+0x31a/0x890\n   ...\n\nSerialize qdisc_reset_all_tx_gt() against the lockless dequeue path by\ntaking qdisc-\u0026gt;seqlock for TCQ_F_NOLOCK qdiscs, matching the\nserialization model already used by dev_reset_queue().\n\nAdditionally clear QDISC_STATE_NON_EMPTY after reset so the qdisc state\nreflects an empty queue, avoiding needless re-scheduling.(CVE-2026-23340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_ife: Fix metalist update behavior\n\nWhenever an ife action replace changes the metalist, instead of\nreplacing the old data on the metalist, the current ife code is appending\nthe new metadata. Aside from being innapropriate behavior, this may lead\nto an unbounded addition of metadata to the metalist which might cause an\nout of bounds error when running the encode op:\n\n[  138.423369][    C1] ==================================================================\n[  138.424317][    C1] BUG: KASAN: slab-out-of-bounds in ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.424906][    C1] Write of size 4 at addr ffff8880077f4ffe by task ife_out_out_bou/255\n[  138.425778][    C1] CPU: 1 UID: 0 PID: 255 Comm: ife_out_out_bou Not tainted 7.0.0-rc1-00169-gfbdfa8da05b6 #624 PREEMPT(full)\n[  138.425795][    C1] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n[  138.425800][    C1] Call Trace:\n[  138.425804][    C1]  \u0026lt;IRQ\u0026gt;\n[  138.425808][    C1]  dump_stack_lvl (lib/dump_stack.c:122)\n[  138.425828][    C1]  print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n[  138.425839][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425844][    C1]  ? __virt_addr_valid (./arch/x86/include/asm/preempt.h:95 (discriminator 1) ./include/linux/rcupdate.h:975 (discriminator 1) ./include/linux/mmzone.h:2207 (discriminator 1) arch/x86/mm/physaddr.c:54 (discriminator 1))\n[  138.425853][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425859][    C1]  kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:597)\n[  138.425868][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425878][    C1]  kasan_check_range (mm/kasan/generic.c:186 (discriminator 1) mm/kasan/generic.c:200 (discriminator 1))\n[  138.425884][    C1]  __asan_memset (mm/kasan/shadow.c:84 (discriminator 2))\n[  138.425889][    C1]  ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425893][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:171)\n[  138.425898][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425903][    C1]  ife_encode_meta_u16 (net/sched/act_ife.c:57)\n[  138.425910][    C1]  ? __pfx_do_raw_spin_lock (kernel/locking/spinlock_debug.c:114)\n[  138.425916][    C1]  ? __asan_memcpy (mm/kasan/shadow.c:105 (discriminator 3))\n[  138.425921][    C1]  ? __pfx_ife_encode_meta_u16 (net/sched/act_ife.c:45)\n[  138.425927][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425931][    C1]  tcf_ife_act (net/sched/act_ife.c:847 net/sched/act_ife.c:879)\n\nTo solve this issue, fix the replace behavior by adding the metalist to\nthe ife rcu data structure.(CVE-2026-23378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix memory leak in ice_set_ringparam()\n\nIn ice_set_ringparam, tx_rings and xdp_rings are allocated before\nrx_rings. If the allocation of rx_rings fails, the code jumps to\nthe done label leaking both tx_rings and xdp_rings. Furthermore, if\nthe setup of an individual Rx ring fails during the loop, the code jumps\nto the free_tx label which releases tx_rings but leaks xdp_rings.\n\nFix this by introducing a free_xdp label and updating the error paths to\nensure both xdp_rings and tx_rings are properly freed if rx_rings\nallocation or setup fails.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-23389)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix side-effect bug in match_char() macro usage\n\nThe match_char() macro evaluates its character parameter multiple\ntimes when traversing differential encoding chains. When invoked\nwith *str++, the string pointer advances on each iteration of the\ninner do-while loop, causing the DFA to check different characters\nat each iteration and therefore skip input characters.\nThis results in out-of-bounds reads when the pointer advances past\nthe input buffer boundary.\n\n[   94.984676] ==================================================================\n[   94.985301] BUG: KASAN: slab-out-of-bounds in aa_dfa_match+0x5ae/0x760\n[   94.985655] Read of size 1 at addr ffff888100342000 by task file/976\n\n[   94.986319] CPU: 7 UID: 1000 PID: 976 Comm: file Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[   94.986322] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   94.986329] Call Trace:\n[   94.986341]  \u0026lt;TASK\u0026gt;\n[   94.986347]  dump_stack_lvl+0x5e/0x80\n[   94.986374]  print_report+0xc8/0x270\n[   94.986384]  ? aa_dfa_match+0x5ae/0x760\n[   94.986388]  kasan_report+0x118/0x150\n[   94.986401]  ? aa_dfa_match+0x5ae/0x760\n[   94.986405]  aa_dfa_match+0x5ae/0x760\n[   94.986408]  __aa_path_perm+0x131/0x400\n[   94.986418]  aa_path_perm+0x219/0x2f0\n[   94.986424]  apparmor_file_open+0x345/0x570\n[   94.986431]  security_file_open+0x5c/0x140\n[   94.986442]  do_dentry_open+0x2f6/0x1120\n[   94.986450]  vfs_open+0x38/0x2b0\n[   94.986453]  ? may_open+0x1e2/0x2b0\n[   94.986466]  path_openat+0x231b/0x2b30\n[   94.986469]  ? __x64_sys_openat+0xf8/0x130\n[   94.986477]  do_file_open+0x19d/0x360\n[   94.986487]  do_sys_openat2+0x98/0x100\n[   94.986491]  __x64_sys_openat+0xf8/0x130\n[   94.986499]  do_syscall_64+0x8e/0x660\n[   94.986515]  ? count_memcg_events+0x15f/0x3c0\n[   94.986526]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986540]  ? handle_mm_fault+0x1639/0x1ef0\n[   94.986551]  ? vma_start_read+0xf0/0x320\n[   94.986558]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986561]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986563]  ? fpregs_assert_state_consistent+0x50/0xe0\n[   94.986572]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986574]  ? arch_exit_to_user_mode_prepare+0x9/0xb0\n[   94.986587]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986588]  ? irqentry_exit+0x3c/0x590\n[   94.986595]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   94.986597] RIP: 0033:0x7fda4a79c3ea\n\nFix by extracting the character value before invoking match_char,\nensuring single evaluation per outer loop.(CVE-2026-23406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix missing bounds check on DEFAULT table in verify_dfa()\n\nThe verify_dfa() function only checks DEFAULT_TABLE bounds when the state\nis not differentially encoded.\n\nWhen the verification loop traverses the differential encoding chain,\nit reads k = DEFAULT_TABLE[j] and uses k as an array index without\nvalidation. A malformed DFA with DEFAULT_TABLE[j] \u0026gt;= state_count,\ntherefore, causes both out-of-bounds reads and writes.\n\n[   57.179855] ==================================================================\n[   57.180549] BUG: KASAN: slab-out-of-bounds in verify_dfa+0x59a/0x660\n[   57.180904] Read of size 4 at addr ffff888100eadec4 by task su/993\n\n[   57.181554] CPU: 1 UID: 0 PID: 993 Comm: su Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[   57.181558] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   57.181563] Call Trace:\n[   57.181572]  \u0026lt;TASK\u0026gt;\n[   57.181577]  dump_stack_lvl+0x5e/0x80\n[   57.181596]  print_report+0xc8/0x270\n[   57.181605]  ? verify_dfa+0x59a/0x660\n[   57.181608]  kasan_report+0x118/0x150\n[   57.181620]  ? verify_dfa+0x59a/0x660\n[   57.181623]  verify_dfa+0x59a/0x660\n[   57.181627]  aa_dfa_unpack+0x1610/0x1740\n[   57.181629]  ? __kmalloc_cache_noprof+0x1d0/0x470\n[   57.181640]  unpack_pdb+0x86d/0x46b0\n[   57.181647]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181653]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181656]  ? aa_unpack_nameX+0x1a8/0x300\n[   57.181659]  aa_unpack+0x20b0/0x4c30\n[   57.181662]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181664]  ? stack_depot_save_flags+0x33/0x700\n[   57.181681]  ? kasan_save_track+0x4f/0x80\n[   57.181683]  ? kasan_save_track+0x3e/0x80\n[   57.181686]  ? __kasan_kmalloc+0x93/0xb0\n[   57.181688]  ? __kvmalloc_node_noprof+0x44a/0x780\n[   57.181693]  ? aa_simple_write_to_buffer+0x54/0x130\n[   57.181697]  ? policy_update+0x154/0x330\n[   57.181704]  aa_replace_profiles+0x15a/0x1dd0\n[   57.181707]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181710]  ? __kvmalloc_node_noprof+0x44a/0x780\n[   57.181712]  ? aa_loaddata_alloc+0x77/0x140\n[   57.181715]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181717]  ? _copy_from_user+0x2a/0x70\n[   57.181730]  policy_update+0x17a/0x330\n[   57.181733]  profile_replace+0x153/0x1a0\n[   57.181735]  ? rw_verify_area+0x93/0x2d0\n[   57.181740]  vfs_write+0x235/0xab0\n[   57.181745]  ksys_write+0xb0/0x170\n[   57.181748]  do_syscall_64+0x8e/0x660\n[   57.181762]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   57.181765] RIP: 0033:0x7f6192792eb2\n\nRemove the MATCH_FLAG_DIFF_ENCODE condition to validate all DEFAULT_TABLE\nentries unconditionally.(CVE-2026-23407)\n\nA race condition vulnerability exists in the AppArmor security module of the Linux kernel, leading to a use-after-free issue. This vulnerability can be triggered when an attacker simultaneously opens rawdata files and removes an associated AppArmor profile. Since rawdata inodes are not refcounted, there is a time window during profile removal where the i_private pointer may reference freed memory, causing the system to access freed memory regions. This can result in program crashes, unexpected value usage, or arbitrary code execution, threatening the confidentiality, integrity, and availability of the system.(CVE-2026-23410)\n\nA vulnerability exists in the AppArmor security module of the Linux kernel when handling the i_private field of the inode structure. AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can and does live beyond that point and it is possible that some of the fs callback functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs. While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private. This vulnerability could allow a local attacker to bypass AppArmor\u0026apos;s access control policies through a specially crafted request, leading to privilege escalation and impacting system confidentiality, integrity, and availability.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: fix NULL deref caused by udp_sock_create6 when CONFIG_IPV6=n\n\nWhen CONFIG_IPV6 is disabled, the udp_sock_create6() function returns 0\n(success) without actually creating a socket. Callers such as\nfou_create() then proceed to dereference the uninitialized socket\npointer, resulting in a NULL pointer dereference.\n\nThe captured NULL deref crash:\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  RIP: 0010:fou_nl_add_doit (net/ipv4/fou_core.c:590 net/ipv4/fou_core.c:764)\n  [...]\n  Call Trace:\n    \u0026lt;TASK\u0026gt;\n    genl_family_rcv_msg_doit.constprop.0 (net/netlink/genetlink.c:1114)\n    genl_rcv_msg (net/netlink/genetlink.c:1194 net/netlink/genetlink.c:1209)\n    [...]\n    netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n    genl_rcv (net/netlink/genetlink.c:1219)\n    netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n    netlink_sendmsg (net/netlink/af_netlink.c:1894)\n    __sock_sendmsg (net/socket.c:727 (discriminator 1) net/socket.c:742 (discriminator 1))\n    __sys_sendto (./include/linux/file.h:62 (discriminator 1) ./include/linux/file.h:83 (discriminator 1) net/socket.c:2183 (discriminator 1))\n    __x64_sys_sendto (net/socket.c:2213 (discriminator 1) net/socket.c:2209 (discriminator 1) net/socket.c:2209 (discriminator 1))\n    do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n    entry_SYSCALL_64_after_hwframe (net/arch/x86/entry/entry_64.S:130)\n\nThis patch makes udp_sock_create6 return -EPFNOSUPPORT instead, so\ncallers correctly take their error paths. There is only one caller of\nthe vulnerable function and only privileged users can trigger it.(CVE-2026-23439)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix race condition during IPSec ESN update\n\nIn IPSec full offload mode, the device reports an ESN (Extended\nSequence Number) wrap event to the driver. The driver validates this\nevent by querying the IPSec ASO and checking that the esn_event_arm\nfield is 0x0, which indicates an event has occurred. After handling\nthe event, the driver must re-arm the context by setting esn_event_arm\nback to 0x1.\n\nA race condition exists in this handling path. After validating the\nevent, the driver calls mlx5_accel_esp_modify_xfrm() to update the\nkernel\u0026apos;s xfrm state. This function temporarily releases and\nre-acquires the xfrm state lock.\n\nSo, need to acknowledge the event first by setting esn_event_arm to\n0x1. This prevents the driver from reprocessing the same ESN update if\nthe hardware sends events for other reason. Since the next ESN update\nonly occurs after nearly 2^31 packets are received, there\u0026apos;s no risk of\nmissing an update, as it will happen long after this handling has\nfinished.\n\nProcessing the event twice causes the ESN high-order bits (esn_msb) to\nbe incremented incorrectly. The driver then programs the hardware with\nthis invalid ESN state, which leads to anti-replay failures and a\ncomplete halt of IPSec traffic.\n\nFix this by re-arming the ESN event immediately after it is validated,\nbefore calling mlx5_accel_esp_modify_xfrm(). This ensures that any\nspurious, duplicate events are correctly ignored, closing the race\nwindow.(CVE-2026-23440)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Prevent concurrent access to IPSec ASO context\n\nThe query or updating IPSec offload object is through Access ASO WQE.\nThe driver uses a single mlx5e_ipsec_aso struct for each PF, which\ncontains a shared DMA-mapped context for all ASO operations.\n\nA race condition exists because the ASO spinlock is released before\nthe hardware has finished processing WQE. If a second operation is\ninitiated immediately after, it overwrites the shared context in the\nDMA area.\n\nWhen the first operation\u0026apos;s completion is processed later, it reads\nthis corrupted context, leading to unexpected behavior and incorrect\nresults.\n\nThis commit fixes the race by introducing a private context within\neach IPSec offload object. The shared ASO context is now copied to\nthis private context while the ASO spinlock is held. Subsequent\nprocessing uses this saved, per-object context, ensuring its integrity\nis maintained.(CVE-2026-23441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure\n\nieee80211_tx_prepare_skb() has three error paths, but only two of them\nfree the skb. The first error path (ieee80211_tx_prepare() returning\nTX_DROP) does not free it, while invoke_tx_handlers() failure and the\nfragmentation check both do.\n\nAdd kfree_skb() to the first error path so all three are consistent,\nand remove the now-redundant frees in callers (ath9k, mt76,\nmac80211_hwsim) to avoid double-free.\n\nDocument the skb ownership guarantee in the function\u0026apos;s kdoc.(CVE-2026-23444)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check\n\ncdc_ncm_rx_verify_ndp16() validates that the NDP header and its DPE\nentries fit within the skb. The first check correctly accounts for\nndpoffset:\n\n  if ((ndpoffset + sizeof(struct usb_cdc_ncm_ndp16)) \u0026gt; skb_in-\u0026gt;len)\n\nbut the second check omits it:\n\n  if ((sizeof(struct usb_cdc_ncm_ndp16) +\n       ret * (sizeof(struct usb_cdc_ncm_dpe16))) \u0026gt; skb_in-\u0026gt;len)\n\nThis validates the DPE array size against the total skb length as if\nthe NDP were at offset 0, rather than at ndpoffset. When the NDP is\nplaced near the end of the NTB (large wNdpIndex), the DPE entries can\nextend past the skb data buffer even though the check passes.\ncdc_ncm_rx_fixup() then reads out-of-bounds memory when iterating\nthe DPE array.\n\nAdd ndpoffset to the nframes bounds check and use struct_size_t() to\nexpress the NDP-plus-DPE-array size more clearly.(CVE-2026-23448)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock()\n\nSyzkaller reported a panic in smc_tcp_syn_recv_sock() [1].\n\nsmc_tcp_syn_recv_sock() is called in the TCP receive path\n(softirq) via icsk_af_ops-\u0026gt;syn_recv_sock on the clcsock (TCP\nlistening socket). It reads sk_user_data to get the smc_sock\npointer. However, when the SMC listen socket is being closed\nconcurrently, smc_close_active() sets clcsock-\u0026gt;sk_user_data\nto NULL under sk_callback_lock, and then the smc_sock itself\ncan be freed via sock_put() in smc_release().\n\nThis leads to two issues:\n\n1) NULL pointer dereference: sk_user_data is NULL when\n   accessed.\n2) Use-after-free: sk_user_data is read as non-NULL, but the\n   smc_sock is freed before its fields (e.g., queued_smc_hs,\n   ori_af_ops) are accessed.\n\nThe race window looks like this (the syzkaller crash [1]\ntriggers via the SYN cookie path: tcp_get_cookie_sock() -\u0026gt;\nsmc_tcp_syn_recv_sock(), but the normal tcp_check_req() path\nhas the same race):\n\n  CPU A (softirq)              CPU B (process ctx)\n\n  tcp_v4_rcv()\n    TCP_NEW_SYN_RECV:\n    sk = req-\u0026gt;rsk_listener\n    sock_hold(sk)\n    /* No lock on listener */\n                               smc_close_active():\n                                 write_lock_bh(cb_lock)\n                                 sk_user_data = NULL\n                                 write_unlock_bh(cb_lock)\n                                 ...\n                                 smc_clcsock_release()\n                                 sock_put(smc-\u0026gt;sk) x2\n                                   -\u0026gt; smc_sock freed!\n    tcp_check_req()\n      smc_tcp_syn_recv_sock():\n        smc = user_data(sk)\n          -\u0026gt; NULL or dangling\n        smc-\u0026gt;queued_smc_hs\n          -\u0026gt; crash!\n\nNote that the clcsock and smc_sock are two independent objects\nwith separate refcounts. TCP stack holds a reference on the\nclcsock, which keeps it alive, but this does NOT prevent the\nsmc_sock from being freed.\n\nFix this by using RCU and refcount_inc_not_zero() to safely\naccess smc_sock. Since smc_tcp_syn_recv_sock() is called in\nthe TCP three-way handshake path, taking read_lock_bh on\nsk_callback_lock is too heavy and would not survive a SYN\nflood attack. Using rcu_read_lock() is much more lightweight.\n\n- Set SOCK_RCU_FREE on the SMC listen socket so that\n  smc_sock freeing is deferred until after the RCU grace\n  period. This guarantees the memory is still valid when\n  accessed inside rcu_read_lock().\n- Use rcu_read_lock() to protect reading sk_user_data.\n- Use refcount_inc_not_zero(\u0026amp;smc-\u0026gt;sk.sk_refcnt) to pin the\n  smc_sock. If the refcount has already reached zero (close\n  path completed), it returns false and we bail out safely.\n\nNote: smc_hs_congested() has a similar lockless read of\nsk_user_data without rcu_read_lock(), but it only checks for\nNULL and accesses the global smc_hs_wq, never dereferencing\nany smc_sock field, so it is not affected.\n\nReproducer was verified with mdelay injection and smc_run,\nthe issue no longer occurs with this patch applied.\n\n[1] https://syzkaller.appspot.com/bug?extid=827ae2bfb3a3529333e9(CVE-2026-23450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM: runtime: Fix a race condition related to device removal\n\nThe following code in pm_runtime_work() may dereference the dev-\u0026gt;parent\npointer after the parent device has been freed:\n\n\t/* Maybe the parent is now able to suspend. */\n\tif (parent \u0026amp;\u0026amp; !parent-\u0026gt;power.ignore_children) {\n\t\tspin_unlock(\u0026amp;dev-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;parent-\u0026gt;power.lock);\n\t\trpm_idle(parent, RPM_ASYNC);\n\t\tspin_unlock(\u0026amp;parent-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;dev-\u0026gt;power.lock);\n\t}\n\nFix this by inserting a flush_work() call in pm_runtime_remove().\n\nWithout this patch blktest block/001 triggers the following complaint\nsporadically:\n\nBUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160\nRead of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081\nWorkqueue: pm pm_runtime_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x61/0x80\n print_address_description.constprop.0+0x8b/0x310\n print_report+0xfd/0x1d7\n kasan_report+0xd8/0x1d0\n __kasan_check_byte+0x42/0x60\n lock_acquire.part.0+0x38/0x230\n lock_acquire+0x70/0x160\n _raw_spin_lock+0x36/0x50\n rpm_suspend+0xc6a/0xfe0\n rpm_idle+0x578/0x770\n pm_runtime_work+0xee/0x120\n process_one_work+0xde3/0x1410\n worker_thread+0x5eb/0xfe0\n kthread+0x37b/0x480\n ret_from_fork+0x6cb/0x920\n ret_from_fork_asm+0x11/0x20\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_alloc_info+0x3d/0x50\n __kasan_kmalloc+0xa0/0xb0\n __kmalloc_noprof+0x311/0x990\n scsi_alloc_target+0x122/0xb60 [scsi_mod]\n __scsi_scan_target+0x101/0x460 [scsi_mod]\n scsi_scan_channel+0x179/0x1c0 [scsi_mod]\n scsi_scan_host_selected+0x259/0x2d0 [scsi_mod]\n store_scan+0x2d2/0x390 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810\n do_syscall_64+0xee/0xfc0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nFreed by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_free_info+0x3f/0x50\n __kasan_slab_free+0x67/0x80\n kfree+0x225/0x6c0\n scsi_target_dev_release+0x3d/0x60 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_dev_release+0xacf/0x12c0 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_put+0x7f/0xc0 [scsi_mod]\n sdev_store_delete+0xa5/0x120 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810(CVE-2026-23452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user\n\nAfter commit ab4eedb790ca (\u0026quot;Bluetooth: L2CAP: Fix corrupted list in\nhci_chan_del\u0026quot;), l2cap_conn_del() uses conn-\u0026gt;lock to protect access to\nconn-\u0026gt;users. However, l2cap_register_user() and l2cap_unregister_user()\ndon\u0026apos;t use conn-\u0026gt;lock, creating a race condition where these functions can\naccess conn-\u0026gt;users and conn-\u0026gt;hchan concurrently with l2cap_conn_del().\n\nThis can lead to use-after-free and list corruption bugs, as reported\nby syzbot.\n\nFix this by changing l2cap_register_user() and l2cap_unregister_user()\nto use conn-\u0026gt;lock instead of hci_dev_lock(), ensuring consistent locking\nfor the l2cap_conn structure.(CVE-2026-23461)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2026-23473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: fix statistics allocation\n\nThe controller per-cpu statistics is not allocated until after the\ncontroller has been registered with driver core, which leaves a window\nwhere accessing the sysfs attributes can trigger a NULL-pointer\ndereference.\n\nFix this by moving the statistics allocation to controller allocation\nwhile tying its lifetime to that of the controller (rather than using\nimplicit devres).(CVE-2026-23475)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix krb5 mount with username option\n\nCustomer reported that some of their krb5 mounts were failing against\na single server as the client was trying to mount the shares with\nwrong credentials.  It turned out the client was reusing SMB session\nfrom first mount to try mounting the other shares, even though a\ndifferent username= option had been specified to the other mounts.\n\nBy using username mount option along with sec=krb5 to search for\nprincipals from keytab is supported by cifs.upcall(8) since\ncifs-utils-4.8.  So fix this by matching username mount option in\nmatch_session() even with Kerberos.\n\nFor example, the second mount below should fail with -ENOKEY as there\nis no \u0026apos;foobar\u0026apos; principal in keytab (/etc/krb5.keytab).  The client\nends up reusing SMB session from first mount to perform the second\none, which is wrong.\n\n```\n$ ktutil\nktutil:  add_entry -password -p testuser -k 1 -e aes256-cts\nPassword for (CVE-2026-31392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/rmap: fix incorrect pte restoration for lazyfree folios\n\nWe batch unmap anonymous lazyfree folios by folio_unmap_pte_batch.  If the\nbatch has a mix of writable and non-writable bits, we may end up setting\nthe entire batch writable.  Fix this by respecting writable bit during\nbatching.\n\nAlthough on a successful unmap of a lazyfree folio, the soft-dirty bit is\nlost, preserve it on pte restoration by respecting the bit during\nbatching, to make the fix consistent w.r.t both writable bit and\nsoft-dirty bit.\n\nI was able to write the below reproducer and crash the kernel. \nExplanation of reproducer (set 64K mTHP to always):\n\nFault in a 64K large folio.  Split the VMA at mid-point with\nMADV_DONTFORK.  fork() - parent points to the folio with 8 writable ptes\nand 8 non-writable ptes.  Merge the VMAs with MADV_DOFORK so that\nfolio_unmap_pte_batch() can determine all the 16 ptes as a batch.  Do\nMADV_FREE on the range to mark the folio as lazyfree.  Write to the memory\nto dirty the pte, eventually rmap will dirty the folio.  Then trigger\nreclaim, we will hit the pte restoration path, and the kernel will crash\nwith the trace given below.\n\nThe BUG happens at:\n\n\tBUG_ON(atomic_inc_return(\u0026amp;ptc-\u0026gt;anon_map_count) \u0026gt; 1 \u0026amp;\u0026amp; rw);\n\nThe code path is asking for anonymous page to be mapped writable into the\npagetable.  The BUG_ON() firing implies that such a writable page has been\nmapped into the pagetables of more than one process, which breaks\nanonymous memory/CoW semantics.\n\n[   21.134473] kernel BUG at mm/page_table_check.c:118!\n[   21.134497] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[   21.135917] Modules linked in:\n[   21.136085] CPU: 1 UID: 0 PID: 1735 Comm: dup-lazyfree Not tainted 7.0.0-rc1-00116-g018018a17770 #1028 PREEMPT\n[   21.136858] Hardware name: linux,dummy-virt (DT)\n[   21.137019] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[   21.137308] pc : page_table_check_set+0x28c/0x2a8\n[   21.137607] lr : page_table_check_set+0x134/0x2a8\n[   21.137885] sp : ffff80008a3b3340\n[   21.138124] x29: ffff80008a3b3340 x28: fffffdffc3d14400 x27: ffffd1a55e03d000\n[   21.138623] x26: 0040000000000040 x25: ffffd1a55f7dd000 x24: 0000000000000001\n[   21.139045] x23: 0000000000000001 x22: 0000000000000001 x21: ffffd1a55f217f30\n[   21.139629] x20: 0000000000134521 x19: 0000000000134519 x18: 005c43e000040000\n[   21.140027] x17: 0001400000000000 x16: 0001700000000000 x15: 000000000000ffff\n[   21.140578] x14: 000000000000000c x13: 005c006000000000 x12: 0000000000000020\n[   21.140828] x11: 0000000000000000 x10: 005c000000000000 x9 : ffffd1a55c079ee0\n[   21.141077] x8 : 0000000000000001 x7 : 005c03e000040000 x6 : 000000004000ffff\n[   21.141490] x5 : ffff00017fffce00 x4 : 0000000000000001 x3 : 0000000000000002\n[   21.141741] x2 : 0000000000134510 x1 : 0000000000000000 x0 : ffff0000c08228c0\n[   21.141991] Call trace:\n[   21.142093]  page_table_check_set+0x28c/0x2a8 (P)\n[   21.142265]  __page_table_check_ptes_set+0x144/0x1e8\n[   21.142441]  __set_ptes_anysz.constprop.0+0x160/0x1a8\n[   21.142766]  contpte_set_ptes+0xe8/0x140\n[   21.142907]  try_to_unmap_one+0x10c4/0x10d0\n[   21.143177]  rmap_walk_anon+0x100/0x250\n[   21.143315]  try_to_unmap+0xa0/0xc8\n[   21.143441]  shrink_folio_list+0x59c/0x18a8\n[   21.143759]  shrink_lruvec+0x664/0xbf0\n[   21.144043]  shrink_node+0x218/0x878\n[   21.144285]  __node_reclaim.constprop.0+0x98/0x338\n[   21.144763]  user_proactive_reclaim+0x2a4/0x340\n[   21.145056]  reclaim_store+0x3c/0x60\n[   21.145216]  dev_attr_store+0x20/0x40\n[   21.145585]  sysfs_kf_write+0x84/0xa8\n[   21.145835]  kernfs_fop_write_iter+0x130/0x1c8\n[   21.145994]  vfs_write+0x2b8/0x368\n[   21.146119]  ksys_write+0x70/0x110\n[   21.146240]  __arm64_sys_write+0x24/0x38\n[   21.146380]  invoke_syscall+0x50/0x120\n[   21.146513]  el0_svc_common.constprop.0+0x48/0xf8\n[   21.146679]  do_el0_svc+0x28/0x40\n[   21.146798]  el0_svc+0x34/0x110\n[   21.146926]  el0t\n---truncated---(CVE-2026-31398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm/bus: Fix potential use after free in asynchronous initialization\n\nDingisoul with KASAN reports a use after free if device_add() fails in\nnd_async_device_register().\n\nCommit b6eae0f61db2 (\u0026quot;libnvdimm: Hold reference on parent while\nscheduling async init\u0026quot;) correctly added a reference on the parent device\nto be held until asynchronous initialization was complete.  However, if\ndevice_add() results in an allocation failure the ref count of the\ndevice drops to 0 prior to the parent pointer being accessed.  Thus\nresulting in use after free.\n\nThe bug bot AI correctly identified the fix.  Save a reference to the\nparent pointer to be used to drop the parent reference regardless of the\noutcome of device_add().(CVE-2026-31399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: fix cache_request leak in cache_release\n\nWhen a reader\u0026apos;s file descriptor is closed while in the middle of reading\na cache_request (rp-\u0026gt;offset != 0), cache_release() decrements the\nrequest\u0026apos;s readers count but never checks whether it should free the\nrequest.\n\nIn cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the\ncache_request is removed from the queue and freed along with its buffer\nand cache_head reference. cache_release() lacks this cleanup.\n\nThe only other path that frees requests with readers == 0 is\ncache_dequeue(), but it runs only when CACHE_PENDING transitions from\nset to clear. If that transition already happened while readers was\nstill non-zero, cache_dequeue() will have skipped the request, and no\nsubsequent call will clean it up.\n\nAdd the same cleanup logic from cache_read() to cache_release(): after\ndecrementing readers, check if it reached 0 with CACHE_PENDING clear,\nand if so, dequeue and free the cache_request.(CVE-2026-31400)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd\n\nThe /proc/fs/nfs/exports proc entry is created at module init\nand persists for the module\u0026apos;s lifetime. exports_proc_open()\ncaptures the caller\u0026apos;s current network namespace and stores\nits svc_export_cache in seq-\u0026gt;private, but takes no reference\non the namespace. If the namespace is subsequently torn down\n(e.g. container destruction after the opener does setns() to a\ndifferent namespace), nfsd_net_exit() calls nfsd_export_shutdown()\nwhich frees the cache. Subsequent reads on the still-open fd\ndereference the freed cache_detail, walking a freed hash table.\n\nHold a reference on the struct net for the lifetime of the open\nfile descriptor. This prevents nfsd_net_exit() from running --\nand thus prevents nfsd_export_shutdown() from freeing the cache\n-- while any exports fd is open. cache_detail already stores\nits net pointer (cd-\u0026gt;net, set by cache_create_net()), so\nexports_release() can retrieve it without additional per-file\nstorage.(CVE-2026-31403)\n\nIn the Linux kernel, the Bluetooth SCO module\u0026apos;s sco_recv_frame() function contains a use-after-free vulnerability. The function reads conn-\u0026gt;sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() operation can free the socket between the lock release and the subsequent sk-\u0026gt;sk_state access, resulting in a use-after-free vulnerability. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold references under the lock. The vulnerability is fixed by using sco_sock_hold() to acquire a reference before releasing the lock and adding sock_put() on all exit paths.(CVE-2026-31408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_fw: fix NULL pointer dereference on shared blocks\n\nThe old-method path in fw_classify() calls tcf_block_q() and\ndereferences q-\u0026gt;handle.  Shared blocks leave block-\u0026gt;q NULL, causing a\nNULL deref when an empty cls_fw filter is attached to a shared block\nand a packet with a nonzero major skb mark is classified.\n\nReject the configuration in fw_change() when the old method (no\nTCA_OPTIONS) is used on a shared block, since fw_classify()\u0026apos;s\nold-method path needs block-\u0026gt;q which is NULL for shared blocks.\n\nThe fixed null-ptr-deref calling stack:\n KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\n RIP: 0010:fw_classify (net/sched/cls_fw.c:81)\n Call Trace:\n  tcf_classify (./include/net/tc_wrapper.h:197 net/sched/cls_api.c:1764 net/sched/cls_api.c:1860)\n  tc_run (net/core/dev.c:4401)\n  __dev_queue_xmit (net/core/dev.c:4535 net/core/dev.c:4790)(CVE-2026-31421)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_flow: fix NULL pointer dereference on shared blocks\n\nflow_change() calls tcf_block_q() and dereferences q-\u0026gt;handle to derive\na default baseclass.  Shared blocks leave block-\u0026gt;q NULL, causing a NULL\nderef when a flow filter without a fully qualified baseclass is created\non a shared block.\n\nCheck tcf_block_shared() before accessing block-\u0026gt;q and return -EINVAL\nfor shared blocks.  This avoids the null-deref shown below:\n\n=======================================================================\nKASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\nRIP: 0010:flow_change (net/sched/cls_flow.c:508)\nCall Trace:\n tc_new_tfilter (net/sched/cls_api.c:2432)\n rtnetlink_rcv_msg (net/core/rtnetlink.c:6980)\n [...]\n=======================================================================(CVE-2026-31422)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: EC: clean up handlers on probe failure in acpi_ec_setup()\n\nWhen ec_install_handlers() returns -EPROBE_DEFER on reduced-hardware\nplatforms, it has already started the EC and installed the address\nspace handler with the struct acpi_ec pointer as handler context.\nHowever, acpi_ec_setup() propagates the error without any cleanup.\n\nThe caller acpi_ec_add() then frees the struct acpi_ec for non-boot\ninstances, leaving a dangling handler context in ACPICA.\n\nAny subsequent AML evaluation that accesses an EC OpRegion field\ndispatches into acpi_ec_space_handler() with the freed pointer,\ncausing a use-after-free:\n\n BUG: KASAN: slab-use-after-free in mutex_lock (kernel/locking/mutex.c:289)\n Write of size 8 at addr ffff88800721de38 by task init/1\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mutex_lock (kernel/locking/mutex.c:289)\n  acpi_ec_space_handler (drivers/acpi/ec.c:1362)\n  acpi_ev_address_space_dispatch (drivers/acpi/acpica/evregion.c:293)\n  acpi_ex_access_region (drivers/acpi/acpica/exfldio.c:246)\n  acpi_ex_field_datum_io (drivers/acpi/acpica/exfldio.c:509)\n  acpi_ex_extract_from_field (drivers/acpi/acpica/exfldio.c:700)\n  acpi_ex_read_data_from_field (drivers/acpi/acpica/exfield.c:327)\n  acpi_ex_resolve_node_to_value (drivers/acpi/acpica/exresolv.c:392)\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 1:\n  acpi_ec_alloc (drivers/acpi/ec.c:1424)\n  acpi_ec_add (drivers/acpi/ec.c:1692)\n\n Freed by task 1:\n  kfree (mm/slub.c:6876)\n  acpi_ec_add (drivers/acpi/ec.c:1751)\n\nThe bug triggers on reduced-hardware EC platforms (ec-\u0026gt;gpe \u0026lt; 0)\nwhen the GPIO IRQ provider defers probing. Once the stale handler\nexists, any unprivileged sysfs read that causes AML to touch an\nEC OpRegion (battery, thermal, backlight) exercises the dangling\npointer.\n\nFix this by calling ec_remove_handlers() in the error path of\nacpi_ec_setup() before clearing first_ec. ec_remove_handlers()\nchecks each EC_FLAGS_* bit before acting, so it is safe to call\nregardless of how far ec_install_handlers() progressed:\n\n  -ENODEV  (handler not installed): only calls acpi_ec_stop()\n  -EPROBE_DEFER (handler installed): removes handler, stops EC(CVE-2026-31426)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skb: fix cross-cache free of KFENCE-allocated skb head\n\nSKB_SMALL_HEAD_CACHE_SIZE is intentionally set to a non-power-of-2\nvalue (e.g. 704 on x86_64) to avoid collisions with generic kmalloc\nbucket sizes. This ensures that skb_kfree_head() can reliably use\nskb_end_offset to distinguish skb heads allocated from\nskb_small_head_cache vs. generic kmalloc caches.\n\nHowever, when KFENCE is enabled, kfence_ksize() returns the exact\nrequested allocation size instead of the slab bucket size. If a caller\n(e.g. bpf_test_init) allocates skb head data via kzalloc() and the\nrequested size happens to equal SKB_SMALL_HEAD_CACHE_SIZE, then\nslab_build_skb() -\u0026gt; ksize() returns that exact value. After subtracting\nskb_shared_info overhead, skb_end_offset ends up matching\nSKB_SMALL_HEAD_HEADROOM, causing skb_kfree_head() to incorrectly free\nthe object to skb_small_head_cache instead of back to the original\nkmalloc cache, resulting in a slab cross-cache free:\n\n  kmem_cache_free(skbuff_small_head): Wrong slab cache. Expected\n  skbuff_small_head but got kmalloc-1k\n\nFix this by always calling kfree(head) in skb_kfree_head(). This keeps\nthe free path generic and avoids allocator-specific misclassification\nfor KFENCE objects.(CVE-2026-31429)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nX.509: Fix out-of-bounds access when parsing extensions\n\nLeo reports an out-of-bounds access when parsing a certificate with\nempty Basic Constraints or Key Usage extension because the first byte of\nthe extension is read before checking its length.  Fix it.\n\nThe bug can be triggered by an unprivileged user by submitting a\nspecially crafted certificate to the kernel through the keyrings(7) API.\nLeo has demonstrated this with a proof-of-concept program responsibly\ndisclosed off-list.(CVE-2026-31430)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix memory leak when a wq is reset\n\nidxd_wq_disable_cleanup() which is called from the reset path for a\nworkqueue, sets the wq type to NONE, which for other parts of the\ndriver mean that the wq is empty (all its resources were released).\n\nOnly set the wq type to NONE after its resources are released.(CVE-2026-31441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix possible invalid memory access after FLR\n\nIn the case that the first Function Level Reset (FLR) concludes\ncorrectly, but in the second FLR the scratch area for the saved\nconfiguration cannot be allocated, it\u0026apos;s possible for a invalid memory\naccess to happen.\n\nAlways set the deallocated scratch area to NULL after FLR completes.(CVE-2026-31442)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix use-after-free in update_super_work when racing with umount\n\nCommit b98535d09179 (\u0026quot;ext4: fix bug_on in start_this_handle during umount\nfilesystem\u0026quot;) moved ext4_unregister_sysfs() before flushing s_sb_upd_work\nto prevent new error work from being queued via /proc/fs/ext4/xx/mb_groups\nreads during unmount. However, this introduced a use-after-free because\nupdate_super_work calls ext4_notify_error_sysfs() -\u0026gt; sysfs_notify() which\naccesses the kobject\u0026apos;s kernfs_node after it has been freed by kobject_del()\nin ext4_unregister_sysfs():\n\n  update_super_work                ext4_put_super\n  -----------------                --------------\n                                   ext4_unregister_sysfs(sb)\n                                     kobject_del(\u0026amp;sbi-\u0026gt;s_kobj)\n                                       __kobject_del()\n                                         sysfs_remove_dir()\n                                           kobj-\u0026gt;sd = NULL\n                                         sysfs_put(sd)\n                                           kernfs_put()  // RCU free\n  ext4_notify_error_sysfs(sbi)\n    sysfs_notify(\u0026amp;sbi-\u0026gt;s_kobj)\n      kn = kobj-\u0026gt;sd              // stale pointer\n      kernfs_get(kn)             // UAF on freed kernfs_node\n                                   ext4_journal_destroy()\n                                     flush_work(\u0026amp;sbi-\u0026gt;s_sb_upd_work)\n\nInstead of reordering the teardown sequence, fix this by making\next4_notify_error_sysfs() detect that sysfs has already been torn down\nby checking s_kobj.state_in_sysfs, and skipping the sysfs_notify() call\nin that case. A dedicated mutex (s_error_notify_mutex) serializes\next4_notify_error_sysfs() against kobject_del() in ext4_unregister_sysfs()\nto prevent TOCTOU races where the kobject could be deleted between the\nstate_in_sysfs check and the sysfs_notify() call.(CVE-2026-31446)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: validate p_idx bounds in ext4_ext_correct_indexes\n\next4_ext_correct_indexes() walks up the extent tree correcting\nindex entries when the first extent in a leaf is modified. Before\naccessing path[k].p_idx-\u0026gt;ei_block, there is no validation that\np_idx falls within the valid range of index entries for that\nlevel.\n\nIf the on-disk extent header contains a corrupted or crafted\neh_entries value, p_idx can point past the end of the allocated\nbuffer, causing a slab-out-of-bounds read.\n\nFix this by validating path[k].p_idx against EXT_LAST_INDEX() at\nboth access sites: before the while loop and inside it. Return\n-EFSCORRUPTED if the index pointer is out of range, consistent\nwith how other bounds violations are handled in the ext4 extent\ntree code.(CVE-2026-31449)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: publish jinode after initialization\n\next4_inode_attach_jinode() publishes ei-\u0026gt;jinode to concurrent users.\nIt used to set ei-\u0026gt;jinode before jbd2_journal_init_jbd_inode(),\nallowing a reader to observe a non-NULL jinode with i_vfs_inode\nstill unset.\n\nThe fast commit flush path can then pass this jinode to\njbd2_wait_inode_data(), which dereferences i_vfs_inode-\u0026gt;i_mapping and\nmay crash.\n\nBelow is the crash I observe:\n```\nBUG: unable to handle page fault for address: 000000010beb47f4\nPGD 110e51067 P4D 110e51067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\nRIP: 0010:xas_find_marked+0x3d/0x2e0\nCode: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f \u0026lt;49\u0026gt; 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02\nRSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246\nRAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003\nRDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10\nRBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec\nR10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000\nR13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88\nFS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;TASK\u0026gt;\nfilemap_get_folios_tag+0x87/0x2a0\n__filemap_fdatawait_range+0x5f/0xd0\n? srso_alias_return_thunk+0x5/0xfbef5\n? __schedule+0x3e7/0x10c0\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? cap_safe_nice+0x37/0x70\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\nfilemap_fdatawait_range_keep_errors+0x12/0x40\next4_fc_commit+0x697/0x8b0\n? ext4_file_write_iter+0x64b/0x950\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? vfs_write+0x356/0x480\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\next4_sync_file+0xf7/0x370\ndo_fsync+0x3b/0x80\n? syscall_trace_enter+0x108/0x1d0\n__x64_sys_fdatasync+0x16/0x20\ndo_syscall_64+0x62/0x2c0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\n...\n```\n\nFix this by initializing the jbd2_inode first.\nUse smp_wmb() and WRITE_ONCE() to publish ei-\u0026gt;jinode after\ninitialization. Readers use READ_ONCE() to fetch the pointer.(CVE-2026-31450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: replace BUG_ON with proper error handling in ext4_read_inline_folio\n\nReplace BUG_ON() with proper error handling when inline data size\nexceeds PAGE_SIZE. This prevents kernel panic and allows the system to\ncontinue running while properly reporting the filesystem corruption.\n\nThe error is logged via ext4_error_inode(), the buffer head is released\nto prevent memory leak, and -EFSCORRUPTED is returned to indicate\nfilesystem corruption.(CVE-2026-31451)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: convert inline data to extents when truncate exceeds inline size\n\nAdd a check in ext4_setattr() to convert files from inline data storage\nto extent-based storage when truncate() grows the file size beyond the\ninline capacity. This prevents the filesystem from entering an\ninconsistent state where the inline data flag is set but the file size\nexceeds what can be stored inline.\n\nWithout this fix, the following sequence causes a kernel BUG_ON():\n\n1. Mount filesystem with inode that has inline flag set and small size\n2. truncate(file, 50MB) - grows size but inline flag remains set\n3. sendfile() attempts to write data\n4. ext4_write_inline_data() hits BUG_ON(write_size \u0026gt; inline_capacity)\n\nThe crash occurs because ext4_write_inline_data() expects inline storage\nto accommodate the write, but the actual inline capacity (~60 bytes for\ni_block + ~96 bytes for xattrs) is far smaller than the file size and\nwrite request.\n\nThe fix checks if the new size from setattr exceeds the inode\u0026apos;s actual\ninline capacity (EXT4_I(inode)-\u0026gt;i_inline_size) and converts the file to\nextent-based storage before proceeding with the size change.\n\nThis addresses the root cause by ensuring the inline data flag and file\nsize remain consistent during truncate operations.(CVE-2026-31452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: add GFP_NOIO in the bio completion if needed\n\nThe bio completion path in the process context (e.g. dm-verity)\nwill directly call into decompression rather than trigger another\nworkqueue context for minimal scheduling latencies, which can\nthen call vm_map_ram() with GFP_KERNEL.\n\nDue to insufficient memory, vm_map_ram() may generate memory\nswapping I/O, which can cause submit_bio_wait to deadlock\nin some scenarios.\n\nTrimmed down the call stack, as follows:\n\nf2fs_submit_read_io\n  submit_bio                      //bio_list is initialized.\n    mmc_blk_mq_recovery\n      z_erofs_endio\n        vm_map_ram\n          __pte_alloc_kernel\n            __alloc_pages_direct_reclaim\n              shrink_folio_list\n                __swap_writepage\n                  submit_bio_wait  //bio_list is non-NULL, hang!!!\n\nUse memalloc_noio_{save,restore}() to wrap up this path.(CVE-2026-31467)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n\nA UAF issue occurs when the virtio_net driver is configured with napi_tx=N\nand the device\u0026apos;s IFF_XMIT_DST_RELEASE flag is cleared\n(e.g., during the configuration of tc route filter rules).\n\nWhen IFF_XMIT_DST_RELEASE is removed from the net_device, the network stack\nexpects the driver to hold the reference to skb-\u0026gt;dst until the packet\nis fully transmitted and freed. In virtio_net with napi_tx=N,\nskbs may remain in the virtio transmit ring for an extended period.\n\nIf the network namespace is destroyed while these skbs are still pending,\nthe corresponding dst_ops structure has freed. When a subsequent packet\nis transmitted, free_old_xmit() is triggered to clean up old skbs.\nIt then calls dst_release() on the skb associated with the stale dst_entry.\nSince the dst_ops (referenced by the dst_entry) has already been freed,\na UAF kernel paging request occurs.\n\nfix it by adds skb_dst_drop(skb) in start_xmit to explicitly release\nthe dst reference before the skb is queued in virtio_net.\n\nCall Trace:\n Unable to handle kernel paging request at virtual address ffff80007e150000\n CPU: 2 UID: 0 PID: 6236 Comm: ping Kdump: loaded Not tainted 7.0.0-rc1+ #6 PREEMPT\n  ...\n  percpu_counter_add_batch+0x3c/0x158 lib/percpu_counter.c:98 (P)\n  dst_release+0xe0/0x110  net/core/dst.c:177\n  skb_release_head_state+0xe8/0x108 net/core/skbuff.c:1177\n  sk_skb_reason_drop+0x54/0x2d8 net/core/skbuff.c:1255\n  dev_kfree_skb_any_reason+0x64/0x78 net/core/dev.c:3469\n  napi_consume_skb+0x1c4/0x3a0 net/core/skbuff.c:1527\n  __free_old_xmit+0x164/0x230  drivers/net/virtio_net.c:611 [virtio_net]\n  free_old_xmit drivers/net/virtio_net.c:1081 [virtio_net]\n  start_xmit+0x7c/0x530 drivers/net/virtio_net.c:3329 [virtio_net]\n  ...\n\nReproduction Steps:\nNETDEV=\u0026quot;enp3s0\u0026quot;\n\nconfig_qdisc_route_filter() {\n    tc qdisc del dev $NETDEV root\n    tc qdisc add dev $NETDEV root handle 1: prio\n    tc filter add dev $NETDEV parent 1:0 \\\n\tprotocol ip prio 100 route to 100 flowid 1:1\n    ip route add 192.168.1.100/32 dev $NETDEV realm 100\n}\n\ntest_ns() {\n    ip netns add testns\n    ip link set $NETDEV netns testns\n    ip netns exec testns ifconfig $NETDEV  10.0.32.46/24\n    ip netns exec testns ping -c 1 10.0.32.1\n    ip netns del testns\n}\n\nconfig_qdisc_route_filter\n\ntest_ns\nsleep 2\ntest_ns(CVE-2026-31469)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: use generic driver_override infrastructure\n\nWhen a driver is probed through __driver_attach(), the bus\u0026apos; match()\ncallback is called without the device lock held, thus accessing the\ndriver_override field without a lock, which can cause a UAF.\n\nFix this by using the driver-core driver_override infrastructure taking\ncare of proper locking internally.\n\nNote that calling match() from __driver_attach() without the device lock\nheld is intentional. [1]\n\nAlso note that we do not enable the driver_override feature of struct\nbus_type, as SPI - in contrast to most other buses - passes \u0026quot;\u0026quot; to\nsysfs_emit() when the driver_override pointer is NULL. Thus, printing\n\u0026quot;\\n\u0026quot; instead of \u0026quot;(null)\\n\u0026quot;.(CVE-2026-31487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: use netlink policy range checks\n\nReplace manual range and mask validations with netlink policy\nannotations in ctnetlink code paths, so that the netlink core rejects\ninvalid values early and can generate extack errors.\n\n- CTA_PROTOINFO_TCP_STATE: reject values \u0026gt; TCP_CONNTRACK_SYN_SENT2 at\n  policy level, removing the manual \u0026gt;= TCP_CONNTRACK_MAX check.\n- CTA_PROTOINFO_TCP_WSCALE_ORIGINAL/REPLY: reject values \u0026gt; TCP_MAX_WSCALE\n  (14). The normal TCP option parsing path already clamps to this value,\n  but the ctnetlink path accepted 0-255, causing undefined behavior when\n  used as a u32 shift count.\n- CTA_FILTER_ORIG_FLAGS/REPLY_FLAGS: use NLA_POLICY_MASK with\n  CTA_FILTER_F_ALL, removing the manual mask checks.\n- CTA_EXPECT_FLAGS: use NLA_POLICY_MASK with NF_CT_EXPECT_MASK, adding\n  a new mask define grouping all valid expect flags.\n\nExtracted from a broader nf-next patch by Florian Westphal, scoped to\nctnetlink for the fixes tree.(CVE-2026-31495)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conntrack_expect: skip expectations in other netns via proc\n\nSkip expectations that do not reside in this netns.\n\nSimilar to e77e6ff502ea (\u0026quot;netfilter: conntrack: do not dump other netns\u0026apos;s\nconntrack entries via proc\u0026quot;).(CVE-2026-31496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop\n\nl2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED\nstate to support L2CAP reconfiguration (e.g. MTU changes). However,\nsince both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from\nthe initial configuration, the reconfiguration path falls through to\nl2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and\nretrans_list without freeing the previous allocations and sets\nchan-\u0026gt;sdu to NULL without freeing the existing skb. This leaks all\npreviously allocated ERTM resources.\n\nAdditionally, l2cap_parse_conf_req() does not validate the minimum\nvalue of remote_mps derived from the RFC max_pdu_size option. A zero\nvalue propagates to l2cap_segment_sdu() where pdu_len becomes zero,\ncausing the while loop to never terminate since len is never\ndecremented, exhausting all available memory.\n\nFix the double-init by skipping l2cap_ertm_init() and\nl2cap_chan_ready() when the channel is already in BT_CONNECTED state,\nwhile still allowing the reconfiguration parameters to be updated\nthrough l2cap_parse_conf_req(). Also add a pdu_len zero check in\nl2cap_segment_sdu() as a safeguard.(CVE-2026-31498)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix deadlock in l2cap_conn_del()\n\nl2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer\nand id_addr_timer while holding conn-\u0026gt;lock. However, the work functions\nl2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire\nconn-\u0026gt;lock, creating a potential AB-BA deadlock if the work is already\nexecuting when l2cap_conn_del() takes the lock.\n\nMove the work cancellations before acquiring conn-\u0026gt;lock and use\ndisable_delayed_work_sync() to additionally prevent the works from\nbeing rearmed after cancellation, consistent with the pattern used in\nhci_conn_del().(CVE-2026-31499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix out-of-bounds writes in iavf_get_ethtool_stats()\n\niavf incorrectly uses real_num_tx_queues for ETH_SS_STATS. Since the\nvalue could change in runtime, we should use num_tx_queues instead.\n\nMoreover iavf_get_ethtool_stats() uses num_active_queues while\niavf_get_sset_count() and iavf_get_stat_strings() use\nreal_num_tx_queues, which triggers out-of-bounds writes when we do\n\u0026quot;ethtool -L\u0026quot; and \u0026quot;ethtool -S\u0026quot; simultaneously [1].\n\nFor example when we change channels from 1 to 8, Thread 3 could be\nscheduled before Thread 2, and out-of-bounds writes could be triggered\nin Thread 3:\n\nThread 1 (ethtool -L)       Thread 2 (work)        Thread 3 (ethtool -S)\niavf_set_channels()\n...\niavf_alloc_queues()\n-\u0026gt; num_active_queues = 8\niavf_schedule_finish_config()\n                                                   iavf_get_sset_count()\n                                                   real_num_tx_queues: 1\n                                                   -\u0026gt; buffer for 1 queue\n                                                   iavf_get_ethtool_stats()\n                                                   num_active_queues: 8\n                                                   -\u0026gt; out-of-bounds!\n                            iavf_finish_config()\n                            -\u0026gt; real_num_tx_queues = 8\n\nUse immutable num_tx_queues in all related functions to avoid the issue.\n\n[1]\n BUG: KASAN: vmalloc-out-of-bounds in iavf_add_one_ethtool_stat+0x200/0x270\n Write of size 8 at addr ffffc900031c9080 by task ethtool/5800\n\n CPU: 1 UID: 0 PID: 5800 Comm: ethtool Not tainted 6.19.0-enjuk-08403-g8137e3db7f1c #241 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x6f/0xb0\n  print_report+0x170/0x4f3\n  kasan_report+0xe1/0x180\n  iavf_add_one_ethtool_stat+0x200/0x270\n  iavf_get_ethtool_stats+0x14c/0x2e0\n  __dev_ethtool+0x3d0c/0x5830\n  dev_ethtool+0x12d/0x270\n  dev_ioctl+0x53c/0xe30\n  sock_do_ioctl+0x1a9/0x270\n  sock_ioctl+0x3d4/0x5e0\n  __x64_sys_ioctl+0x137/0x1c0\n  do_syscall_64+0xf3/0x690\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n RIP: 0033:0x7f7da0e6e36d\n ...\n  \u0026lt;/TASK\u0026gt;\n\n The buggy address belongs to a 1-page vmalloc region starting at 0xffffc900031c9000 allocated at __dev_ethtool+0x3cc9/0x5830\n The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000\n index:0xffff88813a013de0 pfn:0x13a013\n flags: 0x200000000000000(node=0|zone=2)\n raw: 0200000000000000 0000000000000000 dead000000000122 0000000000000000\n raw: ffff88813a013de0 0000000000000000 00000001ffffffff 0000000000000000\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffffc900031c8f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n \u0026gt;ffffc900031c9080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n                    ^\n  ffffc900031c9100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9180: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8(CVE-2026-31505)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb\n\nBefore using sk pointer, check if it is null.\n\nFix the following:\n\n KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267]\n CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025\n Workqueue: events l2cap_info_timeout\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n veth0_macvtap: entered promiscuous mode\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __kasan_check_byte+0x12/0x40\n  lock_acquire+0x79/0x2e0\n  lock_sock_nested+0x48/0x100\n  ? l2cap_sock_ready_cb+0x46/0x160\n  l2cap_sock_ready_cb+0x46/0x160\n  l2cap_conn_start+0x779/0xff0\n  ? __pfx_l2cap_conn_start+0x10/0x10\n  ? l2cap_info_timeout+0x60/0xa0\n  ? __pfx___mutex_lock+0x10/0x10\n  l2cap_info_timeout+0x68/0xa0\n  ? process_scheduled_works+0xa8d/0x18c0\n  process_scheduled_works+0xb6e/0x18c0\n  ? __pfx_process_scheduled_works+0x10/0x10\n  ? assign_work+0x3d5/0x5e0\n  worker_thread+0xa53/0xfc0\n  kthread+0x388/0x470\n  ? __pfx_worker_thread+0x10/0x10\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x51e/0xb90\n  ? __pfx_ret_from_fork+0x10/0x10\n veth1_macvtap: entered promiscuous mode\n  ? __switch_to+0xc7d/0x1450\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\n Modules linked in:\n ---[ end trace 0000000000000000 ]---\n batman_adv: batadv0: Interface activated: batadv_slave_0\n batman_adv: batadv0: Interface activated: batadv_slave_1\n netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n ieee80211 phy39: Selected rate control algorithm \u0026apos;minstrel_ht\u0026apos;\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Kernel panic - not syncing: Fatal exception(CVE-2026-31510)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete\n\nThis fixes the condition checking so mgmt_pending_valid is executed\nwhenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd)\nwould kfree(cmd) without unlinking it from the list first, leaving a\ndangling pointer. Any subsequent list traversal (e.g.,\nmgmt_pending_foreach during __mgmt_power_off, or another\nmgmt_pending_valid call) would dereference freed memory.(CVE-2026-31511)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n\nl2cap_ecred_data_rcv() reads the SDU length field from skb-\u0026gt;data using\nget_unaligned_le16() without first verifying that skb contains at least\nL2CAP_SDULEN_SIZE (2) bytes. When skb-\u0026gt;len is less than 2, this reads\npast the valid data in the skb.\n\nThe ERTM reassembly path correctly calls pskb_may_pull() before reading\nthe SDU length (l2cap_reassemble_sdu, L2CAP_SAR_START case). Apply the\nsame validation to the Enhanced Credit Based Flow Control data path.(CVE-2026-31512)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: prevent policy_hthresh.work from racing with netns teardown\n\nA XFRM_MSG_NEWSPDINFO request can queue the per-net work item\npolicy_hthresh.work onto the system workqueue.\n\nThe queued callback, xfrm_hash_rebuild(), retrieves the enclosing\nstruct net via container_of(). If the net namespace is torn down\nbefore that work runs, the associated struct net may already have\nbeen freed, and xfrm_hash_rebuild() may then dereference stale memory.\n\nxfrm_policy_fini() already flushes policy_hash_work during teardown,\nbut it does not synchronize policy_hthresh.work.\n\nSynchronize policy_hthresh.work in xfrm_policy_fini() as well, so the\nqueued work cannot outlive the net namespace teardown and access a\nfreed struct net.(CVE-2026-31516)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nesp: fix skb leak with espintcp and async crypto\n\nWhen the TX queue for espintcp is full, esp_output_tail_tcp will\nreturn an error and not free the skb, because with synchronous crypto,\nthe common xfrm output code will drop the packet for us.\n\nWith async crypto (esp_output_done), we need to drop the skb when\nesp_output_tail_tcp returns an error.(CVE-2026-31518)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN\n\nThe BPF interpreter\u0026apos;s signed 32-bit division and modulo handlers use\nthe kernel abs() macro on s32 operands. The abs() macro documentation\n(include/linux/math.h) explicitly states the result is undefined when\nthe input is the type minimum. When DST contains S32_MIN (0x80000000),\nabs((s32)DST) triggers undefined behavior and returns S32_MIN unchanged\non arm64/x86. This value is then sign-extended to u64 as\n0xFFFFFFFF80000000, causing do_div() to compute the wrong result.\n\nThe verifier\u0026apos;s abstract interpretation (scalar32_min_max_sdiv) computes\nthe mathematically correct result for range tracking, creating a\nverifier/interpreter mismatch that can be exploited for out-of-bounds\nmap value access.\n\nIntroduce abs_s32() which handles S32_MIN correctly by casting to u32\nbefore negating, avoiding signed overflow entirely. Replace all 8\nabs((s32)...) call sites in the interpreter\u0026apos;s sdiv32/smod32 handlers.\n\ns32 is the only affected case -- the s64 division/modulo handlers do\nnot use abs().(CVE-2026-31525)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Make sure to use pmu_ctx-\u0026gt;pmu for groups\n\nOliver reported that x86_pmu_del() ended up doing an out-of-bound memory access\nwhen group_sched_in() fails and needs to roll back.\n\nThis *should* be handled by the transaction callbacks, but he found that when\nthe group leader is a software event, the transaction handlers of the wrong PMU\nare used. Despite the move_group case in perf_event_open() and group_sched_in()\nusing pmu_ctx-\u0026gt;pmu.\n\nTurns out, inherit uses event-\u0026gt;pmu to clone the events, effectively undoing the\nmove_group case for all inherited contexts. Fix this by also making inherit use\npmu_ctx-\u0026gt;pmu, ensuring all inherited counters end up in the same pmu context.\n\nSimilarly, __perf_event_read() should use equally use pmu_ctx-\u0026gt;pmu for the\ngroup case.(CVE-2026-31528)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: nexthop: allocate skb dynamically in rtm_get_nexthop()\n\nWhen querying a nexthop object via RTM_GETNEXTHOP, the kernel currently\nallocates a fixed-size skb using NLMSG_GOODSIZE. While sufficient for\nsingle nexthops and small Equal-Cost Multi-Path groups, this fixed\nallocation fails for large nexthop groups like 512 nexthops.\n\nThis results in the following warning splat:\n\n WARNING: net/ipv4/nexthop.c:3395 at rtm_get_nexthop+0x176/0x1c0, CPU#20: rep/4608\n [...]\n RIP: 0010:rtm_get_nexthop (net/ipv4/nexthop.c:3395)\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  rtnetlink_rcv_msg (net/core/rtnetlink.c:6989)\n  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n  netlink_sendmsg (net/netlink/af_netlink.c:1894)\n  ____sys_sendmsg (net/socket.c:721 net/socket.c:736 net/socket.c:2585)\n  ___sys_sendmsg (net/socket.c:2641)\n  __sys_sendmsg (net/socket.c:2671)\n  do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n  \u0026lt;/TASK\u0026gt;\n\nFix this by allocating the size dynamically using nh_nlmsg_size() and\nusing nlmsg_new(), this is consistent with nexthop_notify() behavior. In\naddition, adjust nh_nlmsg_size_grp() so it calculates the size needed\nbased on flags passed. While at it, also add the size of NHA_FDB for\nnexthop group size calculation as it was missing too.\n\nThis cannot be reproduced via iproute2 as the group size is currently\nlimited and the command fails as follows:\n\naddattr_l ERROR: message exceeded bound of 1048(CVE-2026-31531)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw: fix ro-\u0026gt;uniq use-after-free in raw_rcv()\n\nraw_release() unregisters raw CAN receive filters via can_rx_unregister(),\nbut receiver deletion is deferred with call_rcu(). This leaves a window\nwhere raw_rcv() may still be running in an RCU read-side critical section\nafter raw_release() frees ro-\u0026gt;uniq, leading to a use-after-free of the\npercpu uniq storage.\n\nMove free_percpu(ro-\u0026gt;uniq) out of raw_release() and into a raw-specific\nsocket destructor. can_rx_unregister() takes an extra reference to the\nsocket and only drops it from the RCU callback, so freeing uniq from\nsk_destruct ensures the percpu area is not released until the relevant\ncallbacks have drained.\n\n[mkl: applied manually](CVE-2026-31532)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: fix use-after-free in -EBUSY error path of tls_do_encryption\n\nThe -EBUSY handling in tls_do_encryption(), introduced by commit\n859054147318 (\u0026quot;net: tls: handle backlogging of crypto requests\u0026quot;), has\na use-after-free due to double cleanup of encrypt_pending and the\nscatterlist entry.\n\nWhen crypto_aead_encrypt() returns -EBUSY, the request is enqueued to\nthe cryptd backlog and the async callback tls_encrypt_done() will be\ninvoked upon completion. That callback unconditionally restores the\nscatterlist entry (sge-\u0026gt;offset, sge-\u0026gt;length) and decrements\nctx-\u0026gt;encrypt_pending. However, if tls_encrypt_async_wait() returns an\nerror, the synchronous error path in tls_do_encryption() performs the\nsame cleanup again, double-decrementing encrypt_pending and\ndouble-restoring the scatterlist.\n\nThe double-decrement corrupts the encrypt_pending sentinel (initialized\nto 1), making tls_encrypt_async_wait() permanently skip the wait for\npending async callbacks. A subsequent sendmsg can then free the\ntls_rec via bpf_exec_tx_verdict() while a cryptd callback is still\npending, resulting in a use-after-free when the callback fires on the\nfreed record.\n\nFix this by skipping the synchronous cleanup when the -EBUSY async\nwait returns an error, since the callback has already handled\nencrypt_pending and sge restoration.(CVE-2026-31533)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gt: Check set_default_submission() before deferencing\n\nWhen the i915 driver firmware binaries are not present, the\nset_default_submission pointer is not set. This pointer is\ndereferenced during suspend anyways.\n\nAdd a check to make sure it is set before dereferencing.\n\n[   23.289926] PM: suspend entry (deep)\n[   23.293558] Filesystems sync: 0.000 seconds\n[   23.298010] Freezing user space processes\n[   23.302771] Freezing user space processes completed (elapsed 0.000 seconds)\n[   23.309766] OOM killer disabled.\n[   23.313027] Freezing remaining freezable tasks\n[   23.318540] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)\n[   23.342038] serial 00:05: disabled\n[   23.345719] serial 00:02: disabled\n[   23.349342] serial 00:01: disabled\n[   23.353782] sd 0:0:0:0: [sda] Synchronizing SCSI cache\n[   23.358993] sd 1:0:0:0: [sdb] Synchronizing SCSI cache\n[   23.361635] ata1.00: Entering standby power mode\n[   23.368863] ata2.00: Entering standby power mode\n[   23.445187] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[   23.452194] #PF: supervisor instruction fetch in kernel mode\n[   23.457896] #PF: error_code(0x0010) - not-present page\n[   23.463065] PGD 0 P4D 0\n[   23.465640] Oops: Oops: 0010 [#1] SMP NOPTI\n[   23.469869] CPU: 8 UID: 0 PID: 211 Comm: kworker/u48:18 Tainted: G S      W           6.19.0-rc4-00020-gf0b9d8eb98df #10 PREEMPT(voluntary)\n[   23.482512] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN\n[   23.496511] Workqueue: async async_run_entry_fn\n[   23.501087] RIP: 0010:0x0\n[   23.503755] Code: Unable to access opcode bytes at 0xffffffffffffffd6.\n[   23.510324] RSP: 0018:ffffb4a60065fca8 EFLAGS: 00010246\n[   23.515592] RAX: 0000000000000000 RBX: ffff9f428290e000 RCX: 000000000000000f\n[   23.522765] RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffff9f428290e000\n[   23.529937] RBP: ffff9f4282907070 R08: ffff9f4281130428 R09: 00000000ffffffff\n[   23.537111] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f42829070f8\n[   23.544284] R13: ffff9f4282906028 R14: ffff9f4282900000 R15: ffff9f4282906b68\n[   23.551457] FS:  0000000000000000(0000) GS:ffff9f466b2cf000(0000) knlGS:0000000000000000\n[   23.559588] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   23.565365] CR2: ffffffffffffffd6 CR3: 000000031c230001 CR4: 0000000000f70ef0\n[   23.572539] PKRU: 55555554\n[   23.575281] Call Trace:\n[   23.577770]  \u0026lt;TASK\u0026gt;\n[   23.579905]  intel_engines_reset_default_submission+0x42/0x60\n[   23.585695]  __intel_gt_unset_wedged+0x191/0x200\n[   23.590360]  intel_gt_unset_wedged+0x20/0x40\n[   23.594675]  gt_sanitize+0x15e/0x170\n[   23.598290]  i915_gem_suspend_late+0x6b/0x180\n[   23.602692]  i915_drm_suspend_late+0x35/0xf0\n[   23.607008]  ? __pfx_pci_pm_suspend_late+0x10/0x10\n[   23.611843]  dpm_run_callback+0x78/0x1c0\n[   23.615817]  device_suspend_late+0xde/0x2e0\n[   23.620037]  async_suspend_late+0x18/0x30\n[   23.624082]  async_run_entry_fn+0x25/0xa0\n[   23.628129]  process_one_work+0x15b/0x380\n[   23.632182]  worker_thread+0x2a5/0x3c0\n[   23.635973]  ? __pfx_worker_thread+0x10/0x10\n[   23.640279]  kthread+0xf6/0x1f0\n[   23.643464]  ? __pfx_kthread+0x10/0x10\n[   23.647263]  ? __pfx_kthread+0x10/0x10\n[   23.651045]  ret_from_fork+0x131/0x190\n[   23.654837]  ? __pfx_kthread+0x10/0x10\n[   23.658634]  ret_from_fork_asm+0x1a/0x30\n[   23.662597]  \u0026lt;/TASK\u0026gt;\n[   23.664826] Modules linked in:\n[   23.667914] CR2: 0000000000000000\n[   23.671271] ------------[ cut here ]------------\n\n(cherry picked from commit daa199abc3d3d1740c9e3a2c3e9216ae5b447cad)(CVE-2026-31540)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/platform/uv: Handle deconfigured sockets\n\nWhen a socket is deconfigured, it\u0026apos;s mapped to SOCK_EMPTY (0xffff). This causes\na panic while allocating UV hub info structures.\n\nFix this by using NUMA_NO_NODE, allowing UV hub info structures to be\nallocated on valid nodes.(CVE-2026-31542)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix NULL deref in bond_debug_rlb_hash_show\n\nrlb_clear_slave intentionally keeps RLB hash-table entries on\nthe rx_hashtbl_used_head list with slave set to NULL when no\nreplacement slave is available. However, bond_debug_rlb_hash_show\nvisites client_info-\u0026gt;slave without checking if it\u0026apos;s NULL.\n\nOther used-list iterators in bond_alb.c already handle this NULL-slave\nstate safely:\n\n- rlb_update_client returns early on !client_info-\u0026gt;slave\n- rlb_req_update_slave_clients, rlb_clear_slave, and rlb_rebalance\ncompare slave values before visiting\n- lb_req_update_subnet_clients continues if slave is NULL\n\nThe following NULL deref crash can be trigger in\nbond_debug_rlb_hash_show:\n\n[    1.289791] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    1.292058] RIP: 0010:bond_debug_rlb_hash_show (drivers/net/bonding/bond_debugfs.c:41)\n[    1.293101] RSP: 0018:ffffc900004a7d00 EFLAGS: 00010286\n[    1.293333] RAX: 0000000000000000 RBX: ffff888102b48200 RCX: ffff888102b48204\n[    1.293631] RDX: ffff888102b48200 RSI: ffffffff839daad5 RDI: ffff888102815078\n[    1.293924] RBP: ffff888102815078 R08: ffff888102b4820e R09: 0000000000000000\n[    1.294267] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100f929c0\n[    1.294564] R13: ffff888100f92a00 R14: 0000000000000001 R15: ffffc900004a7ed8\n[    1.294864] FS:  0000000001395380(0000) GS:ffff888196e75000(0000) knlGS:0000000000000000\n[    1.295239] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    1.295480] CR2: 0000000000000000 CR3: 0000000102adc004 CR4: 0000000000772ef0\n[    1.295897] Call Trace:\n[    1.296134]  seq_read_iter (fs/seq_file.c:231)\n[    1.296341]  seq_read (fs/seq_file.c:164)\n[    1.296493]  full_proxy_read (fs/debugfs/file.c:378 (discriminator 1))\n[    1.296658]  vfs_read (fs/read_write.c:572)\n[    1.296981]  ksys_read (fs/read_write.c:717)\n[    1.297132]  do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n[    1.297325]  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\nAdd a NULL check and print \u0026quot;(none)\u0026quot; for entries with no assigned slave.(CVE-2026-31546)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Clear stale exiting pointer in futex_lock_pi() retry path\n\nFuzzying/stressing futexes triggered:\n\n    WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524\n\nWhen futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY\nand stores a refcounted task pointer in \u0026apos;exiting\u0026apos;.\n\nAfter wait_for_owner_exiting() consumes that reference, the local pointer\nis never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a\ndifferent error, the bogus pointer is passed to wait_for_owner_exiting().\n\n  CPU0\t\t\t     CPU1\t\t       CPU2\n  futex_lock_pi(uaddr)\n  // acquires the PI futex\n  exit()\n    futex_cleanup_begin()\n      futex_state = EXITING;\n\t\t\t     futex_lock_pi(uaddr)\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t attach_to_pi_owner()\n\t\t\t\t   // observes EXITING\n\t\t\t\t   *exiting = owner;  // takes ref\n\t\t\t\t   return -EBUSY\n\t\t\t       wait_for_owner_exiting(-EBUSY, owner)\n\t\t\t\t put_task_struct();   // drops ref\n\t\t\t       // exiting still points to owner\n\t\t\t       goto retry;\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t lock_pi_update_atomic()\n\t\t\t\t   cmpxchg(uaddr)\n\t\t\t\t\t*uaddr ^= WAITERS // whatever\n\t\t\t\t   // value changed\n\t\t\t\t return -EAGAIN;\n\t\t\t       wait_for_owner_exiting(-EAGAIN, exiting) // stale\n\t\t\t\t WARN_ON_ONCE(exiting)\n\nFix this by resetting upon retry, essentially aligning it with requeue_pi.(CVE-2026-31555)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib\n\namdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence\nfrom amdgpu_ib_schedule(). This fence is used to wait for job\ncompletion.\n\nCurrently, the code drops the fence reference using dma_fence_put()\nbefore calling dma_fence_wait().\n\nIf dma_fence_put() releases the last reference, the fence may be\nfreed before dma_fence_wait() is called. This can lead to a\nuse-after-free.\n\nFix this by waiting on the fence first and releasing the reference\nonly after dma_fence_wait() completes.\n\nFixes the below:\ndrivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory \u0026apos;f\u0026apos; (line 696)\n\n(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)(CVE-2026-31566)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: gw: fix OOB heap access in cgw_csum_crc8_rel()\n\ncgw_csum_crc8_rel() correctly computes bounds-safe indices via calc_idx():\n\n    int from = calc_idx(crc8-\u0026gt;from_idx, cf-\u0026gt;len);\n    int to   = calc_idx(crc8-\u0026gt;to_idx,   cf-\u0026gt;len);\n    int res  = calc_idx(crc8-\u0026gt;result_idx, cf-\u0026gt;len);\n\n    if (from \u0026lt; 0 || to \u0026lt; 0 || res \u0026lt; 0)\n        return;\n\nHowever, the loop and the result write then use the raw s8 fields directly\ninstead of the computed variables:\n\n    for (i = crc8-\u0026gt;from_idx; ...)        /* BUG: raw negative index */\n    cf-\u0026gt;data[crc8-\u0026gt;result_idx] = ...;    /* BUG: raw negative index */\n\nWith from_idx = to_idx = result_idx = -64 on a 64-byte CAN FD frame,\ncalc_idx(-64, 64) = 0 so the guard passes, but the loop iterates with\ni = -64, reading cf-\u0026gt;data[-64], and the write goes to cf-\u0026gt;data[-64].\nThis write might end up to 56 (7.0-rc) or 40 (\u0026lt;= 6.19) bytes before the\nstart of the canfd_frame on the heap.\n\nThe companion function cgw_csum_xor_rel() uses `from`/`to`/`res`\ncorrectly throughout; fix cgw_csum_crc8_rel() to match.\n\nConfirmed with KASAN on linux-7.0-rc2:\n  BUG: KASAN: slab-out-of-bounds in cgw_csum_crc8_rel+0x515/0x5b0\n  Read of size 1 at addr ffff8880076619c8 by task poc_cgw_oob/62\n\nTo configure the can-gw crc8 checksums CAP_NET_ADMIN is needed.(CVE-2026-31570)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION\n\nDrop the WARN in sev_pin_memory() on npages overflowing an int, as the\nWARN is comically trivially to trigger from userspace, e.g. by doing:\n\n  struct kvm_enc_region range = {\n          .addr = 0,\n          .size = -1ul,\n  };\n\n  __vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, \u0026amp;range);\n\nNote, the checks in sev_mem_enc_register_region() that presumably exist to\nverify the incoming address+size are completely worthless, as both \u0026quot;addr\u0026quot;\nand \u0026quot;size\u0026quot; are u64s and SEV is 64-bit only, i.e. they _can\u0026apos;t_ be greater\nthan ULONG_MAX.  That wart will be cleaned up in the near future.\n\n\tif (range-\u0026gt;addr \u0026gt; ULONG_MAX || range-\u0026gt;size \u0026gt; ULONG_MAX)\n\t\treturn -EINVAL;\n\nOpportunistically add a comment to explain why the code calculates the\nnumber of pages the \u0026quot;hard\u0026quot; way, e.g. instead of just shifting @ulen.(CVE-2026-31590)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup\n\nDisable the delayed work before clearing BAR mappings and doorbells to\navoid running the handler after resources have been torn down.\n\n  Unable to handle kernel paging request at virtual address ffff800083f46004\n  [...]\n  Internal error: Oops: 0000000096000007 [#1]  SMP\n  [...]\n  Call trace:\n   epf_ntb_cmd_handler+0x54/0x200 [pci_epf_vntb] (P)\n   process_one_work+0x154/0x3b0\n   worker_thread+0x2c8/0x400\n   kthread+0x148/0x210\n   ret_from_fork+0x10/0x20(CVE-2026-31595)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU: Fix FPDSS on Zen1\n\nZen1\u0026apos;s hardware divider can leave, under certain circumstances, partial\nresults from previous operations.  Those results can be leaked by\nanother, attacker thread.\n\nFix that with a chicken bit.(CVE-2026-31628)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: proc: size address buffers for %pISpc output\n\nThe AF_RXRPC procfs helpers format local and remote socket addresses into\nfixed 50-byte stack buffers with \u0026quot;%pISpc\u0026quot;.\n\nThat is too small for the longest current-tree IPv6-with-port form the\nformatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a\ndotted-quad tail not only for v4mapped addresses, but also for ISATAP\naddresses via ipv6_addr_is_isatap().\n\nAs a result, a case such as\n\n  [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535\n\nis possible with the current formatter. That is 50 visible characters, so\n51 bytes including the trailing NUL, which does not fit in the existing\nchar[50] buffers used by net/rxrpc/proc.c.\n\nSize the buffers from the formatter\u0026apos;s maximum textual form and switch the\ncall sites to scnprintf().\n\nChanges since v1:\n- correct the changelog to cite the actual maximum current-tree case\n  explicitly\n- frame the proof around the ISATAP formatting path instead of the earlier\n  mapped-v4 example(CVE-2026-31630)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmmc: vub300: fix NULL-deref on disconnect\n\nMake sure to deregister the controller before dropping the reference to\nthe driver data on disconnect to avoid NULL-pointer dereferences or\nuse-after-free.(CVE-2026-31651)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: fix use-after-free in timeout object destroy\n\nnft_ct_timeout_obj_destroy() frees the timeout object with kfree()\nimmediately after nf_ct_untimeout(), without waiting for an RCU grace\nperiod. Concurrent packet processing on other CPUs may still hold\nRCU-protected references to the timeout object obtained via\nrcu_dereference() in nf_ct_timeout_data().\n\nAdd an rcu_head to struct nf_ct_timeout and use kfree_rcu() to defer\nfreeing until after an RCU grace period, matching the approach already\nused in nfnetlink_cttimeout.c.\n\nKASAN report:\n BUG: KASAN: slab-use-after-free in nf_conntrack_tcp_packet+0x1381/0x29d0\n Read of size 4 at addr ffff8881035fe19c by task exploit/80\n\n Call Trace:\n  nf_conntrack_tcp_packet+0x1381/0x29d0\n  nf_conntrack_in+0x612/0x8b0\n  nf_hook_slow+0x70/0x100\n  __ip_local_out+0x1b2/0x210\n  tcp_sendmsg_locked+0x722/0x1580\n  __sys_sendto+0x2d8/0x320\n\n Allocated by task 75:\n  nft_ct_timeout_obj_init+0xf6/0x290\n  nft_obj_init+0x107/0x1b0\n  nf_tables_newobj+0x680/0x9c0\n  nfnetlink_rcv_batch+0xc29/0xe00\n\n Freed by task 26:\n  nft_obj_destroy+0x3f/0xa0\n  nf_tables_trans_destroy_work+0x51c/0x5c0\n  process_one_work+0x2c4/0x5a0(CVE-2026-31665)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: uinput - fix circular locking dependency with ff-core\n\nA lockdep circular locking dependency warning can be triggered\nreproducibly when using a force-feedback gamepad with uinput (for\nexample, playing ELDEN RING under Wine with a Flydigi Vader 5\ncontroller):\n\n  ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex\n\nThe cycle is caused by four lock acquisition paths:\n\n1. ff upload: input_ff_upload() holds ff-\u0026gt;mutex and calls\n   uinput_dev_upload_effect() -\u0026gt; uinput_request_submit() -\u0026gt;\n   uinput_request_send(), which acquires udev-\u0026gt;mutex.\n\n2. device create: uinput_ioctl_handler() holds udev-\u0026gt;mutex and calls\n   uinput_create_device() -\u0026gt; input_register_device(), which acquires\n   input_mutex.\n\n3. device register: input_register_device() holds input_mutex and\n   calls kbd_connect() -\u0026gt; input_register_handle(), which acquires\n   dev-\u0026gt;mutex.\n\n4. evdev release: evdev_release() calls input_flush_device() under\n   dev-\u0026gt;mutex, which calls input_ff_flush() acquiring ff-\u0026gt;mutex.\n\nFix this by introducing a new state_lock spinlock to protect\nudev-\u0026gt;state and udev-\u0026gt;dev access in uinput_request_send() instead of\nacquiring udev-\u0026gt;mutex.  The function only needs to atomically check\ndevice state and queue an input event into the ring buffer via\nuinput_dev_event() -- both operations are safe under a spinlock\n(ktime_get_ts64() and wake_up_interruptible() do not sleep).  This\nbreaks the ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex link since a spinlock is a leaf in\nthe lock ordering and cannot form cycles with mutexes.\n\nTo keep state transitions visible to uinput_request_send(), protect\nwrites to udev-\u0026gt;state in uinput_create_device() and\nuinput_destroy_device() with the same state_lock spinlock.\n\nAdditionally, move init_completion(\u0026amp;request-\u0026gt;done) from\nuinput_request_send() to uinput_request_submit() before\nuinput_request_reserve_slot().  Once the slot is allocated,\nuinput_flush_requests() may call complete() on it at any time from\nthe destroy path, so the completion must be initialised before the\nrequest becomes visible.\n\nLock ordering after the fix:\n\n  ff-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex (no back-edge)(CVE-2026-31667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_netem: fix out-of-bounds access in packet corruption\n\nIn netem_enqueue(), the packet corruption logic uses\nget_random_u32_below(skb_headlen(skb)) to select an index for\nmodifying skb-\u0026gt;data. When an AF_PACKET TX_RING sends fully non-linear\npackets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.\n\nPassing 0 to get_random_u32_below() takes the variable-ceil slow path\nwhich returns an unconstrained 32-bit random integer. Using this\nunconstrained value as an offset into skb-\u0026gt;data results in an\nout-of-bounds memory access.\n\nFix this by verifying skb_headlen(skb) is non-zero before attempting\nto corrupt the linear data area. Fully non-linear packets will silently\nbypass the corruption logic.(CVE-2026-31675)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - limit RX SG extraction by receive buffer budget\n\nMake af_alg_get_rsgl() limit each RX scatterlist extraction to the\nremaining receive buffer budget.\n\naf_alg_get_rsgl() currently uses af_alg_readable() only as a gate\nbefore extracting data into the RX scatterlist. Limit each extraction\nto the remaining af_alg_rcvbuf(sk) budget so that receive-side\naccounting matches the amount of data attached to the request.\n\nIf skcipher cannot obtain enough RX space for at least one chunk while\nmore data remains to be processed, reject the recvmsg call instead of\nrounding the request length down to zero.(CVE-2026-31677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: defer tunnel netdev_put to RCU release\n\novs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already\ndetached the device. Dropping the netdev reference in destroy can race\nwith concurrent readers that still observe vport-\u0026gt;dev.\n\nDo not release vport-\u0026gt;dev in ovs_netdev_tunnel_destroy(). Instead, let\nvport_netdev_free() drop the reference from the RCU callback, matching\nthe non-tunnel destroy path and avoiding additional synchronization\nunder RTNL.(CVE-2026-31678)\n\nIn the Linux kernel, a memory out-of-bounds access vulnerability exists in the act_csum module\u0026apos;s tcf_csum_act() function when processing nested VLAN headers. When an skb still carries in-payload VLAN tags, the function walks nested VLAN headers directly from skb-\u0026gt;data. The current code reads vlan-\u0026gt;h_vlan_encapsulated_proto and then pulls VLAN_HLEN bytes without first ensuring that the full VLAN header is present in the linear area. If only part of an inner VLAN header is linearized, accessing h_vlan_encapsulated_proto reads past the linear area, and the following skb_pull(VLAN_HLEN) may violate skb invariants.(CVE-2026-31684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ip6t_eui64: reject invalid MAC header for all packets\n\n`eui64_mt6()` derives a modified EUI-64 from the Ethernet source address\nand compares it with the low 64 bits of the IPv6 source address.\n\nThe existing guard only rejects an invalid MAC header when\n`par-\u0026gt;fragoff != 0`. For packets with `par-\u0026gt;fragoff == 0`, `eui64_mt6()`\ncan still reach `eth_hdr(skb)` even when the MAC header is not valid.\n\nFix this by removing the `par-\u0026gt;fragoff != 0` condition so that packets\nwith an invalid MAC header are rejected before accessing `eth_hdr(skb)`.(CVE-2026-31685)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u0026gt;pvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device\u0026apos;s release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they\u0026apos;re called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: \u0026apos;(null)\u0026apos;: is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.(CVE-2026-31689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy ID to userspace if PSP command failed\n\nWhen retrieving the ID for the CPU, don\u0026apos;t attempt to copy the ID blob to\nuserspace if the firmware command failed.  If the failure was due to an\ninvalid length, i.e. the userspace buffer+length was too small, copying\nthe number of bytes _firmware_ requires will overflow the kernel-allocated\nbuffer and leak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 64 at addr ffff8881867f5960 by task syz.0.906/24388\n\n  CPU: 130 UID: 0 PID: 24388 Comm: syz.0.906 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_get_id2+0x361/0x490 ../drivers/crypto/ccp/sev-dev.c:2222\n   sev_ioctl+0x25f/0x490 ../drivers/crypto/ccp/sev-dev.c:2575\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy PDH cert to userspace if PSP command failed\n\nWhen retrieving the PDH cert, don\u0026apos;t attempt to copy the blobs to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff8885c4ab8aa0 by task syz.0.186/21033\n\n  CPU: 51 UID: 0 PID: 21033 Comm: syz.0.186 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc.                                                       Arcadia_IT_80/Arcadia_IT_80, BIOS 34.84.12-0 11/17/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pdh_export+0x3d3/0x7c0 ../drivers/crypto/ccp/sev-dev.c:2347\n   sev_ioctl+0x2a2/0x490 ../drivers/crypto/ccp/sev-dev.c:2568\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31698)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy CSR to userspace if PSP command failed\n\nWhen retrieving the PEK CSR, don\u0026apos;t attempt to copy the blob to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff898144612e20 by task syz.9.219/21405\n\n  CPU: 14 UID: 0 PID: 21405 Comm: syz.9.219 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pek_csr+0x31f/0x590 ../drivers/crypto/ccp/sev-dev.c:1872\n   sev_ioctl+0x3a4/0x490 ../drivers/crypto/ccp/sev-dev.c:2562\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path\n\nsmb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL\nand the default QUERY_INFO path.  The QUERY_INFO branch clamps\nqi.input_buffer_length to the server-reported OutputBufferLength and then\ncopies qi.input_buffer_length bytes from qi_rsp-\u0026gt;Buffer to userspace, but\nit never verifies that the flexible-array payload actually fits within\nrsp_iov[1].iov_len.\n\nA malicious server can return OutputBufferLength larger than the actual\nQUERY_INFO response, causing copy_to_user() to walk past the response\nbuffer and expose adjacent kernel heap to userspace.\n\nGuard the QUERY_INFO copy with a bounds check on the actual Buffer\npayload.  Use struct_size(qi_rsp, Buffer, qi.input_buffer_length)\nrather than an open-coded addition so the guard cannot overflow on\n32-bit builds.(CVE-2026-31708)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: validate ND option lengths in vxlan_na_create\n\nvxlan_na_create() walks ND options according to option-provided\nlengths. A malformed option can make the parser advance beyond the\ncomputed option span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31738)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: br_nd_send: validate ND option lengths\n\nbr_nd_send() walks ND options according to option-provided lengths.\nA malformed option can make the parser advance beyond the computed\noption span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31752)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: fix NULL pointer dereference in ep_queue\n\nWhen the gadget endpoint is disabled or not yet configured, the ep-\u0026gt;desc\npointer can be NULL. This leads to a NULL pointer dereference when\n__cdns3_gadget_ep_queue() is called, causing a kernel crash.\n\nAdd a check to return -ESHUTDOWN if ep-\u0026gt;desc is NULL, which is the\nstandard return code for unconfigured endpoints.\n\nThis prevents potential crashes when ep_queue is called on endpoints\nthat are not ready.(CVE-2026-31755)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: move wake reason storage into validated event handlers\n\nhci_store_wake_reason() is called from hci_event_packet() immediately\nafter stripping the HCI event header but before hci_event_func()\nenforces the per-event minimum payload length from hci_ev_table.\nThis means a short HCI event frame can reach bacpy() before any bounds\ncheck runs.\n\nRather than duplicating skb parsing and per-event length checks inside\nhci_store_wake_reason(), move wake-address storage into the individual\nevent handlers after their existing event-length validation has\nsucceeded. Convert hci_store_wake_reason() into a small helper that only\nstores an already-validated bdaddr while the caller holds hci_dev_lock().\nUse the same helper after hci_event_func() with a NULL address to\npreserve the existing unexpected-wake fallback semantics when no\nvalidated event handler records a wake address.\n\nAnnotate the helper with __must_hold(\u0026amp;hdev-\u0026gt;lock) and add\nlockdep_assert_held(\u0026amp;hdev-\u0026gt;lock) so future call paths keep the lock\ncontract explicit.\n\nCall the helper from hci_conn_request_evt(), hci_conn_complete_evt(),\nhci_sync_conn_complete_evt(), le_conn_complete_evt(),\nhci_le_adv_report_evt(), hci_le_ext_adv_report_evt(),\nhci_le_direct_adv_report_evt(), hci_le_pa_sync_established_evt(), and\nhci_le_past_received_evt().(CVE-2026-31771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: SMP: derive legacy responder STK authentication from MITM state\n\nThe legacy responder path in smp_random() currently labels the stored\nSTK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH.\nThat reflects what the local service requested, not what the pairing\nflow actually achieved.\n\nFor Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear\nand the resulting STK should remain unauthenticated even if the local\nside requested HIGH security. Use the established MITM state when\nstoring the responder STK so the key metadata matches the pairing result.\n\nThis also keeps the legacy path aligned with the Secure Connections code,\nwhich already treats JUST_WORKS/JUST_CFM as unauthenticated.(CVE-2026-31773)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler()\n\nThe memcpy function assumes the dynamic array notif-\u0026gt;matches is at least\nas large as the number of bytes to copy. Otherwise, results-\u0026gt;matches may\ncontain unwanted data. To guarantee safety, extend the validation in one\nof the checks to ensure sufficient packet length.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2026-31779)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ioc32: stop speculation on the drm_compat_ioctl path\n\nThe drm compat ioctl path takes a user controlled pointer, and then\ndereferences it into a table of function pointers, the signature method\nof spectre problems.  Fix this up by calling array_index_nospec() on the\nindex to the function pointer list.(CVE-2026-31781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: validate LTK enc_size on load\n\nLoad Long Term Keys stores the user-provided enc_size and later uses\nit to size fixed-size stack operations when replying to LE LTK\nrequests. An enc_size larger than the 16-byte key buffer can therefore\noverflow the reply stack buffer.\n\nReject oversized enc_size values while validating the management LTK\nrecord so invalid keys never reach the stored key state.(CVE-2026-43020)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: use skb_header_pointer() for TCPv4 GSO frag_off check\n\nSyzbot reported a KMSAN uninit-value warning in gso_features_check()\ncalled from netif_skb_features() [1].\n\ngso_features_check() reads iph-\u0026gt;frag_off to decide whether to clear\nmangleid_features. Accessing the IPv4 header via ip_hdr()/inner_ip_hdr()\ncan rely on skb header offsets that are not always safe for direct\ndereference on packets injected from PF_PACKET paths.\n\nUse skb_header_pointer() for the TCPv4 frag_off check so the header read\nis robust whether data is already linear or needs copying.\n\n[1] https://syzkaller.appspot.com/bug?extid=1543a7d954d9c6d00407(CVE-2026-43036)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak\n\nWhen processing Router Advertisements with user options the kernel\nbuilds an RTM_NEWNDUSEROPT netlink message. The nduseroptmsg struct\nhas three padding fields that are never zeroed and can leak kernel data\n\nThe fix is simple, just zeroes the padding fields.(CVE-2026-43040)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af-alg - fix NULL pointer dereference in scatterwalk\n\nThe AF_ALG interface fails to unmark the end of a Scatter/Gather List (SGL)\nwhen chaining a new af_alg_tsgl structure. If a sendmsg() fills an SGL\nexactly to MAX_SGL_ENTS, the last entry is marked as the end. A subsequent\nsendmsg() allocates a new SGL and chains it, but fails to clear the end\nmarker on the previous SGL\u0026apos;s last data entry.\n\nThis causes the crypto scatterwalk to hit a premature end, returning NULL\non sg_next() and leading to a kernel panic during dereference.\n\nFix this by explicitly unmarking the end of the previous SGL when\nperforming sg_chain() in af_alg_alloc_tsgl().(CVE-2026-43043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: Fix TX deadlock when using DMA\n\n`dmaengine_terminate_async` does not guarantee that the\n`__dma_tx_complete` callback will run. The callback is currently the\nonly place where `dma-\u0026gt;tx_running` gets cleared. If the transaction is\ncanceled and the callback never runs, then `dma-\u0026gt;tx_running` will never\nget cleared and we will never schedule new TX DMA transactions again.\n\nThis change makes it so we clear `dma-\u0026gt;tx_running` after we terminate\nthe DMA transaction. This is \u0026quot;safe\u0026quot; because `serial8250_tx_dma_flush`\nis holding the UART port lock. The first thing the callback does is also\ngrab the UART port lock, so access to `dma-\u0026gt;tx_running` is serialized.(CVE-2026-43061)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix not releasing workqueue on .release()\n\nThe workqueue associated with an DSA/IAA device is not released when\nthe object is freed.(CVE-2026-43064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Skip discovery table for offline dies\n\nThis warning can be triggered if NUMA is disabled and the system\nboots with fewer CPUs than the number of CPUs in die 0.\n\nWARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]\n\nCurrently, the discovery table continues to be parsed even if all CPUs\nin the associated die are offline.  This can lead to an array overflow\nat \u0026quot;pmu-\u0026gt;boxes[die] = box\u0026quot; in uncore_pci_pmu_register(), which may\ntrigger the warning above or cause other issues.(CVE-2026-43079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: icmp: fix null-ptr-deref in icmp_build_probe()\n\nipv6_stub-\u0026gt;ipv6_dev_find() may return ERR_PTR(-EAFNOSUPPORT) when the\nIPv6 stack is not active (CONFIG_IPV6=m and not loaded), and passing\nthis error pointer to dev_hold() will cause a kernel crash with\nnull-ptr-deref.\n\nInstead, silently discard the request. RFC 8335 does not appear to\ndefine a specific response for the case where an IPv6 interface\nidentifier is syntactically valid but the implementation cannot perform\nthe lookup at runtime, and silently dropping the request may safer than\nmisreporting \u0026quot;No Such Interface\u0026quot;.(CVE-2026-43099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/smp: Add check for kcalloc() failure in parse_thread_groups()\n\nAs kcalloc() may fail, check its return value to avoid a NULL pointer\ndereference when passing it to of_property_read_u32_array().(CVE-2026-43148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: enable basic endpoint checking\n\npegasus_probe() fills URBs with hardcoded endpoint pipes without\nverifying the endpoint descriptors:\n\n  - usb_rcvbulkpipe(dev, 1) for RX data\n  - usb_sndbulkpipe(dev, 2) for TX data\n  - usb_rcvintpipe(dev, 3)  for status interrupts\n\nA malformed USB device can present these endpoints with transfer types\nthat differ from what the driver assumes.\n\nAdd a pegasus_usb_ep enum for endpoint numbers, replacing magic\nconstants throughout. Add usb_check_bulk_endpoints() and\nusb_check_int_endpoints() calls before any resource allocation to\nverify endpoint types before use, rejecting devices with mismatched\ndescriptors at probe time, and avoid triggering assertion.\n\nSimilar fix to\n- commit 90b7f2961798 (\u0026quot;net: usb: rtl8150: enable basic endpoint checking\u0026quot;)\n- commit 9e7021d2aeae (\u0026quot;net: usb: catc: enable basic endpoint checking\u0026quot;)(CVE-2026-43156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/bitmap: fix GPF in write_page caused by resize race\n\nA General Protection Fault occurs in write_page() during array resize:\nRIP: 0010:write_page+0x22b/0x3c0 [md_mod]\n\nThis is a use-after-free race between bitmap_daemon_work() and\n__bitmap_resize(). The daemon iterates over `bitmap-\u0026gt;storage.filemap`\nwithout locking, while the resize path frees that storage via\nmd_bitmap_file_unmap(). `quiesce()` does not stop the md thread,\nallowing concurrent access to freed pages.\n\nFix by holding `mddev-\u0026gt;bitmap_info.mutex` during the bitmap update.(CVE-2026-43163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data()\n\nOn the receive path, __ioam6_fill_trace_data() uses trace-\u0026gt;nodelen\nto decide how much data to write for each node. It trusts this field\nas-is from the incoming packet, with no consistency check against\ntrace-\u0026gt;type (the 24-bit field that tells which data items are\npresent). A crafted packet can set nodelen=0 while setting type bits\n0-21, causing the function to write ~100 bytes past the allocated\nregion (into skb_shared_info), which corrupts adjacent heap memory\nand leads to a kernel panic.\n\nAdd a shared helper ioam6_trace_compute_nodelen() in ioam6.c to\nderive the expected nodelen from the type field, and use it:\n\n  - in ioam6_iptunnel.c (send path, existing validation) to replace\n    the open-coded computation;\n  - in exthdrs.c (receive path, ipv6_hop_ioam) to drop packets whose\n    nodelen is inconsistent with the type field, before any data is\n    written.\n\nPer RFC 9197, bits 12-21 are each short (4-octet) fields, so they\nare included in IOAM6_MASK_SHORT_FIELDS (changed from 0xff100000 to\n0xff1ffc00).(CVE-2026-43186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE\n\nThe arch definition of cpumask_of_node() cannot handle NUMA_NO_NODE -\nwhich is a valid index - so add a check for this.(CVE-2026-43212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/kexec: add a sanity check on previous kernel\u0026apos;s ima kexec buffer\n\nWhen the second-stage kernel is booted via kexec with a limiting command\nline such as \u0026quot;mem=\u0026lt;size\u0026gt;\u0026quot;, the physical range that contains the carried\nover IMA measurement list may fall outside the truncated RAM leading to a\nkernel panic.\n\n    BUG: unable to handle page fault for address: ffff97793ff47000\n    RIP: ima_restore_measurement_list+0xdc/0x45a\n    #PF: error_code(0x0000) – not-present page\n\nOther architectures already validate the range with page_is_ram(), as done\nin commit cbf9c4b9617b (\u0026quot;of: check previous kernel\u0026apos;s ima-kexec-buffer\nagainst memory bounds\u0026quot;) do a similar check on x86.\n\nWithout carrying the measurement list across kexec, the attestation\nwould fail.(CVE-2026-43240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fiemap page fault fix\n\nIn gfs2_fiemap(), we are calling iomap_fiemap() while holding the inode\nglock.  This can lead to recursive glock taking if the fiemap buffer is\nmemory mapped to the same inode and accessing it triggers a page fault.\n\nFix by disabling page faults for iomap_fiemap() and faulting in the\nbuffer by hand if necessary.\n\nFixes xfstest generic/742.(CVE-2026-43262)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: supply snapshot context in ceph_zero_partial_object()\n\nThe ceph_zero_partial_object function was missing proper snapshot\ncontext for its OSD write operations, which could lead to data\ninconsistencies in snapshots.\n\nReproducer:\n../src/vstart.sh --new -x --localhost --bluestore\n./bin/ceph auth caps client.fs_a mds \u0026apos;allow rwps fsname=a\u0026apos; mon \u0026apos;allow r fsname=a\u0026apos; osd \u0026apos;allow rw tag cephfs data=a\u0026apos;\nmount -t ceph (CVE-2026-43273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: move ext4_percpu_param_init() before ext4_mb_init()\n\nWhen running `kvm-xfstests -c ext4/1k -C 1 generic/383` with the\n`DOUBLE_CHECK` macro defined, the following panic is triggered:\n\n==================================================================\nEXT4-fs error (device vdc): ext4_validate_block_bitmap:423:\n                        comm mount: bg 0: bad block bitmap checksum\nBUG: unable to handle page fault for address: ff110000fa2cc000\nPGD 3e01067 P4D 3e02067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W\n                        6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none)\nRIP: 0010:percpu_counter_add_batch+0x13/0xa0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_mark_group_bitmap_corrupted+0xcb/0xe0\n ext4_validate_block_bitmap+0x2a1/0x2f0\n ext4_read_block_bitmap+0x33/0x50\n mb_group_bb_bitmap_alloc+0x33/0x80\n ext4_mb_add_groupinfo+0x190/0x250\n ext4_mb_init_backend+0x87/0x290\n ext4_mb_init+0x456/0x640\n __ext4_fill_super+0x1072/0x1680\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n vfs_cmd_create+0x59/0xe0\n __do_sys_fsconfig+0x4f6/0x6b0\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nThis issue can be reproduced using the following commands:\n        mkfs.ext4 -F -q -b 1024 /dev/sda 5G\n        tune2fs -O quota,project /dev/sda\n        mount /dev/sda /tmp/test\n\nWith DOUBLE_CHECK defined, mb_group_bb_bitmap_alloc() reads\nand validates the block bitmap. When the validation fails,\next4_mark_group_bitmap_corrupted() attempts to update\nsbi-\u0026gt;s_freeclusters_counter. However, this percpu_counter has not been\ninitialized yet at this point, which leads to the panic described above.\n\nFix this by moving the execution of ext4_percpu_param_init() to occur\nbefore ext4_mb_init(), ensuring the per-CPU counters are initialized\nbefore they are used.(CVE-2026-43288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node\n\nWhen CONFIG_PAGE_OWNER is enabled, freeing KASAN shadow pages during\nvmalloc cleanup triggers expensive stack unwinding that acquires RCU read\nlocks.  Processing a large purge_list without rescheduling can cause the\ntask to hold CPU for extended periods (10+ seconds), leading to RCU stalls\nand potential OOM conditions.\n\nThe issue manifests in purge_vmap_node() -\u0026gt; kasan_release_vmalloc_node()\nwhere iterating through hundreds or thousands of vmap_area entries and\nfreeing their associated shadow pages causes:\n\n  rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:\n  rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P6229/1:b..l\n  ...\n  task:kworker/0:17 state:R running task stack:28840 pid:6229\n  ...\n  kasan_release_vmalloc_node+0x1ba/0xad0 mm/vmalloc.c:2299\n  purge_vmap_node+0x1ba/0xad0 mm/vmalloc.c:2299\n\nEach call to kasan_release_vmalloc() can free many pages, and with\npage_owner tracking, each free triggers save_stack() which performs stack\nunwinding under RCU read lock.  Without yielding, this creates an\nunbounded RCU critical section.\n\nAdd periodic cond_resched() calls within the loop to allow:\n- RCU grace periods to complete\n- Other tasks to run\n- Scheduler to preempt when needed\n\nThe fix uses need_resched() for immediate response under load, with a\nbatch count of 32 as a guaranteed upper bound to prevent worst-case stalls\neven under light load.(CVE-2026-43292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipa: fix event ring index not programmed for IPA v5.0+\n\nFor IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to\nCH_C_CNTXT_1. The v5.0 register definition intended to define this\nfield in the CH_C_CNTXT_1 fmask array but used the old identifier of\nERINDEX instead of CH_ERINDEX.\n\nWithout a valid event ring, GSI channels could never signal transfer\ncompletions. This caused gsi_channel_trans_quiesce() to block\nforever in wait_for_completion().\n\nAt least for IPA v5.2 this resolves an issue seen where runtime\nsuspend, system suspend, and remoteproc stop all hanged forever. It\nalso meant the IPA data path was completely non functional.(CVE-2026-43345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/kbuf: check if target buffer list is still legacy on recycle\n\nThere\u0026apos;s a gap between when the buffer was grabbed and when it\npotentially gets recycled, where if the list is empty, someone could\u0026apos;ve\nupgraded it to a ring provided type. This can happen if the request\nis forced via io-wq. The legacy recycling is missing checking if the\nbuffer_list still exists, and if it\u0026apos;s of the correct type. Add those\nchecks.(CVE-2026-43366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in process_message_header()\n\nIf the message frame is (maliciously) corrupted in a way that the\nlength of the control segment ends up being less than the size of the\nmessage header or a different frame is made to look like a message\nframe, out-of-bounds reads may ensue in process_message_header().\n\nPerform an explicit bounds check before decoding the message header.(CVE-2026-43406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix memory leaks in ceph_mdsc_build_path()\n\nAdd __putname() calls to error code paths that did not free the \u0026quot;path\u0026quot;\npointer obtained by __getname().  If ownership of this pointer is not\npassed to the caller via path_info.path, the function must free it\nbefore returning.(CVE-2026-43419)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: class: cdc-wdm: fix reordering issue in read code path\n\nQuoting the bug report:\n\nDue to compiler optimization or CPU out-of-order execution, the\ndesc-\u0026gt;length update can be reordered before the memmove. If this\nhappens, wdm_read() can see the new length and call copy_to_user() on\nuninitialized memory. This also violates LKMM data race rules [1].\n\nFix it by using WRITE_ONCE and memory barriers.(CVE-2026-43427)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Limit the length of unkillable synchronous timeouts\n\nThe usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in\nusbcore allow unlimited timeout durations.  And since they use\nuninterruptible waits, this leaves open the possibility of hanging a\ntask for an indefinitely long time, with no way to kill it short of\nunplugging the target device.\n\nTo prevent this sort of problem, enforce a maximum limit on the length\nof these unkillable timeouts.  The limit chosen here, somewhat\narbitrarily, is 60 seconds.  On many systems (although not all) this\nis short enough to avoid triggering the kernel\u0026apos;s hung-task detector.\n\nIn addition, clear up the ambiguity of negative timeout values by\ntreating them the same as 0, i.e., using the maximum allowed timeout.(CVE-2026-43428)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix deadlock between devlink lock and esw-\u0026gt;wq\n\nesw-\u0026gt;work_queue executes esw_functions_changed_event_handler -\u0026gt;\nesw_vfs_changed_event_handler and acquires the devlink lock.\n\n.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -\u0026gt;\nmlx5_devlink_eswitch_mode_set -\u0026gt; mlx5_eswitch_disable_locked -\u0026gt;\nmlx5_eswitch_event_handler_unregister -\u0026gt; flush_workqueue deadlocks\nwhen esw_vfs_changed_event_handler executes.\n\nFix that by no longer flushing the work to avoid the deadlock, and using\na generation counter to keep track of work relevance. This avoids an old\nhandler manipulating an esw that has undergone one or more mode changes:\n- the counter is incremented in mlx5_eswitch_event_handler_unregister.\n- the counter is read and passed to the ephemeral mlx5_host_work struct.\n- the work handler takes the devlink lock and bails out if the current\n  generation is different than the one it was scheduled to operate on.\n- mlx5_eswitch_cleanup does the final draining before destroying the wq.\n\nNo longer flushing the workqueue has the side effect of maybe no longer\ncancelling pending vport_change_handler work items, but that\u0026apos;s ok since\nthose are disabled elsewhere:\n- mlx5_eswitch_disable_locked disables the vport eq notifier.\n- mlx5_esw_vport_disable disarms the HW EQ notification and marks\n  vport-\u0026gt;enabled under state_lock to false to prevent pending vport\n  handler from doing anything.\n- mlx5_eswitch_cleanup destroys the workqueue and makes sure all events\n  are disabled/finished.(CVE-2026-43468)\n\nIn the Linux kernel, the following vulnerability has been resolved:  crypto: pcrypt - Fix handling of MAY_BACKLOG requests  MAY_BACKLOG requests can return EBUSY.  Handle them by checking for that value and filtering out EINPROGRESS notifications.  The Linux kernel CVE team has assigned CVE-2026-43493 to this issue.(CVE-2026-43493)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skbuff: propagate shared-frag marker through frag-transfer helpers\n\nTwo frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail\nto propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()-\u0026gt;flags when\nmoving frags from source to destination.  __pskb_copy_fclone() defers\nthe rest of the shinfo metadata to skb_copy_header() after copying\nfrag descriptors, but that helper only carries over gso_{size,segs,\ntype} and never touches skb_shinfo()-\u0026gt;flags; skb_shift() moves frag\ndescriptors directly and leaves flags untouched.  As a result, the\ndestination skb keeps a reference to the same externally-owned or\npage-cache-backed pages while reporting skb_has_shared_frag() as\nfalse.\n\nThe mismatch is harmful in any in-place writer that uses\nskb_has_shared_frag() to decide whether shared pages must be detoured\nthrough skb_cow_data().  ESP input is one such writer (esp4.c,\nesp6.c), and a single nft \u0026apos;dup to \u0026lt;local\u0026gt;\u0026apos; rule -- or any other\nnf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()\u0026apos;d\nskb in esp_input() with the marker stripped, letting an unprivileged\nuser write into the page cache of a root-owned read-only file via\nauthencesn-ESN stray writes.\n\nSet SKBFL_SHARED_FRAG on the destination whenever frag descriptors\nwere actually moved from the source.  skb_copy() and skb_copy_expand()\nshare skb_copy_header() too but linearize all paged data into freshly\nallocated head storage and emerge with nr_frags == 0, so\nskb_has_shared_frag() returns false on its own; they need no change.\n\nThe same omission exists in skb_gro_receive() and skb_gro_receive_list().\nThe former moves the incoming skb\u0026apos;s frag descriptors into the\naccumulator\u0026apos;s last sub-skb via two paths (a direct frag-move loop and\nthe head_frag + memcpy path); the latter chains the incoming skb whole\nonto p\u0026apos;s frag_list.  Downstream skb_segment() reads only\nskb_shinfo(p)-\u0026gt;flags, and skb_segment_list() reuses each sub-skb\u0026apos;s\nshinfo as the nskb -- both p and lp must carry the marker.\n\nThe same omission also exists in tcp_clone_payload(), which builds an\nMTU probe skb by moving frag descriptors from skbs on sk_write_queue\ninto a freshly allocated nskb.  The helper falls into the same family\nand warrants the same fix for consistency; no TCP TX-side in-place\nwriter is currently known to reach a user page through this gap, but\na future consumer depending on the marker would regress silently.\n\nThe same omission exists in skb_segment(): the per-iteration flag\nmerge takes only head_skb\u0026apos;s flag, and the inner switch that rebinds\nfrag_skb to list_skb on head_skb-frags exhaustion does not fold the\nnew frag_skb\u0026apos;s flag into nskb.  Fold frag_skb\u0026apos;s flag at both sites\nso segments drawing frags from frag_list members carry the marker.(CVE-2026-43503)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb()\n\nAdd the same NULL guard already present in\nl2cap_sock_resume_cb() and l2cap_sock_ready_cb().(CVE-2026-45834)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix slab-use-after-free in qd_put\n\nCommit a475c5dd16e5 (\u0026quot;gfs2: Free quota data objects synchronously\u0026quot;)\nstarted freeing quota data objects during filesystem shutdown instead of\nputting them back onto the LRU list, but it failed to remove these\nobjects from the LRU list, causing LRU list corruption.  This caused\nuse-after-free when the shrinker (gfs2_qd_shrink_scan) tried to access\nalready-freed objects on the LRU list.\n\nFix this by removing qd objects from the LRU list before freeing them in\nqd_put().\n\nInitial fix from Deepanshu Kartikey \u0026lt;(CVE-2026-45861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix role switching during resume\n\nIf the role change while we are suspended, the cdns3 driver switches to the\nnew mode during resume. However, switching to host mode in this context\ncauses a NULL pointer dereference.\n\nThe host role\u0026apos;s start() operation registers a xhci-hcd device, but its\nprobe is deferred while we are in the resume path. The host role\u0026apos;s resume()\noperation assumes the xhci-hcd device is already probed, which is not the\ncase, leading to the dereference. Since the start() operation of the new\nrole is already called, the resume operation can be skipped.\n\nSo skip the resume operation for the new role if a role switch occurs\nduring resume. Once the resume sequence is complete, the xhci-hcd device\ncan be probed in case of host mode.\n\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000208\nMem abort info:\n...\nData abort info:\n...\n[0000000000000208] pgd=0000000000000000, p4d=0000000000000000\nInternal error: Oops: 0000000096000004 [#1]  SMP\nModules linked in:\nCPU: 0 UID: 0 PID: 146 Comm: sh Not tainted\n6.19.0-rc7-00013-g6e64f4aabfae-dirty #135 PREEMPT\nHardware name: Texas Instruments J7200 EVM (DT)\npstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : usb_hcd_is_primary_hcd+0x0/0x1c\nlr : cdns_host_resume+0x24/0x5c\n...\nCall trace:\n usb_hcd_is_primary_hcd+0x0/0x1c (P)\n cdns_resume+0x6c/0xbc\n cdns3_controller_resume.isra.0+0xe8/0x17c\n cdns3_plat_resume+0x18/0x24\n platform_pm_resume+0x2c/0x68\n dpm_run_callback+0x90/0x248\n device_resume+0x100/0x24c\n dpm_resume+0x190/0x2ec\n dpm_resume_end+0x18/0x34\n suspend_devices_and_enter+0x2b0/0xa44\n pm_suspend+0x16c/0x5fc\n state_store+0x80/0xec\n kobj_attr_store+0x18/0x2c\n sysfs_kf_write+0x7c/0x94\n kernfs_fop_write_iter+0x130/0x1dc\n vfs_write+0x240/0x370\n ksys_write+0x70/0x108\n __arm64_sys_write+0x1c/0x28\n invoke_syscall+0x48/0x10c\n el0_svc_common.constprop.0+0x40/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x34/0x108\n el0t_64_sync_handler+0xa0/0xe4\n el0t_64_sync+0x198/0x19c\nCode: 52800003 f9407ca5 d63f00a0 17ffffe4 (f9410401)\n---[ end trace 0000000000000000 ]---(CVE-2026-45911)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix inline data read failure for ztailpacking pclusters\n\nCompressed folios for ztailpacking pclusters must be valid before adding\nthese pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster()\nmay assume they are already valid and then trigger a NULL pointer\ndereference.\n\nIt is somewhat hard to reproduce because the inline data is in the same\nblock as the tail of the compressed indexes, which are usually read just\nbefore. However, it may still happen if a fatal signal arrives while\nread_mapping_folio() is running, as shown below:\n\n erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008\n\n ...\n\n pc : z_erofs_decompress_queue+0x4c8/0xa14\n lr : z_erofs_decompress_queue+0x160/0xa14\n sp : ffffffc08b3eb3a0\n x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000\n x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001\n x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700\n x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098\n x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004\n x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9\n x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000\n x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000000000003f\n x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020\n x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n  z_erofs_decompress_queue+0x4c8/0xa14\n  z_erofs_runqueue+0x908/0x97c\n  z_erofs_read_folio+0x128/0x228\n  filemap_read_folio+0x68/0x128\n  filemap_get_pages+0x44c/0x8b4\n  filemap_read+0x12c/0x5b8\n  generic_file_read_iter+0x4c/0x15c\n  do_iter_readv_writev+0x188/0x1e0\n  vfs_iter_read+0xac/0x1a4\n  backing_file_read_iter+0x170/0x34c\n  ovl_read_iter+0xf0/0x140\n  vfs_read+0x28c/0x344\n  ksys_read+0x80/0xf0\n  __arm64_sys_read+0x24/0x34\n  invoke_syscall+0x60/0x114\n  el0_svc_common+0x88/0xe4\n  do_el0_svc+0x24/0x30\n  el0_svc+0x40/0xa8\n  el0t_64_sync_handler+0x70/0xbc\n  el0t_64_sync+0x1bc/0x1c0\n\nFix this by reading the inline data before allocating and adding\nthe pclusters to the I/O chains.(CVE-2026-45943)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc()\n\nIn amdgpu_acpi_enumerate_xcc(), if amdgpu_acpi_dev_init() returns -ENOMEM,\nthe function returns directly without releasing the allocated xcc_info,\nresulting in a memory leak.\n\nFix this by ensuring that xcc_info is properly freed in the error paths.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-45947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fix memory leaks in gfs2_fill_super error path\n\nFix two memory leaks in the gfs2_fill_super() error handling path when\ntransitioning a filesystem to read-write mode fails.\n\nFirst leak: kthread objects (thread_struct, task_struct, etc.)\nWhen gfs2_freeze_lock_shared() fails after init_threads() succeeds, the\ncreated kernel threads (logd and quotad) are never destroyed. This\noccurs because the fail_per_node label doesn\u0026apos;t call\ngfs2_destroy_threads().\n\nSecond leak: quota bitmap buffer (8192 bytes)\nWhen gfs2_make_fs_rw() fails after gfs2_quota_init() succeeds but\nbefore other operations complete, the allocated quota bitmap is never\nfreed.\n\nThe fix moves thread cleanup to the fail_per_node label to handle all\nerror paths uniformly. gfs2_destroy_threads() is safe to call\nunconditionally as it checks for NULL pointers. Quota cleanup is added\nin gfs2_make_fs_rw() to properly handle the withdrawal case where\nquota initialization succeeds but the filesystem is then withdrawn.\n\nThread leak backtrace (gfs2_freeze_lock_shared failure):\n  unreferenced object 0xffff88801d7bca80 (size 4480):\n    copy_process+0x3a1/0x4670 kernel/fork.c:2422\n    kernel_clone+0xf3/0x6e0 kernel/fork.c:2779\n    kthread_create_on_node+0x100/0x150 kernel/kthread.c:478\n    init_threads+0xab/0x350 fs/gfs2/ops_fstype.c:611\n    gfs2_fill_super+0xe5c/0x1240 fs/gfs2/ops_fstype.c:1265\n\nQuota leak backtrace (gfs2_make_fs_rw failure):\n  unreferenced object 0xffff88812de7c000 (size 8192):\n    gfs2_quota_init+0xe5/0x820 fs/gfs2/quota.c:1409\n    gfs2_make_fs_rw+0x7a/0xe0 fs/gfs2/super.c:149\n    gfs2_fill_super+0xfbb/0x1240 fs/gfs2/ops_fstype.c:1275(CVE-2026-45961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch()\n\nCover a missed execution path with a new check.(CVE-2026-45982)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix unsigned underflow in z_erofs_lz4_handle_overlap()\n\nSome crafted images can have illegal (!partial_decoding \u0026amp;\u0026amp;\nm_llen \u0026lt; m_plen) extents, and the LZ4 inplace decompression path\ncan be wrongly hit, but it cannot handle (outpages \u0026lt; inpages)\nproperly: \u0026quot;outpages - inpages\u0026quot; wraps to a large value and\nthe subsequent rq-\u0026gt;out[] access reads past the decompressed_pages\narray.\n\nHowever, such crafted cases can correctly result in a corruption\nreport in the normal LZ4 non-inplace path.\n\nLet\u0026apos;s add an additional check to fix this for backporting.\n\nReproducible image (base64-encoded gzipped blob):\n\nH4sIAJGR12kCA+3SPUoDQRgG4MkmkkZk8QRbRFIIi9hbpEjrHQI5ghfwCN5BLCzTGtLbBI+g\ndilSJo1CnIm7GEXFxhT6PDDwfrs73/ywIQD/1ePD4r7Ou6ETsrq4mu7XcWfj++Pb58nJU/9i\nPNtbjhan04/9GtX4qVYc814WDqt6FaX5s+ZwXXeq52lndT6IuVvlblytLMvh4Gzwaf90nsvz\n2DF/21+20T/ldgp5s1jXRaN4t/8izsy/OUB6e/Qa79r+JwAAAAAAAL52vQVuGQAAAP6+my1w\nywAAAAAAAADwu14ATsEYtgBQAAA=\n\n$ mount -t erofs -o cache_strategy=disabled foo.erofs /mnt\n$ dd if=/mnt/data of=/dev/null bs=4096 count=1(CVE-2026-45999)\n\nIn the Linux kernel, the following vulnerability has been resolved:  ipmi:ssif: Clean up kthread on errors  If an error occurs after the ssif kthread is created, but before the main IPMI code starts the ssif interface, the ssif kthread will not be stopped.  So make sure the kthread is stopped on an error condition if it is running.  The Linux kernel CVE team has assigned CVE-2026-46044 to this issue.(CVE-2026-46044)\n\nIn the Linux kernel, the following vulnerability has been resolved:  md/raid5: fix soft lockup in retry_aligned_read()  When retry_aligned_read() encounters an overlapped stripe, it releases the stripe via raid5_release_stripe() which puts it on the lockless released_stripes llist. In the next raid5d loop iteration, release_stripe_list() drains the stripe onto handle_list (since STRIPE_HANDLE is set by the original IO), but retry_aligned_read() runs before handle_active_stripes() and removes the stripe from handle_list via find_get_stripe() -\u0026gt; list_del_init(). This prevents handle_stripe() from ever processing the stripe to resolve the overlap, causing an infinite loop and soft lockup.  Fix this by using __release_stripe() with temp_inactive_list instead of raid5_release_stripe() in the failure path, so the stripe does not go through the released_stripes llist. This allows raid5d to break out of its loop, and the overlap will be resolved when the stripe is eventually processed by handle_stripe().  The Linux kernel CVE team has assigned CVE-2026-46051 to this issue.(CVE-2026-46051)\n\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: nSVM: Raise #UD if unhandled VMMCALL isn\u0026apos;t intercepted by L1  Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1.  The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it\u0026apos;s not intercepted.  Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses.  The last remaining \u0026quot;single\u0026quot; stub will soon be dropped as well.  [sean: rewrite changelog and comment, tag for stable, remove defunct stubs]  The Linux kernel CVE team has assigned CVE-2026-46076 to this issue.(CVE-2026-46076)\n\nIn the Linux kernel, the following vulnerability has been resolved:  erofs: fix the out-of-bounds nameoff handling for trailing dirents  Currently we already have boundary-checks for nameoffs, but the trailing dirents are special since the namelens are calculated with strnlen() with unchecked nameoffs.  If a crafted EROFS has a trailing dirent with nameoff \u0026gt;= maxsize, maxsize - nameoff can underflow, causing strnlen() to read past the directory block.  nameoff0 should also be verified to be a multiple of `sizeof(struct erofs_dirent)` as well [1].  [1] https://sashiko.dev/#/patchset/20260416063511.3173774-1-hsiangkao%40linux.alibaba.com  The Linux kernel CVE team has assigned CVE-2026-46078 to this issue.(CVE-2026-46078)\n\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0  INVLPGA should cause a #UD when EFER.SVME is not set. Add a check to properly inject #UD when EFER.SVME=0.  [sean: tag for stable@]  The Linux kernel CVE team has assigned CVE-2026-46082 to this issue.(CVE-2026-46082)\n\nIn the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: take vmap_purge_lock in shrinker  decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan().  However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks.  Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users.  The Linux kernel CVE team has assigned CVE-2026-46093 to this issue.(CVE-2026-46093)\n\nIn the Linux kernel, the following vulnerability has been resolved:mm/damon/sysfs-schemes: protect memcg_path kfree() with damon_sysfs_lockPatch series \u0026quot;mm/damon/sysfs-schemes: fix use-after-free for [memcg_]path\u0026quot;.Reads of \u0026apos;memcg_path\u0026apos; and \u0026apos;path\u0026apos; files in DAMON sysfs interface could racewith their writes, results in use-after-free.  Fix those.This patch (of 2):damon_sysfs_scheme_filter-\u0026gt;mmecg_path can be read and written by users,via DAMON sysfs memcg_path file.  It can also be indirectly read, for theparameters {on,off}line committing to DAMON.  The reads for parameterscommitting are protected by damon_sysfs_lock to avoid the sysfs filesbeing destroyed while any of the parameters are being read.  But theuser-driven direct reads and writes are not protected by any lock, whilethe write is deallocating the memcg_path-pointing buffer.  As a result,the readers could read the already freed buffer (user-after-free).  Notethat the user-reads don\u0026apos;t race when the same open file is used by thewriter, due to kernfs\u0026apos;s open file locking.  Nonetheless, doing the readsand writes with separate open files would be common.  Fix it by protectingboth the user-direct reads and writes with damon_sysfs_lock.(CVE-2026-46121)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt\n\nhci_le_create_big_complete_evt() iterates over BT_BOUND connections for\na BIG handle using a while loop, accessing ev-\u0026gt;bis_handle[i++] on each\niteration.  However, there is no check that i stays within ev-\u0026gt;num_bis\nbefore the array access.\n\nWhen a controller sends a LE_Create_BIG_Complete event with fewer\nbis_handle entries than there are BT_BOUND connections for that BIG,\nor with num_bis=0, the loop reads beyond the valid bis_handle[] flex\narray into adjacent heap memory.  Since the out-of-bounds values\ntypically exceed HCI_CONN_HANDLE_MAX (0x0EFF), hci_conn_set_handle()\nrejects them and the connection remains in BT_BOUND state.  The same\nconnection is then found again by hci_conn_hash_lookup_big_state(),\ncreating an infinite loop with hci_dev_lock held.\n\nFix this by terminating the BIG if in case not all BIS could be setup\nproperly.(CVE-2026-46138)\n\nIn the Linux kernel, vports are used concurrently and protected by RCU, so netdev_put() must happen after the RCU grace period. The rtnl_delete_link() must happen under RTNL and cannot be executed in RCU context. Calling synchronize_net() while holding RTNL is not good for performance and system stability, so calling netdev_put() in RCU call is the right solution. However, when the device is deleted, rtnl_unlock() calls netdev_run_todo() and blocks until all references are gone. In the current code, this means that call_rcu() is never reached, the vport is never freed, and the reference is never released, causing a self-deadlock on device removal. The fix moves the rcu_call() before rtnl_unlock(), so the scheduled RCU callback will be executed when synchronize_net() is called from rtnl_unlock()-\u0026gt;netdev_run_todo() while RTNL itself is already released.(CVE-2026-46165)\n\nIn the Linux kernel\u0026apos;s RISC-V KVM subsystem, when the second kzalloc (host_context.vector.datap) fails in kvm_riscv_vcpu_alloc_vector_context, the first allocation (guest_context.vector.datap) is not freed, causing a memory leak. An attacker can trigger this via ioctl(vm_fd, KVM_CREATE_VCPU), potentially leading to resource exhaustion.(CVE-2026-46171)\n\nIn the Linux kernel, the mlx4_ib_create_srq() function fails to release resources allocated by mlx4_srq_alloc() in error handling paths, leading to a resource leak. An attacker could exploit this vulnerability to cause resource exhaustion or denial of service.(CVE-2026-46178)\n\nIn the Linux kernel, the spi_nor_params_show() function uses sizeof(snor_f_names) to calculate the array length. Since snor_f_names is an array of pointers, sizeof returns the total byte size of the pointer array (element_count  sizeof(void )), which on 64-bit systems is 8 times larger than intended. This causes an out-of-bounds read when a flag bit is set that exceeds the actual element count but falls within the inflated byte-size count. The fix replaces sizeof with ARRAY_SIZE to pass the actual number of elements.(CVE-2026-46190)","status":"published","published":"2026-06-05T11:11:31Z","modified":"2026-08-18T01:20:04.171596141Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-31689","title":"CVE-2026-31689 in linux - Patched by Root","description":"Root has patched CVE-2026-31689 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:17:09.812221638Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:32.037361Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-31689","title":"CVE-2026-31689 in linux - Patched by Root","description":"Root has patched CVE-2026-31689 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:38.644955163Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-06T16:59:13.904931Z"},{"id":"UBUNTU-CVE-2026-31689","description":"In the Linux kernel, the following vulnerability has been resolved: EDAC/mc: Fix error path ordering in edac_mc_alloc() When the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path will call put_device() which will end up calling the device's release function. However, the init ordering is wrong such that device_initialize() happens *after* the failed allocation and thus the device itself and the release function pointer are not initialized yet when they're called:   MCE: In-kernel MCE decoding enabled.   ------------[ cut here ]------------   kobject: '(null)': is not initialized, yet kobject_put() is being called.   WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd   CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)   RIP: 0010:kobject_put   Call Trace:    \u003cTASK\u003e    edac_mc_alloc+0xbe/0xe0 [edac_core]    amd64_edac_init+0x7a4/0xff0 [amd64_edac]    ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]    do_one_initcall    ... Reorder the calling sequence so that the device is initialized and thus the release function pointer is properly set before it can be used. This was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T18:16:00Z","modified":"2026-11-11T09:39:37.331532966Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-11T10:01:34.66199Z"},{"id":"AZL-84404","title":"CVE-2026-31689 affecting package kernel for versions less than 6.6.137.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T18:16:54Z","modified":"2026-08-28T17:56:49.125413Z","updated_at":"2026-11-02T15:28:10.335477Z"},{"id":"CVE-2026-31689","title":"EDAC/mc: Fix error path ordering in edac_mc_alloc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u003epvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device's release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they're called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: '(null)': is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u003cTASK\u003e\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.","status":"published","published":"2026-04-27T17:34:27.793Z","modified":"2026-10-28T02:30:36.825525996Z","updated_at":"2026-11-02T15:45:00.861953Z"},{"id":"MGASA-2026-0108","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.137 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-05-04T16:05:38Z","modified":"2026-05-04T16:17:57.935092Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0110","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.137 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-05-07T05:06:13Z","modified":"2026-05-07T05:15:09.702997Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"SUSE-SU-2026:24181-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-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23128: arm64: Set __nocfi on swsusp_arch_resume() (bsc#1258298).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31523: nvme-pci: ensure we're polling a polled queue (bsc#1263017).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64570: wifi: mac80211: fix fils_discovery double free on alloc failure (bsc#1274010).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68253: drm/i915/hdcp: check streams[] bounds before overflow (bsc#1275156).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a \"STACKTRACE\" histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- Also reflect disabled BATMAN in supported.conf Fixes: 4058797e93cc (\"Disable CONFIG_BATMAN_ADV (jsc#PED-16892)\").\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read \"ngpios\" as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random \"error beacon valid\" messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-12T15:51:36Z","modified":"2026-10-20T17:23:58.081294417Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24182-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 RT kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23128: arm64: Set __nocfi on swsusp_arch_resume() (bsc#1258298).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31523: nvme-pci: ensure we're polling a polled queue (bsc#1263017).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-63795: 9p: avoid putting oldfid in p9_client_walk() error path (bsc#1271955).\n- CVE-2026-68162: sctp: avoid auth_enable sysctl UAF during netns teardown (bsc#1274920).\n- CVE-2026-68445: drm/vc4: Prevent shader BO mappings from becoming writable (bsc#1276277).\n- CVE-2026-72084: scsi: target: Bound PR-OUT TransportID parsing to the received buffer (bsc#1275540).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64570: wifi: mac80211: fix fils_discovery double free on alloc failure (bsc#1274010).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68253: drm/i915/hdcp: check streams[] bounds before overflow (bsc#1275156).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a \"STACKTRACE\" histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read \"ngpios\" as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random \"error beacon valid\" messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-12T14:42:54Z","modified":"2026-10-20T17:23:58.082704471Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24315-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-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23128: arm64: Set __nocfi on swsusp_arch_resume() (bsc#1258298).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31523: nvme-pci: ensure we're polling a polled queue (bsc#1263017).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64570: wifi: mac80211: fix fils_discovery double free on alloc failure (bsc#1274010).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68253: drm/i915/hdcp: check streams[] bounds before overflow (bsc#1275156).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a \"STACKTRACE\" histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- Also reflect disabled BATMAN in supported.conf Fixes: 4058797e93cc (\"Disable CONFIG_BATMAN_ADV (jsc#PED-16892)\").\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read \"ngpios\" as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random \"error beacon valid\" messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-12T16:13:17Z","modified":"2026-10-27T17:23:13.4159637Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24316-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 RT kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23128: arm64: Set __nocfi on swsusp_arch_resume() (bsc#1258298).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31523: nvme-pci: ensure we're polling a polled queue (bsc#1263017).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued (bsc#1266008).\n- CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs (bsc#1269532).\n- CVE-2026-63795: 9p: avoid putting oldfid in p9_client_walk() error path (bsc#1271955).\n- CVE-2026-68162: sctp: avoid auth_enable sysctl UAF during netns teardown (bsc#1274920).\n- CVE-2026-68445: drm/vc4: Prevent shader BO mappings from becoming writable (bsc#1276277).\n- CVE-2026-72084: scsi: target: Bound PR-OUT TransportID parsing to the received buffer (bsc#1275540).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_conn: Fix null ptr deref in hci_abort_conn() (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64570: wifi: mac80211: fix fils_discovery double free on alloc failure (bsc#1274010).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68253: drm/i915/hdcp: check streams[] bounds before overflow (bsc#1275156).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a \"STACKTRACE\" histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read \"ngpios\" as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random \"error beacon valid\" messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-12T16:39:36Z","modified":"2026-10-27T17:23:13.475564625Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:4640-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 RT kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_sync: remove unnecessary hci_conn_get in create_conn_sync (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64473: vfio: Remove device debugfs before releasing devres (bsc#1273320).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68264: drm/xe/pt: Reset current_op in xe_pt_update_ops_init() (bsc#1275142).\n- CVE-2026-68266: drm/xe: Hold a dma-buf reference for imported BOs (bsc#1275137).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68382: drm/xe/guc: Hold device ref until queue teardown completes (bsc#1274824).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72018: dibs: loopback: validate offset and size in move_data() (bsc#1276852).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72070: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() (bsc#1277153).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72125: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER (bsc#1277535).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72147: dmaengine: dw-edma-pcie: Reject devices without driver data (bsc#1277234).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72491: net/9p: fix race condition on rdma-\u003estate in trans_rdma.c (bsc#1276947).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74440: drm/xe: Wait on external BO kernel fences in exec IOCTL (bsc#1261564).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74449: drm/amd/display: Fix divide-by-zero in calculate_mcache_setting on zero viewport (bsc#1278215).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74533: replace additional lock in hci_conn with a common spinlock (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74538: Bluetooth: ISO: lock sk in iso_connect_ind (bsc#1275682).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74551: hwmon: (nzxt-smart2) DMA-align output buffer (bsc#1275680).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80779: net/ionic: avoid OOB TX partner lookup for hwstamp RXQ (bsc#1279590).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80947: wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (bsc#1280239).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80979: net/smc: unregister the connection before draining the rx tasklet (bsc#1280299).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-80984: net/smc: do not dereference an unset send buffer on the SMC-D teardown path (bsc#1280309).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89453: iommu/amd: Put PCI device after handling PPR faults (bsc#1280384).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89780: net: qualcomm: rmnet: restore skb-\u003edev on deaggregated frames (bsc#1280969).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90047: drm/xe: Don't hand out the flat CCS storage as usable VRAM (bsc#1280927).\n- CVE-2026-90065: net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure (bsc#1281660).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90240: iommu/vt-d: Flush context cache with correct SID when tearing down aliases (bsc#1281683).\n- CVE-2026-90241: iommu/vt-d: Tear down scalable-mode context on probe failure (bsc#1281682).\n- CVE-2026-90243: iommu/vt-d: Clear Present bit before tearing down copied context entry (bsc#1281845).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90426: iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs (bsc#1282013).\n- CVE-2026-90428: iommu/tegra241-cmdqv: Don't run the error ISR before probe sets up vintfs (bsc#1282003).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97413: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write (bsc#1282975).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a 'STACKTRACE' histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97947: x86/amd_node: Fix potential NULL pointer dereference (bsc#1283130).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98030: net: dsa: bcm_sf2: bound the CFP rule dump by the caller's buffer size (bsc#1283489).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: core: Add scoped cleanup helper for card references (stable-fixes).\n- ALSA: core: Define auto-cleanup for snd_card_free() (stable-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add HDA_CODEC_QUIRK for Samsung 750XBE/730XBE (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Pavilion x360 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: ice1712: Fix the card leak at probe error with the auto-cleanup (git-fixes).\n- ALSA: ice1712: Fix the error handling via auto-cleanup at probe (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: ump: Copy FB name string more safely (stable-fixes).\n- ALSA: ump: Copy safe string name to rawmidi (stable-fixes).\n- ALSA: ump: Update rawmidi name per EP name update (stable-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: Propagate write errors in generic mixer put callbacks (stable-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- Also reflect disabled BATMAN in supported.conf Fixes: 4058797e93cc ('Disable CONFIG_BATMAN_ADV (jsc#PED-16892)').\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate device-supplied DMA indices (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_conn: fix CIS hold ownership on reuse (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: balance the parent hold in hci_bind_bis() (git-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: mgmt: fix race in read_unconf_index_list() (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: Bound SW TPA IDs to prevent crashes (git-fixes).\n- bnxt_en: Fix potential data corruption with HW GRO/LRO (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the 'newfangled' __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Bump frame warning limit for clang builds of dml (stable-fixes).\n- drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend (git-fixes).\n- drm/amd/display: Check for sharpening case when calculating max vtaps for scaler (stable-fixes).\n- drm/amd/display: clean-up dead code in dml2_mall_phantom (stable-fixes).\n- drm/amd/display: Find link encoder for flexible DIG mapping cases (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/display: Initialize dsc_caps to 0 (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: hide pp_table sysfs on APUs (git-fixes).\n- drm/amdgpu: add a helper to calculate ring distance (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: Failed to check various return code (stable-fixes).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: harden FRU PIA parsing with bounded helpers (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: Prefer ROM BAR for default VGA device (stable-fixes).\n- drm/amdgpu: Skip accessing psp rum time db for APUs (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdgpu: validate and share PSP fw_pri_buf copies via psp_copy_fw (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/dp: Add DSC virtual DPCD quirk for Realtek MST branch device (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915/psr: Add new SU area calculation helper to apply workarounds (stable-fixes).\n- drm/i915/psr: Clear stale sel fetch enable bits on sel fetch disable (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/imagination: clamp freelist reconstruction requests (git-fixes).\n- drm/imagination: Fix page count for page table for map() interface (git-fixes).\n- drm/imagination: Populate FW common context ID before passing to the FW (stable-fixes).\n- drm/imagination: Propagate map failures correctly from pvr_mmu_map_sgl() (git-fixes).\n- drm/logicvc: Drop the select of the nonexistent CONFIG_DRM_KMS_DMA_HELPER (git-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: dsi: Add compatible for mt8167-dsi (stable-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/bios: skip the IFR header if present (stable-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix UAF in nouveau_uvmm_sm when BO is in TTM_PL_SYSTEM (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: RCU-free the scheduler-containing nouveau_sched (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: Enable GPIOLIB for panels which uses functions from it (stable-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV (git-fixes).\n- drm/xe: Wait on external BO kernel fences in exec IOCTL (CVE-2026-74440 bsc#1261564).\n- drm: add drm_memory_stats_is_zero (stable-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- drm: rz-du: Ensure correct suspend/resume ordering with VSP (stable-fixes).\n- EDAC/amd64: Add support for AMD family 1Ah-based newer models (jsc#PED-16968).\n- EDAC/mc_sysfs: Increase legacy channel support to 16 (jsc#PED-16968).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbcon: don't suspend/resume when vc is graphics mode (stable-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- firmware: sysfb: Move bpp-depth calculation into screen_info helper (stable-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read 'ngpios' as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix '(null)' output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: atr: fix dangling adapter pointer on add failure (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: disable autosuspend on remove (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ibmveth: Add multi buffers rx replenishment hcall support (jsc#PED-16852).\n- ibmvnic: Fix hardcoded NUM_RX_STATS/NUM_TX_STATS with dynamic sizeof (jsc#PED-16854).\n- ibmvnic: Increase max subcrq indirect entries with fallback (jsc#PED-16854).\n- ibmvnic: Use ndo_get_stats64 to fix inaccurate SAR reporting (jsc#PED-16854).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX (git-fixes).\n- kernel-binary.spec.in: Fix syntax error.\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: s390: pci: Fix aisb calculation (bsc#1277451).\n- KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic (bsc#1277451).\n- KVM: s390: pci: Fix GISC refcount leak on AIF enable failure (bsc#1277451).\n- KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1277451).\n- KVM: s390: pci: Fix memory accounting for pinned/unpinned pages (bsc#1277451).\n- KVM: s390: pci: Fix missing error codes and memory unaccounting (bsc#1277451).\n- KVM: s390: pci: Fix NULL dereference on AIBV allocation failure (bsc#1277451).\n- KVM: s390: pci: Fix resource leak on IRQ registration failure (bsc#1277451).\n- KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1277451).\n- KVM: s390: pci: Validate AIBV and AISB before pinning guest pages (bsc#1277451).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net/ibmveth: fix comment typos in ibmveth.c (jsc#PED-16852).\n- net: ibmveth: added KUnit tests for some buffer pool functions (jsc#PED-16852).\n- net: ibmveth: Indented struct ibmveth_adapter correctly (jsc#PED-16852).\n- net: ibmveth: Refactored veth_pool_store for better maintainability (jsc#PED-16852).\n- net: ibmveth: Reset the adapter when unexpected states are detected (jsc#PED-16852).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: page_pool: Remove zone/policy GFP flags when allocating XArray entries (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: hp-bioscfg: bound ordered-list parsing by the package count (stable-fixes).\n- platform/x86: hp-bioscfg: pass validated element count to package parsers (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: sequencing: don't call .post_enable() if pwrseq_unit_enable() failed (git-fixes).\n- power: sequencing: fix NULL-pointer dereference in pwrseq_device_register() (git-fixes).\n- power: sequencing: fix NULL-pointer dereference in pwrseq_unit_new() (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/perf: Add power12 Base Performance Monitoring support (jsc#PED-16906).\n- powerpc/perf: Set cpumode flags using sample address (jsc#PED-16906).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Limit PVR list to 16 entries for CAS negotiation (jsc#PED-16906).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Add Power12 architected mode (jsc#PED-16906).\n- powerpc: Add Power12 raw mode (jsc#PED-16906).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/core: Fix potential use after free in counter_release() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_destroy_cq_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_destroy_srq_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_free_cq() (git-fixes).\n- RDMA/core: Fix use after free in ib_query_qp() (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Free RX data on late probe failure (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Preserve unit 0 on (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- RDMA/rvt: Return NULL after port allocation failure (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: intel: Move suspend tracking from trigger to pm suspend (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: davinci: Unset POWERDOWN bit when releasing resources (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thermal: gov_step_wise: Fix stale mitigation vote with non-zero lower bounds (git-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- USB: make to_usb_driver() use container_of_const() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: don't get the radio mask for netdev-less wdevs (git-fixes).\n- wifi: cfg80211: expose cfg80211_chandef_get_width() (stable-fixes).\n- wifi: cfg80211: fix width unit in cfg80211_radio_chandef_valid() (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: skip regulatory for punctured subchannels (stable-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: parse beacon notif per layout (stable-fixes).\n- wifi: iwlwifi: mvm: validate mac_link_id in session protect notif (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: abort chanswitch when leaving a mesh (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow injecting frames wider than the chanctx (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: explicitly disable FTM responder on AP stop (stable-fixes).\n- wifi: mac80211: ibss: wait for in-flight TX on disconnect (stable-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: mesh: reset the CSA state when leaving (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: add Netgear A8500 USB device ID (stable-fixes).\n- wifi: mt76: mt7925: handle 320MHz bandwidth in RXV and TXS (stable-fixes).\n- wifi: mt76: mt7925: populate EHT 320MHz MCS map in sta_rec (stable-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random 'error beacon valid' messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: cleanup unused rtwdev::roc_work (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mce: Add support for physical address valid bit (jsc#PED-16968).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951).\n- xfs: don't free cowblocks from under dirty pagecache on unshare (bsc#1278709).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-13T11:52:05Z","modified":"2026-10-14T11:15:08.088253504Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"SUSE-SU-2026:4706-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-2024-26730: hwmon: (nct6775) Fix access to temperature configuration registers (bsc#1222538).\n- CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's-\u003enocb_cb_kthread pointer (bsc#1254408).\n- CVE-2026-23352: x86/efi: defer freeing of boot services memory (bsc#1260474).\n- CVE-2026-31689: EDAC/mc: Fix error path ordering in edac_mc_alloc() (bsc#1263602).\n- CVE-2026-43409: kprobes: avoid crash when rmmod/insmod after ftrace killed (bsc#1264747).\n- CVE-2026-45836: Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndtimeo_cb() (bsc#1266410).\n- CVE-2026-45872: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (bsc#1266735).\n- CVE-2026-46044: ipmi:ssif: Clean up kthread on errors (bsc#1267464).\n- CVE-2026-46135: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1267373).\n- CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() (bsc#1267648).\n- CVE-2026-46196: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (bsc#1266848).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53384: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails (bsc#1271817).\n- CVE-2026-53400: i2c: core: fix adapter registration race (bsc#1271906).\n- CVE-2026-63883: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ (bsc#1272572).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63913: netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check\n  (bsc#1272890).\n- CVE-2026-63956: USB: serial: cypress_m8: fix memory corruption with small endpoint (bsc#1272473).\n- CVE-2026-63963: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers (bsc#1272471).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64009: xfrm: Check for underflow in xfrm_state_mtu (bsc#1273879).\n- CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device (bsc#1273750).\n- CVE-2026-64046: net: tls: prevent chain-after-chain in plain text SG (bsc#1273059).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64173: tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails (bsc#1272145).\n- CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path (bsc#1272215).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64213: hwmon: (lm90) Add lock protection to lm90_alert (bsc#1272793).\n- CVE-2026-64279: i2c: core: fix adapter deregistration race (bsc#1273953).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64297: module: decompress: check return value of module_extend_max_pages() (bsc#1273938).\n- CVE-2026-64299: tracing: Prevent out-of-bounds read in glob matching (bsc#1273976).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64372: cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (bsc#1273889).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64402: coresight: ultrasoc-smb: Fix OOB write in smb_sync_perf_buffer() (bsc#1273258).\n- CVE-2026-64405: Bluetooth: hci_sync: remove unnecessary hci_conn_get in create_conn_sync (bsc#1273512).\n- CVE-2026-64425: io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (bsc#1273522).\n- CVE-2026-64473: vfio: Remove device debugfs before releasing devres (bsc#1273320).\n- CVE-2026-64474: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc (bsc#1274316).\n- CVE-2026-64475: vfio/pci: Release the VGA arbiter client on register_device() failure (bsc#1274319).\n- CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device (bsc#1274245).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64528: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers (bsc#1272847).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64580: xfrm6: clear dst.dev on error to avoid double netdev_put in xfrm6_fill_dst() (bsc#1274037).\n- CVE-2026-64589: i2c: core: fix hang on adapter registration failure (bsc#1274494).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access (bsc#1274890).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68264: drm/xe/pt: Reset current_op in xe_pt_update_ops_init() (bsc#1275142).\n- CVE-2026-68266: drm/xe: Hold a dma-buf reference for imported BOs (bsc#1275137).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68290: rds: tcp: unregister sysctl before tearing down listen socket (bsc#1275977).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68376: sctp: fix auth_hmacs array size in struct sctp_cookie (bsc#1274836).\n- CVE-2026-68382: drm/xe/guc: Hold device ref until queue teardown completes (bsc#1274824).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68441: net/sched: Handle TC_ACT_REDIRECT from qdisc filter chains (bsc#1274776).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68451: s390/zcrypt: Validate length for CCA ECC private key requests (bsc#1276287).\n- CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests (bsc#1276295).\n- CVE-2026-68454: KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1276388).\n- CVE-2026-68471: wifi: ieee80211: validate MLE common info length (bsc#1276504).\n- CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets (bsc#1275495).\n- CVE-2026-72012: tracing/osnoise: Call synchronize_rcu() when unregistering (bsc#1276783).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72018: dibs: loopback: validate offset and size in move_data() (bsc#1276852).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72025: s390/monwriter: Reject buffer reuse with different data length (bsc#1276923).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction (bsc#1277148).\n- CVE-2026-72066: cpu: hotplug: Bound hotplug states sysfs output (bsc#1277149).\n- CVE-2026-72070: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() (bsc#1277153).\n- CVE-2026-72085: scsi: xen: scsiback: Free unsubmitted command instead of double-putting it (bsc#1275542).\n- CVE-2026-72086: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path (bsc#1277179).\n- CVE-2026-72098: dm-verity: fix buffer overflow in FEC calculation (bsc#1275543).\n- CVE-2026-72102: dm_early_create: fix freeing used table on dm_resume failure (bsc#1277314).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72125: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER (bsc#1277535).\n- CVE-2026-72129: nvmet-rdma: handle inline data with a nonzero offset (bsc#1275545).\n- CVE-2026-72130: nvmet: Introduce nvmet_req_transfer_len() (bsc#1275549).\n- CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72138: xen/gntdev: fix error handling in ioctl (bsc#1277235).\n- CVE-2026-72147: dmaengine: dw-edma-pcie: Reject devices without driver data (bsc#1277234).\n- CVE-2026-72157: net: thunderbolt: Fix frags[] overflow by bounding frame_count (bsc#1277544).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72166: net/9p: fix infinite loop in p9_client_rpc on fatal signal (bsc#1277556).\n- CVE-2026-72218: lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure (bsc#1277218).\n- CVE-2026-72219: lockd: Plug nlm_file leak when nlm_do_fopen() fails (bsc#1277217).\n- CVE-2026-72224: nvdimm/btt: Free arenas on btt_init() error paths (bsc#1277215).\n- CVE-2026-72237: perf/x86/amd/brs: Fix kernel address leakage (bsc#1277615).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup (bsc#1277662).\n- CVE-2026-72256: netfilter: xt_cluster: reject template conntracks in hash match (bsc#1277674).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72299: tipc: restrict socket queue dumps in enqueue tracepoints (bsc#1275924).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72321: ipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer() (bsc#1277143).\n- CVE-2026-72322: ipv6: mcast: Fix potential UAF in MLD delayed work (bsc#1275972).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72348: netfilter: ip6tables: mark malformed IPv6 extension headers for hotdrop (bsc#1276007).\n- CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt() (bsc#1277784).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72351: gue: validate REMCSUM private option length (bsc#1276009).\n- CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check (bsc#1277823).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq() (bsc#1277857).\n- CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump (bsc#1277128).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72404: tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() (bsc#1278031).\n- CVE-2026-72406: net: sungem: fix probe error cleanup (bsc#1278035).\n- CVE-2026-72413: sctp: fix err_chunk memory leaks in INIT handling (bsc#1277122).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72433: netfilter: nft_meta_bridge: fix NFT_META_BRI_IIFPVID stack leak (bsc#1278053).\n- CVE-2026-72434: netfilter: ipset: make sure gc is properly stopped (bsc#1278054).\n- CVE-2026-72435: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() (bsc#1278056).\n- CVE-2026-72436: netfilter: ipset: Fix data race between add and dump in all hash types (bsc#1277245).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72444: flow_dissector: check device type before reading ETH_ADDRS (bsc#1278100).\n- CVE-2026-72447: sctp: hold socket lock when dumping endpoints in sctp_diag (bsc#1277109).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72449: drm/amdkfd: fix list_del corruption in kfd_criu_resume_svm (bsc#1278108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72491: net/9p: fix race condition on rdma-\u003estate in trans_rdma.c (bsc#1276947).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74256: bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check (bsc#1276535).\n- CVE-2026-74257: sockmap: Fix use-after-free in udp_bpf_recvmsg() (bsc#1276532).\n- CVE-2026-74258: bpf: Guard __get_user acesss with access_ok for uprobe_multi data (bsc#1276538).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74267: net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen\n  (bsc#1276519).\n- CVE-2026-74268: tcp: clear sock_ops cb flags before force-closing a child socket (bsc#1276508).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74278: ALSA: seq: Fix kernel heap address leak in bounce_error_event() (bsc#1278132).\n- CVE-2026-74281: tipc: reject inverted service ranges from peer bindings (bsc#1276474).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74283: tipc: require net admin for TIPCv2 netlink mutators (bsc#1276475).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74288: net: fib_rules: Don't dump dying fib_rule in fib_rules_dump() (bsc#1276460).\n- CVE-2026-74289: ipv4: fib: Don't dump dying fib_info in fib_leaf_notify() (bsc#1276461).\n- CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers (bsc#1276462).\n- CVE-2026-74302: Bluetooth: hci_core: Fix UAF in hci_unregister_dev() (bsc#1276445).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74310: vhost/net: complete zerocopy ubufs only once (bsc#1276891).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74330: configfs: fix lockless traversals of -\u003es_children (bsc#1277129).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74356: vhost: move smp_rmb() into vhost_get_avail_idx() (bsc#1278063).\n- CVE-2026-74359: configfs_lookup(): don't leave -\u003es_dentry dangling on failure (bsc#1278067).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74365: kabi: nvdimm/btt: handling (bsc#1278225).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard (bsc#1277401).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74384: nvme-multipath: fix flex array size in struct nvme_ns_head (bsc#1277405).\n- CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock (bsc#1278255).\n- CVE-2026-74386: nvmet-tcp: fix page fragment cache leak in error path (bsc#1277098).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure (bsc#1278087).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74391: tracing: Bound synthetic-field strings with seq_buf (bsc#1278091).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74398: ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD (bsc#1277410).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74440: drm/xe: Wait on external BO kernel fences in exec IOCTL (bsc#1261564).\n- CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer (bsc#1278210).\n- CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division (bsc#1278211).\n- CVE-2026-74449: drm/amd/display: Fix divide-by-zero in calculate_mcache_setting on zero viewport (bsc#1278215).\n- CVE-2026-74450: drm/amd/pm: fix pptable use-after-free (bsc#1278216).\n- CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job (bsc#1278178).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74465: net: openvswitch: fix potential UAF on meter attach failure (bsc#1277801).\n- CVE-2026-74467: s390/qeth: Check CAP_NET_ADMIN for private ioctls (bsc#1277805).\n- CVE-2026-74469: sctp: prevent peer transport count overflow (bsc#1277792).\n- CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() (bsc#1277781).\n- CVE-2026-74473: vxlan: use pskb_network_may_pull() in route_shortcircuit() (bsc#1276340).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74480: net: bridge: stop fast-leave after deleting a port group (bsc#1276353).\n- CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter (bsc#1277892).\n- CVE-2026-74487: binfmt_misc: restore write access when removing an entry (bsc#1276349).\n- CVE-2026-74490: tipc: avoid use-after-free in poll trace queue dumps (bsc#1276352).\n- CVE-2026-74492: netfilter: ipset: do not update comments from kernel-side hash adds (bsc#1276337).\n- CVE-2026-74493: net/smc: fix socket use-after-free during link group termination (bsc#1276338).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74515: KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1275953).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74533: replace additional lock in hci_conn with a common spinlock (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74538: Bluetooth: ISO: lock sk in iso_connect_ind (bsc#1275682).\n- CVE-2026-74540: Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp (bsc#1275681).\n- CVE-2026-74541: Bluetooth: ISO: clear iso_data always when detaching conn from hcon (bsc#1275694).\n- CVE-2026-74551: hwmon: (nzxt-smart2) DMA-align output buffer (bsc#1275680).\n- CVE-2026-74553: hwmon: (nct6775-core) Fix number of temperature registers for NCT6116 (bsc#1275684).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74564: netfilter: xt_hashlimit: validate hashtable supports XT_HASHLIMIT_RATE_MATCH (bsc#1275567).\n- CVE-2026-74579: netfilter: nft_payload: fix mask build for partial field offload (bsc#1275559).\n- CVE-2026-74580: vhost: reset the vring metadata cache on vring reconfiguration (bsc#1277885).\n- CVE-2026-74586: sctp: clear new_transport when removing a peer (bsc#1277820).\n- CVE-2026-74588: sctp: keep chunk-\u003etransport in step with the list it is queued on (bsc#1277766).\n- CVE-2026-74589: bpf, sockmap: Fix sk_redir use-after-free in send verdict (bsc#1277904).\n- CVE-2026-74592: ima: Instantiate file_truncate and path_truncate hooks (bsc#1277900).\n- CVE-2026-74594: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (bsc#1277843).\n- CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (bsc#1277910).\n- CVE-2026-74597: ip6_tunnel: clear skb2-\u003ecb in ip6ip6_err() (bsc#1277493).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74600: mm/page_table_check: skip special zero mappings (bsc#1277640).\n- CVE-2026-74601: ring-buffer: Use current_context for safe per-CPU buffer swap (bsc#1277896).\n- CVE-2026-74603: ptp: ocp: Fix board ID over-read (bsc#1277915).\n- CVE-2026-74608: smb: client: Fix use-after-free in cifs_try_adding_channels() (bsc#1277796).\n- CVE-2026-74609: tipc: read le-\u003elink under the node lock in tipc_node_link_down() (bsc#1277906).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74625: netfilter: bridge: release template ct on non-IP path (bsc#1277036).\n- CVE-2026-74630: ipv6: prevent in6_dev_get() from resurrecting inet6_dev (bsc#1278191).\n- CVE-2026-74631: net: smc: fix splice entry lifetime imbalance in smc_rx_splice (bsc#1278195).\n- CVE-2026-74632: mm/huge_memory: fix huge_zero_pfn race (bsc#1278199).\n- CVE-2026-74636: tracing: Fix race between update_event_fields and, event_define_fields (bsc#1277371).\n- CVE-2026-74637: perf: Fix dangling cgroup pointer in cpuctx (bsc#1277372).\n- CVE-2026-74638: drm/v3d: Serialize the scheduler timeout handlers (bsc#1277374).\n- CVE-2026-74659: net: bridge: mrp: fix uninitialised bytes on the wire (bsc#1277296).\n- CVE-2026-74660: netfilter: ebt_nflog: pin the NFLOG backend (bsc#1277272).\n- CVE-2026-74663: net/sched: reject overly deep qdisc hierarchies (bsc#1278311).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74666: packet: synchronize pressure clearing with ring reconfiguration (bsc#1277032).\n- CVE-2026-74667: net/packet: reset the MAC header on the packet-socket transmit path (bsc#1277396).\n- CVE-2026-74671: ima: fix out-of-bounds read in xattr_verify() (bsc#1277392).\n- CVE-2026-74688: sctp: clear control chunk transport if it is being removed (bsc#1277489).\n- CVE-2026-74689: net/atm: fix slab-out-of-bounds read in vcc_setsockopt() (bsc#1278314).\n- CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration (bsc#1276930).\n- CVE-2026-74697: bnxt_en: Do not set EOP on RX AGG BDs on 5760X chips (bsc#1277897).\n- CVE-2026-74700: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (bsc#1277626).\n- CVE-2026-74701: net/openvswitch: check Ethernet header length in key_extract() (bsc#1276921).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74710: xsk: require at least 16 bytes of TX metadata (bsc#1276579).\n- CVE-2026-74713: vhost_iotlb: bound map allocation in add_range (bsc#1276570).\n- CVE-2026-74718: devlink: fix net namespace reference leak in reload (bsc#1276573).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal (bsc#1276563).\n- CVE-2026-74726: bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor (bsc#1276565).\n- CVE-2026-74735: l2tp: fix tunnel and session refcount leak on seq_file release (bsc#1277030).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74739: net/sched: cls_u32: skip hash tables in u32_bind_class() (bsc#1278247).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-74752: sctp: validate cookie AUTH state before use (bsc#1278315).\n- CVE-2026-80540: drm/amdgpu: Fix UVD decode image min size calculation (bsc#1277590).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80580: fbdev: bound mode sysfs output to the sysfs buffer (bsc#1278294).\n- CVE-2026-80585: mptcp: fastopen: only mark MPTFO subflows with SYN data (bsc#1277342).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80613: veth: fix NAPI leak in XDP enable error path (bsc#1278205).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80631: btrfs: lzo: reject compressed segment that overflows the compressed input (bsc#1277558).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80663: tools/power/x86/intel-speed-select: Harden daemon pidfile open (bsc#1278335).\n- CVE-2026-80664: netfilter: xt_nat: reject unsupported target families (bsc#1277555).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80679: s390/dasd: Fix potential NULL pointer dereference (bsc#1277557).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80686: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE (bsc#1278245).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80715: igc: remove napi_synchronize() in igc_down() (bsc#1277840).\n- CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink (bsc#1277837).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).\n- CVE-2026-80725: net: gro: properly validate BIG TCP aggregation criteria (bsc#1277452).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length (bsc#1279536).\n- CVE-2026-80756: selinux: do not cancel a policy conversion that never started (bsc#1278708).\n- CVE-2026-80779: net/ionic: avoid OOB TX partner lookup for hwstamp RXQ (bsc#1279590).\n- CVE-2026-80785: fbdev: serialize mode sysfs access with lock_fb_info() (bsc#1279619).\n- CVE-2026-80789: nvmet-tcp: bound SGL data length before allocating command buffers (bsc#1279621).\n- CVE-2026-80793: ipv4: reject undersized MTUs in ip_do_fragment() (bsc#1279799).\n- CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (bsc#1279811).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80836: crypto: virtio - bound the akcipher result length (bsc#1279819).\n- CVE-2026-80840: ipv6: seg6: clear IPv4 control block on IPIP decapsulation (bsc#1279875).\n- CVE-2026-80841: net/packet: defer vmalloc TX_RING free until skbs finish (bsc#1279835).\n- CVE-2026-80842: net: bridge: mcast: fix use-after-free of a master VLAN's multicast context (bsc#1279888).\n- CVE-2026-80844: xfrm: ah6: validate routing header segments_left (bsc#1279786).\n- CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device (bsc#1279878).\n- CVE-2026-80847: tcp: clamp route advmss to TCP_MIN_MSS (bsc#1279850).\n- CVE-2026-80848: xfrm: espintcp: fix UAF during close (bsc#1279581).\n- CVE-2026-80852: tls: device: fix out-of-bounds write in tls_append_frag() (bsc#1279532).\n- CVE-2026-80863: RDMA/rxe: Fix OOB in free_rd_atomic_resources() (bsc#1279535).\n- CVE-2026-80864: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp (bsc#1279525).\n- CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms (bsc#1279527).\n- CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr (bsc#1279497).\n- CVE-2026-80909: drm/amdgpu: Reject UVD message with invalid number of h265 refs (bsc#1279422).\n- CVE-2026-80932: vsock/virtio: flush works in dependency order (bsc#1280143).\n- CVE-2026-80947: wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (bsc#1280239).\n- CVE-2026-80976: seg6: reset IP6CB after IPv6 decapsulation (bsc#1280298).\n- CVE-2026-80979: net/smc: unregister the connection before draining the rx tasklet (bsc#1280299).\n- CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns() (bsc#1280296).\n- CVE-2026-80984: net/smc: do not dereference an unset send buffer on the SMC-D teardown path (bsc#1280309).\n- CVE-2026-81000: net: tun: bound receive headroom (bsc#1280263).\n- CVE-2026-81001: slip: fix use-after-free in sl_sync() (bsc#1280375).\n- CVE-2026-89448: iommu/vt-d: Force requesting ACS when tboot is enabled (bsc#1280379).\n- CVE-2026-89451: iommu/sva: Set handle-\u003edev before the SVA handle is visible (bsc#1280383).\n- CVE-2026-89453: iommu/amd: Put PCI device after handling PPR faults (bsc#1280384).\n- CVE-2026-89477: sctp: fix NULL deref on untransmitted RECONF completion (bsc#1280338).\n- CVE-2026-89479: sctp: stop processing a packet once its association is deleted (bsc#1280786).\n- CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes (bsc#1280449).\n- CVE-2026-89481: nvme-tcp: fix host memory disclosure on R2T for a read command (bsc#1280451).\n- CVE-2026-89482: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone (bsc#1280350).\n- CVE-2026-89485: lockd: pin next file across nlm_inspect_file lock-drop (bsc#1280456).\n- CVE-2026-89508: RDMA/ucma: Lock the handler in ucma_set_ib_path() (bsc#1280544).\n- CVE-2026-89510: RDMA/cxgb4: Cancel reg_work before freeing device on remove (bsc#1280551).\n- CVE-2026-89511: qede: Fix NULL pointer dereference in TPA fragment processing (bsc#1280508).\n- CVE-2026-89525: udf: reject VAT indexes equal to the entry count (bsc#1282288).\n- CVE-2026-89531: svcrdma: Reject connection when transport allocation fails (bsc#1281738).\n- CVE-2026-89532: svcrdma: Fix pcl_for_each_segment for empty chunks (bsc#1280985).\n- CVE-2026-89533: svcrdma: Fix offset arithmetic in read_chunk_range (bsc#1280993).\n- CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback (bsc#1280711).\n- CVE-2026-89538: SUNRPC: Reject krb5 v2 wrap tokens with oversized ec field (bsc#1280716).\n- CVE-2026-89539: SUNRPC: reject duplicate CREDS_VALUE options (bsc#1280717).\n- CVE-2026-89540: sunrpc: init gssp_lock before publishing proc entry (bsc#1280719).\n- CVE-2026-89541: SUNRPC: harden gss_unwrap_resp_priv length checks (bsc#1280388).\n- CVE-2026-89542: SUNRPC: harden gss_krb5_unwrap_v2 against short tokens (bsc#1280387).\n- CVE-2026-89544: SUNRPC: fix gssx_dec_option_array error path bugs (bsc#1280758).\n- CVE-2026-89547: SUNRPC: Check svc pool percpu counter allocation (bsc#1280548).\n- CVE-2026-89548: SUNRPC: always drain cache_cleaner before destroying a cache_detail (bsc#1280546).\n- CVE-2026-89550: SUNRPC: svcauth_gss: enforce krb5 token minimum length (bsc#1280726).\n- CVE-2026-89551: SUNRPC: xdr_buf_trim: clamp buf-\u003elen to avoid underflow (bsc#1280727).\n- CVE-2026-89564: ip: orphan prefetched skbs before multicast forwarding (bsc#1280797).\n- CVE-2026-89569: Bluetooth: RFCOMM: serialize security confirmation handling (bsc#1280733).\n- CVE-2026-89580: bpf: Disable preemption in __bpf_get_stack (bsc#1280577).\n- CVE-2026-89603: entry: Fix seccomp bypass after ptrace with TSYNC (bsc#1280923).\n- CVE-2026-89609: ecryptfs: hold msg ctx list lock when cleaning daemon queue (bsc#1281793).\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-89644: btrfs: fix extent map leak in NOCOW direct I/O write (bsc#1281054).\n- CVE-2026-89662: NFSD: Prevent lock owner use-after-free during client teardown (bsc#1280509).\n- CVE-2026-89663: nfsd: revoke copy-notify stateids before dropping their reference (bsc#1280518).\n- CVE-2026-89665: nfsd: reject out-of-range useconds in NFSv2 SETATTR/CREATE (bsc#1281057).\n- CVE-2026-89671: nfsd: gate nfs3 setacl by argp-\u003emask (bsc#1280252).\n- CVE-2026-89672: nfsd: gate nfs2 setacl by argp-\u003emask (bsc#1280235).\n- CVE-2026-89673: nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo (bsc#1280237).\n- CVE-2026-89674: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget (bsc#1280243).\n- CVE-2026-89680: nfsd: fix nfsd_file leak on inter-server COPY setup failure (bsc#1280206).\n- CVE-2026-89684: nfsd: fix cpntf publish race in nfs4_init_cp_state (bsc#1280178).\n- CVE-2026-89686: nfsd: fix BUG_ON in nfsd4_alloc_layout_stateid on racing delegation revoke (bsc#1280184).\n- CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid (bsc#1280151).\n- CVE-2026-89696: nfsd: block non-SAVEFH ops after FOREIGN PUTFH to prevent NULL deref (bsc#1280146).\n- CVE-2026-89697: nfsd: add fh_want_write() for early-verified SETATTR in nfsd_proc_setattr() (bsc#1280148).\n- CVE-2026-89699: nfsd: validate symlink target length in NFSv4 CREATE (bsc#1281077).\n- CVE-2026-89702: nfsd: size fh_verify server sockaddr slot by xpt_locallen (bsc#1280487).\n- CVE-2026-89704: nfsd: sample writeback error cursor before async COPY loop (bsc#1280490).\n- CVE-2026-89707: nfsd: release path refs on follow_down() error (bsc#1280468).\n- CVE-2026-89710: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path (bsc#1280455).\n- CVE-2026-89712: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock (bsc#1280870).\n- CVE-2026-89713: NFSD: check truncate permission under inode lock (bsc#1280872).\n- CVE-2026-89780: net: qualcomm: rmnet: restore skb-\u003edev on deaggregated frames (bsc#1280969).\n- CVE-2026-89784: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 (bsc#1281224).\n- CVE-2026-89789: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free (bsc#1281226).\n- CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit (bsc#1281383).\n- CVE-2026-89912: KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save (bsc#1281201).\n- CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables (bsc#1281202).\n- CVE-2026-89929: KVM: nVMX: Decouple INVVPID operand checks from flushing of vpid02 (bsc#1281358).\n- CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (bsc#1281359).\n- CVE-2026-89931: KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (bsc#1281427).\n- CVE-2026-89968: nvmet-tcp: reject unsolicited H2CData PDUs (bsc#1281229).\n- CVE-2026-89970: nvmet-auth: Synchronize timeout work during SQ teardown (bsc#1281231).\n- CVE-2026-89984: perf/x86/intel: Fix kernel address leakages in LBR stack (bsc#1281273).\n- CVE-2026-90003: futex: Prevent rcuwait use-after-free during requeue PI (bsc#1281295).\n- CVE-2026-90047: drm/xe: Don't hand out the flat CCS storage as usable VRAM (bsc#1280927).\n- CVE-2026-90065: net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure (bsc#1281660).\n- CVE-2026-90074: net/sched: fq_pie: clamp default quantum to avoid signed overflow (bsc#1281496).\n- CVE-2026-90088: Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (bsc#1281397).\n- CVE-2026-90097: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition (bsc#1281514).\n- CVE-2026-90104: NFSv4.1: zero referring call lists before decoding (bsc#1281546).\n- CVE-2026-90149: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers (bsc#1281955).\n- CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure (bsc#1281599).\n- CVE-2026-90182: blk-iocost: clear delay state when freeing policy data (bsc#1281644).\n- CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data (bsc#1281964).\n- CVE-2026-90198: ALSA: core: Fix use-after-free in snd_card_do_free() (bsc#1281818).\n- CVE-2026-90203: Squashfs: check block offset is not negative (bsc#1281808).\n- CVE-2026-90218: RDMA/cma: Fix WARNING in res_to_rt (bsc#1281795).\n- CVE-2026-90228: nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() (bsc#1281717).\n- CVE-2026-90240: iommu/vt-d: Flush context cache with correct SID when tearing down aliases (bsc#1281683).\n- CVE-2026-90241: iommu/vt-d: Tear down scalable-mode context on probe failure (bsc#1281682).\n- CVE-2026-90243: iommu/vt-d: Clear Present bit before tearing down copied context entry (bsc#1281845).\n- CVE-2026-90255: Bluetooth: hci_conn: fix the SCO setup context lifetime (bsc#1281694).\n- CVE-2026-90259: btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data() (bsc#1281680).\n- CVE-2026-90263: btrfs: check if root is readonly when setting posix acl (bsc#1281922).\n- CVE-2026-90265: btrfs: defrag: fix deadlock between defrag and delalloc space reservation (bsc#1282054).\n- CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept() (bsc#1281777).\n- CVE-2026-90293: IB/isert: post the full-feature receive buffers after session registration (bsc#1281778).\n- CVE-2026-90294: IB/isert: delay the final Login Response until the session is registered (bsc#1281732).\n- CVE-2026-90307: RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ (bsc#1282050).\n- CVE-2026-90308: RDMA/erdma: Hold QP references for AE and CM processing (bsc#1281786).\n- CVE-2026-90309: RDMA/erdma: Hold CQ references when processing EQ events (bsc#1281789).\n- CVE-2026-90358: bpf, x86: Fix trampoline stack size for 128-bit arguments (bsc#1281825).\n- CVE-2026-90388: iommu/dma: Check atomic pool allocation result directly (bsc#1282197).\n- CVE-2026-90413: IB/isert: reject login PDUs declaring more data than was received (bsc#1282113).\n- CVE-2026-90414: IB/isert: reject PDUs declaring more data than (bsc#1282110).\n- CVE-2026-90415: RDMA/cxgb4: free STAG index when TPT entry write fails (bsc#1282143).\n- CVE-2026-90417: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() (bsc#1281973).\n- CVE-2026-90426: iommu/tegra241-cmdqv: Free the error IRQ before tearing down VINTFs (bsc#1282013).\n- CVE-2026-90428: iommu/tegra241-cmdqv: Don't run the error ISR before probe sets up vintfs (bsc#1282003).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-92495: RDMA/bnxt_re: Clear VM_MAYWRITE on DBR/toggle page mmap (bsc#1282072).\n- CVE-2026-92500: ext4: use fsdata to track inline data write state and fix race (bsc#1282193).\n- CVE-2026-92503: ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() (bsc#1282383).\n- CVE-2026-92507: RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (bsc#1281988).\n- CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq() (bsc#1282034).\n- CVE-2026-92509: RDMA/core: Fix potential use after free in counter_release() (bsc#1282040).\n- CVE-2026-92510: RDMA/core: Fix potential use after free in ib_destroy_srq_user() (bsc#1282041).\n- CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user() (bsc#1282042).\n- CVE-2026-92512: RDMA/core: Fix use after free in ib_query_qp() (bsc#1281995).\n- CVE-2026-92514: RDMA/erdma: Fix CEQ tasklet use-after-free on removal (bsc#1281997).\n- CVE-2026-92523: RDMA/nldev: validate dynamic counter attribute length (bsc#1282271).\n- CVE-2026-92525: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[] (bsc#1282270).\n- CVE-2026-93037: RDMA/hfi1: Propagate sdma_txinit_ahg() errors (bsc#1282020).\n- CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure (bsc#1282170).\n- CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on (bsc#1282286).\n- CVE-2026-93104: RDMA/rvt: Return NULL after port allocation failure (bsc#1282284).\n- CVE-2026-93107: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state (bsc#1281399).\n- CVE-2026-93108: RDMA/ipoib: Drain RCU callbacks during module teardown (bsc#1281408).\n- CVE-2026-93109: RDMA/mlx5: Drain RCU callbacks during module teardown (bsc#1281379).\n- CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core (bsc#1281387).\n- CVE-2026-93154: RDMA/irdma: Add refcounting to user ring MRs (bsc#1282104).\n- CVE-2026-93207: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry (bsc#1282672).\n- CVE-2026-93212: nfsd: guard nfsd_serv deref in nfsd_file_net_dispose (bsc#1282774).\n- CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation (bsc#1282812).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93782: vhost-scsi: flush backend after device ioctls (bsc#1282906).\n- CVE-2026-93794: smb/client: flush dirty data before punching a hole (bsc#1283154).\n- CVE-2026-93810: cachefiles: Fix double fput (bsc#1283213).\n- CVE-2026-93813: btrfs: tree-checker: validate INODE_REF's namelen (bsc#1282767).\n- CVE-2026-93826: HID: hidpp: fix potential UAF in hidpp_connect_event() (bsc#1282891).\n- CVE-2026-93829: smb: client: fix races in cifsd thread creation (bsc#1282803).\n- CVE-2026-97413: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write (bsc#1282975).\n- CVE-2026-97421: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (bsc#1283176).\n- CVE-2026-97477: RDMA/counter: Fix num_counters leak on bind_qp failure in alloc_and_bind() (bsc#1283230).\n- CVE-2026-97505: PCI/sysfs: Add CAP_SYS_ADMIN check to __resource_resize_store() (bsc#1283500).\n- CVE-2026-97557: smb: client: avoid leaking refcount in cifs_queue_oplock_break() (bsc#1283201).\n- CVE-2026-97934: tracing: Fix memory corruption from a 'STACKTRACE' histogram key (bsc#1282997).\n- CVE-2026-97940: ipv6: fix fib6 walker UAF on seq stop (bsc#1283163).\n- CVE-2026-97947: x86/amd_node: Fix potential NULL pointer dereference (bsc#1283130).\n- CVE-2026-97950: configfs: pin the symlink target's dirent instead of chasing -\u003eci_dentry (bsc#1283121).\n- CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume (bsc#1283312).\n- CVE-2026-98030: net: dsa: bcm_sf2: bound the CFP rule dump by the caller's buffer size (bsc#1283489).\n- CVE-2026-98080: btrfs: do not force reloc root creation during qgroup_account_snapshot() (bsc#1283973).\n- CVE-2026-98091: btrfs: detach failed sprout device from transaction update list (bsc#1283805).\n- CVE-2026-98164: KVM: x86/mmu: Check write tracking in all address spaces (bsc#1283935).\n- CVE-2026-100075: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters (bsc#1282881).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- ACPI: PCI: Clear _DEP dependencies after PCI root bridge attach (stable-fixes).\n- ACPICA: add boundary checks in acpi_ps_get_next_field() (stable-fixes).\n- ACPICA: add boundary checks in two places (stable-fixes).\n- ACPICA: Add package limit checks in parser functions (stable-fixes).\n- ACPICA: Add validation for node in acpi_ns_build_normalized_path() (stable-fixes).\n- ACPICA: Enhance buffer validation in acpi_ut_walk_aml_resources() (stable-fixes).\n- ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() (stable-fixes).\n- ACPICA: Fix condition check in acpi_ps_parse_loop() (stable-fixes).\n- ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op) (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ns_custom_package() (stable-fixes).\n- ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (stable-fixes).\n- ACPICA: Improve argument parsing in acpi_ps_get_next_simple_arg() (stable-fixes).\n- ACPICA: Prevent adding invalid references (stable-fixes).\n- ACPICA: validate byte_count in acpi_ps_get_next_package_length() (stable-fixes).\n- ACPICA: validate handler object type in two places (stable-fixes).\n- ALSA: 6fire: Clean ups with guard() (stable-fixes).\n- ALSA: 6fire: fix OOB write from device-reported iso length (git-fixes).\n- ALSA: aloop: Check card index validity at probe (stable-fixes).\n- ALSA: bcd2000: Fix race between rawmidi and disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: caiaq: unregister the input device when probe fails (git-fixes).\n- ALSA: core: Add scoped cleanup helper for card references (stable-fixes).\n- ALSA: core: Define auto-cleanup for snd_card_free() (stable-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: es18xx: check control allocation before private data setup (stable-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/common: Use cleanup macros for PM controls (stable-fixes).\n- ALSA: hda/common: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/conexant: Add pin config quirk for Lenovo IdeaPad Slim 5 16AKP10 (stable-fixes).\n- ALSA: hda/core: Use guard() for mutex locks (stable-fixes).\n- ALSA: hda/realtek: Add HDA_CODEC_QUIRK for Samsung 750XBE/730XBE (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Laptop 14s-dr1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS VivoBook X509DAP (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP 255 15.6 inch G9 Notebook PC (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP EliteBook 830 G8 (8AB8) to enable mute LEDs (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Pavilion x360 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Xiaoxin 14 GT (stable-fixes).\n- ALSA: hda/realtek: Fix speakers on MECHREVO WUJIE Series (stable-fixes).\n- ALSA: hda/tegra: Re-enable SDO workaround for Tegra194 (git-fixes).\n- ALSA: hda: Introduce auto cleanup macros for PM (stable-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hda: trace PCM open only after assigning a stream (git-fixes).\n- ALSA: ice1712: Fix the card leak at probe error with the auto-cleanup (git-fixes).\n- ALSA: ice1712: Fix the error handling via auto-cleanup at probe (git-fixes).\n- ALSA: line6: reject oversized playback packets (git-fixes).\n- ALSA: mpu401: Check card index validity at probe (stable-fixes).\n- ALSA: mts64: Check card index validity at probe (stable-fixes).\n- ALSA: pcm: Fix race between non-atomic ops and trigger-start (stable-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer (git-fixes).\n- ALSA: portman2x4: Check card index validity at probe (stable-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: seq: oss: Reject reads that cannot fit the next event (stable-fixes).\n- ALSA: seq: Serialize compat port-info ioctls (git-fixes).\n- ALSA: serial-u16550: Check card index validity at probe (stable-fixes).\n- ALSA: ua101: reject mismatched capture/playback packet sizes (git-fixes).\n- ALSA: ump: Copy FB name string more safely (stable-fixes).\n- ALSA: ump: Copy safe string name to rawmidi (stable-fixes).\n- ALSA: ump: Update rawmidi name per EP name update (stable-fixes).\n- ALSA: usb-audio: Add dB map quirk for Razer Barracuda X 2.4 (stable-fixes).\n- ALSA: usb-audio: Add FIXED_RATE quirk for JBL Quantum650 Wireless (stable-fixes).\n- ALSA: usb-audio: Add quirk flags for SC13A (stable-fixes).\n- ALSA: usb-audio: Add quirk for Corsair Virtuoso (later revision) (stable-fixes).\n- ALSA: usb-audio: Add quirk for Novation Mininova (stable-fixes).\n- ALSA: usb-audio: Add quirk for YAMAHA CDS3000 (stable-fixes).\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- ALSA: usb-audio: caiaq: validate EP1 reply lengths (stable-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: Propagate write errors in generic mixer put callbacks (stable-fixes).\n- ALSA: usb: 6fire: Avoid embedded URBs (stable-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usx2y: Drain pending US-428 pipe-4 output commands (stable-fixes).\n- ALSA: virmidi: Check card index validity at probe (stable-fixes).\n- ALSA: virtio: reset device before deleting virtqueues (git-fixes).\n- Also reflect disabled BATMAN in supported.conf Fixes: 4058797e93cc ('Disable CONFIG_BATMAN_ADV (jsc#PED-16892)').\n- arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc (git-fixes).\n- arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation (git-fixes).\n- arm64: percpu: Fix LSE operations on {8,16}-bit types (git-fixes).\n- arm64: percpu: Fix this_cpu_and() mask generation (git-fixes).\n- arm64: percpu: Fix this_cpu_write() casting (git-fixes).\n- arm64: Use load LSE atomics for the non-return per-CPU atomic operations (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add Alienware m15 R7 AMD to DMIC quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Victus Laptop 16-e1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HyperX OMEN Gaming Laptop 16-ap1xxx (stable-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: max98363: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: pcm3168a: Drop CONFIG_PM-conditional preproc directive (stable-fixes).\n- ASoC: codecs: rk3328: Use managed GPIO and clock helpers (stable-fixes).\n- ASoC: codecs: rt274: Fix format setting for 44100 rate (git-fixes).\n- ASoC: codecs: rt286: Revert delay value for jack setup (git-fixes).\n- ASoC: codecs: rt712-sdca-dmic: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config-\u003etype (git-fixes).\n- ASoC: hdmi-codec: Report a change when the channel status moves (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- ASoC: Intel: catpt: Complete coredump handling (stable-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: qcom: lpass-cpu: use DAI table index for playback constraints (git-fixes).\n- ASoC: qcom: q6apm: return error code to consumers on failures (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt (stable-fixes).\n- ASoC: rockchip: rockchip_pdm: Reorder clock enable sequence (stable-fixes).\n- ASoC: rockchip: spdif: Restore regcache cache-only mode on sync failure (stable-fixes).\n- ASoC: rt5645: Perform the initial jack detect at probe (stable-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tegra: Fix ASRC Stream6 input threshold control (git-fixes).\n- ASoC: ti: omap3pandora: update board check to use DT compatible (stable-fixes).\n- ASoC: ux500: Correct MSP frame and bit clock setup (git-fixes).\n- ASoC: ux500: Fix MSP stream lifecycle handling (git-fixes).\n- ASoC: ux500: Parenthesize MSP_{RX,TX}_CLKPOL_BIT() arguments (git-fixes).\n- ASoC: ux500: Program the MSP FIFO watermarks (git-fixes).\n- ASoC: ux500: Propagate MSP setup errors (git-fixes).\n- ASoC: ux500: Request the MSP MMIO resource (git-fixes).\n- ASoC: ux500: Validate MSP DAI configuration (git-fixes).\n- ASoC: wm8903: Move the DRC QR threshold to the register that holds it (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough (git-fixes).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Export few static functions (stable-fixes).\n- Bluetooth: btintel: Fix compiler warning for multi_v7_defconfig config (git-fixes).\n- Bluetooth: btintel: Print firmware SHA1 (stable-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate device-supplied DMA indices (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access (git-fixes).\n- Bluetooth: btmtksdio: Fix PM runtime reference leak in shutdown (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU (stable-fixes).\n- Bluetooth: btusb: Add Mercusys MA530 for Realtek RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add support for TP-Link TL-UB250 (stable-fixes).\n- Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV (stable-fixes).\n- Bluetooth: btusb: fix NXP IW610 composite device handling (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: btusb: QCA: Fix populating devcoredump fields on unenabled devices (git-fixes).\n- Bluetooth: btusb: Record matched usb_device_id into btusb_data (stable-fixes).\n- Bluetooth: btusb: refactor endpoint lookup (stable-fixes).\n- Bluetooth: coredump: Quiesce dump work on unregister (git-fixes).\n- Bluetooth: eir: validate service data length before reading UUID (git-fixes).\n- Bluetooth: hci_codec: validate vendor codec count length (git-fixes).\n- Bluetooth: hci_conn: fix CIS hold ownership on reuse (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sock: reject out-of-range OCF values (git-fixes).\n- Bluetooth: hci_sock: validate event length before filtering (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: Serialize local codec list cleanup (git-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: ISO: balance the parent hold in hci_bind_bis() (git-fixes).\n- Bluetooth: ISO: Fix parent socket leak in iso_conn_ready() (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: L2CAP: validate connectionless PSM length (stable-fixes).\n- Bluetooth: L2CAP: validate frame length before control and FCS access (git-fixes).\n- Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel (git-fixes).\n- Bluetooth: mgmt: fix race in read_unconf_index_list() (git-fixes).\n- Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup (git-fixes).\n- Bluetooth: RFCOMM: fix NULL dereference of dlc-\u003esession in RFCOMM_CONNINFO (git-fixes).\n- Bluetooth: RFCOMM: Reject short EA=0 frames in rfcomm_recv_frame() (git-fixes).\n- Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame (stable-fixes).\n- Bluetooth: SMP: reject Security Request over BR/EDR (git-fixes).\n- bnxt_en: Bound SW TPA IDs to prevent crashes (git-fixes).\n- bnxt_en: Fix potential data corruption with HW GRO/LRO (git-fixes).\n- bnxt_en: use irq_update_affinity_hint() (bsc#1280750).\n- bonding: crypto offload enabled, non-offload slave failover, rekey failed (bsc#1282823).\n- bus: fsl-mc: wait for the MC firmware to complete its boot (stable-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- char/nvram: Remove redundant nvram_mutex (stable-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- default_gfp(): avoid using the 'newfangled' __VA_OPT__ trick (bsc#1280139).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dmaengine: dw-axi-dmac: fix PM for system sleep and channel alloc (stable-fixes).\n- dmaengine: Fix device kref underflow in dma_chan_put() (git-fixes).\n- dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() (git-fixes).\n- dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() (git-fixes).\n- dmaengine: sprd: Fix runtime PM reference leak in probe (git-fixes).\n- dmaengine: sun6i: fix non-atomic read of DMA position registers (git-fixes).\n- dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status (git-fixes).\n- dmaengine: ti: k3-udma-glue: fix NULL dereference in k3_udma_glue_release_rx_chn() (git-fixes).\n- dmaengine: wait for RCU readers before releasing dma_device (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor chain after cyclic DMA (git-fixes).\n- dmaengine: xilinx_dma: Fix hardware buffer descriptor reuse order (git-fixes).\n- driver core: Better advertise dev_err_probe() (stable-fixes).\n- driver core: Make dev_err_probe() silent for -ENOMEM (stable-fixes).\n- drm/amd/display: Bump frame warning limit for clang builds of dml (stable-fixes).\n- drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend (git-fixes).\n- drm/amd/display: Check for sharpening case when calculating max vtaps for scaler (stable-fixes).\n- drm/amd/display: clean-up dead code in dml2_mall_phantom (stable-fixes).\n- drm/amd/display: Find link encoder for flexible DIG mapping cases (stable-fixes).\n- drm/amd/display: Fix CRC open failure during active rendering (stable-fixes).\n- drm/amd/display: Fix dc stream excess put in dm_update_crtc_state() (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix DPMS using partially updated pipe context (stable-fixes).\n- drm/amd/display: Initialize dsc_caps to 0 (stable-fixes).\n- drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC (git-fixes).\n- drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits from power states (stable-fixes).\n- drm/amd/pm/si: Fix updating clock limits on AC/DC (git-fixes).\n- drm/amd/pm: bound pp_dpm_set_pp_table() memcpy (stable-fixes).\n- drm/amd/pm: Check SMUv13.0.6/12 metrics integrity (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: hide pp_table sysfs on APUs (git-fixes).\n- drm/amdgpu: add a helper to calculate ring distance (stable-fixes).\n- drm/amdgpu: check ras and obj before dereference (git-fixes).\n- drm/amdgpu: check thunderbolt before switcheroo registration (stable-fixes).\n- drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages (bsc#1284146).\n- drm/amdgpu: Failed to check various return code (stable-fixes).\n- drm/amdgpu: fix ACP MFD device leak on init failure (git-fixes).\n- drm/amdgpu: fix buffer overflow during vBIOS update (stable-fixes).\n- drm/amdgpu: fix IP instance memory leak on kobject add failure (git-fixes).\n- drm/amdgpu: Fix last_update fence leak in amdgpu_vm_init() (git-fixes).\n- drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show() (git-fixes).\n- drm/amdgpu: Fix vmid_wait fence leak in amdgpu_ring_init() (git-fixes).\n- drm/amdgpu: flush pending RCU callbacks on module unload (stable-fixes).\n- drm/amdgpu: harden FRU PIA parsing with bounded helpers (stable-fixes).\n- drm/amdgpu: increase hmm range get pages timeout (stable-fixes).\n- drm/amdgpu: make an improvement on amdgpu_hmm_range_get_pages (stable-fixes).\n- drm/amdgpu: Prefer ROM BAR for default VGA device (stable-fixes).\n- drm/amdgpu: Skip accessing psp rum time db for APUs (stable-fixes).\n- drm/amdgpu: use AMDGPU_GPU_PAGE_SHIFT instead of PAGE_SHIFT (stable-fixes).\n- drm/amdgpu: Use system unbound workqueue for soft IH ring (stable-fixes).\n- drm/amdgpu: validate and share PSP fw_pri_buf copies via psp_copy_fw (stable-fixes).\n- drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id (stable-fixes).\n- drm/amdkfd: Check bounds on allocate_doorbell (stable-fixes).\n- drm/amdkfd: check find_first_zero_bit before __set_bit on kfd-\u003edoorbell_bitmap (stable-fixes).\n- drm/amdkfd: fix UAF race in destroy_queue_cpsch (stable-fixes).\n- drm/amdkfd: Let driver decide buffer size at AMDKFD_IOC_GET_DMABUF_INFO ioctl (stable-fixes).\n- drm/amdkfd: Reject zero-sized AQL queue allocations after size halving (stable-fixes).\n- drm/amdkfd: Remove arbitrary timeout for hmm_range_fault (stable-fixes).\n- drm/amdkfd: Unwind debug trap enable on copy_to_user failure (stable-fixes).\n- drm/arm/komeda: fix error handling for clk_prepare_enable() and callers (stable-fixes).\n- drm/arm/malidp: use clk_bulk API in runtime PM resume and suspend (stable-fixes).\n- drm/ast: Automatically clean up poll helper (stable-fixes).\n- drm/bridge: samsung-dsim: fix TE GPIO lifetime for host attach (git-fixes).\n- drm/bridge: tc358768: Set pre_enable_prev_first for reverse order (stable-fixes).\n- drm/cirrus: Use video aperture helpers (stable-fixes).\n- drm/dp: Add DSC virtual DPCD quirk for Realtek MST branch device (stable-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gem: Consider GEM object reclaimable if shrinking fails (stable-fixes).\n- drm/gma500: return errors from Oaktrail HDMI I2C reads (stable-fixes).\n- drm/gud: Add RCade Display Adapter VID/PID pair (stable-fixes).\n- drm/gud: fix out-of-bounds write in gud_plane_atomic_check() (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/i915/psr: Add new SU area calculation helper to apply workarounds (stable-fixes).\n- drm/i915/psr: Clear stale sel fetch enable bits on sel fetch disable (git-fixes).\n- drm/i915: fix incorrect RCU teardown order (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/i915: Guard against NULL driver_data in i915_pci_probe() (stable-fixes).\n- drm/imagination: clamp freelist reconstruction requests (git-fixes).\n- drm/imagination: Fix page count for page table for map() interface (git-fixes).\n- drm/imagination: Populate FW common context ID before passing to the FW (stable-fixes).\n- drm/imagination: Propagate map failures correctly from pvr_mmu_map_sgl() (git-fixes).\n- drm/logicvc: Drop the select of the nonexistent CONFIG_DRM_KMS_DMA_HELPER (git-fixes).\n- drm/mediatek: Add missing IS_ERR check for ovl_adaptor platform device (git-fixes).\n- drm/mediatek: dsi: Add compatible for mt8167-dsi (stable-fixes).\n- drm/mediatek: Fix ovl adaptor platform device leak (git-fixes).\n- drm/mediatek: Fix pdev reference leak in mtk_drm_bind() (git-fixes).\n- drm/msm/adreno: fix autosuspend cleanup during teardown (git-fixes).\n- drm/msm/dsi: round the byte clock rate after reparenting to the PHY PLL (git-fixes).\n- drm/msm/hdmi_phy: fix runtime PM cleanup on probe failure (git-fixes).\n- drm/nouveau/bios: skip the IFR header if present (stable-fixes).\n- drm/nouveau/clk: don't clobber reclock status when restoring volt/fan (git-fixes).\n- drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update (git-fixes).\n- drm/nouveau/disp: don't reject HDMI config on cards without SCDC (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix UAF in nouveau_uvmm_sm when BO is in TTM_PL_SYSTEM (git-fixes).\n- drm/nouveau: don't bump pin count on failed re-pin in nouveau_bo_pin_locked() (git-fixes).\n- drm/nouveau: fix autosuspend cleanup during teardown (git-fixes).\n- drm/nouveau: Fix bridge reference leak in nv1a_ram_new() (git-fixes).\n- drm/nouveau: fix double-free in nvif_vmm_dtor (git-fixes).\n- drm/nouveau: Fix gem reference leak in validate_init() (git-fixes).\n- drm/nouveau: Fix runtime PM leak in nouveau_connector_detect() (git-fixes).\n- drm/nouveau: RCU-free the scheduler-containing nouveau_sched (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/omap: dsi: Do not copy isr table (git-fixes).\n- drm/panel: Enable GPIOLIB for panels which uses functions from it (stable-fixes).\n- drm/panel: jadard-jd9365da-h3: set prepare_prev_first (stable-fixes).\n- drm/panel: simple: Add AM-1280800W8TZQW-T00H (stable-fixes).\n- drm/radeon: Read the VRAM VBIOS signature with readb() (git-fixes).\n- drm/vc4: Use managed KMS polling to fix UAF on unbind (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/virtio: fix memory leak of fence event on execbuffer failure (git-fixes).\n- drm/virtio: fix NULL pointer dereference on fence allocation failure (git-fixes).\n- drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl() (git-fixes).\n- drm/virtio: fix object leak when drm_gem_handle_create() fails (git-fixes).\n- drm/virtio: fix object leaks in virtio_gpu_resource_create_blob_ioctl() (git-fixes).\n- drm/virtio: release the GEM object on virtio_gpu_vram_create() errors (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV (git-fixes).\n- drm/xe: Wait on external BO kernel fences in exec IOCTL (CVE-2026-74440 bsc#1261564).\n- drm: add drm_memory_stats_is_zero (stable-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr (git-fixes).\n- drm: rz-du: Ensure correct suspend/resume ordering with VSP (stable-fixes).\n- EDAC/amd64: Add support for AMD family 1Ah-based newer models (jsc#PED-16968).\n- EDAC/mc_sysfs: Increase legacy channel support to 16 (jsc#PED-16968).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- fbcon: don't suspend/resume when vc is graphics mode (stable-fixes).\n- fbdev: pm2fb: unwind WC setup on probe failure (stable-fixes).\n- fbdev: pvr2fb: correct user pointer annotation and sentinel initializer (stable-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Validate BASE_ERROR_EVENT payload size (stable-fixes).\n- firmware: arm_scmi: Validate SENSOR_UPDATE payload size (stable-fixes).\n- firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS (git-fixes).\n- firmware: stratix10-svc: change get provision data to async SMC call (stable-fixes).\n- firmware: stratix10-svc: fix FCS SMC call kernel-doc (git-fixes).\n- firmware: sysfb: Move bpp-depth calculation into screen_info helper (stable-fixes).\n- gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out() (git-fixes).\n- gpio: dwapb: Mask interrupts at hardware initialization (stable-fixes).\n- gpio: pisosr: Read 'ngpios' as u32 (stable-fixes).\n- gpio: zynq: fix runtime PM leak on request error path (git-fixes).\n- HID: alps: fix use-after-free on input2 registration failure (git-fixes).\n- HID: amd_sfh: Validate PCI BAR size before mapping (git-fixes).\n- HID: core: quiesce input in hid_hw_stop() to prevent use-after-free (stable-fixes).\n- HID: elecom: fix bus type for M-XGL20DLBK (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: i2c-hid: Fix '(null)' output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: Fold i2c_hid_execute_reset() into i2c_hid_hwreset() (stable-fixes).\n- HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the report-descriptor (stable-fixes).\n- HID: i2c-hid: Revert to await reset ACK before reading report descriptor (git-fixes).\n- HID: i2c-hid: Split i2c_hid_hwreset() in start() and finish() functions (stable-fixes).\n- HID: i2c-hid: Switch i2c_hid_parse() to goto style error handling (stable-fixes).\n- HID: logitech-hidpp: fix race condition when accessing stale stack pointer (stable-fixes).\n- HID: mcp2221: stop device IO before hid_hw_stop (git-fixes).\n- HID: pidff: Support device error response from PID_BLOCK_LOAD (stable-fixes).\n- HID: quirks: add ALWAYS_POLL quirk for SDINNOVATION gaming keyboard (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- host1x: bus: Fix missing ops null check in error teardown (stable-fixes).\n- hwmon: (adt7462) Add of_match_table to support devicetree (stable-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (emc1403) Add support for EMC1428 and EMC1438 (stable-fixes).\n- hwmon: (emc1403) Add support for EMC1442 (stable-fixes).\n- hwmon: (emc1403) Convert to with_info API (stable-fixes).\n- hwmon: (emc1403) Drop hysteresis for low limit temperature (git-fixes).\n- hwmon: (emc1403) Rely on subsystem locking (stable-fixes).\n- hwmon: (emc1403) Support 11 bit accuracy (stable-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficients for LM5064/5066/5066i (stable-fixes).\n- hwmon: (pmbus/tps53679) Fix TPS53676 phase page decoding (git-fixes).\n- hwmon: (pmbus/tps53679) Select page 0 for single-page TPS53676 (git-fixes).\n- hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove (git-fixes).\n- hwmon: (w83793) release probe data through kref (git-fixes).\n- i2c: at91: release DMA channels on remove and probe error (git-fixes).\n- i2c: atr: fix dangling adapter pointer on add failure (git-fixes).\n- i2c: core: fix adapter registration race (git-fixes).\n- i2c: core: fix irq domain leak on adapter registration failure (git-fixes).\n- i2c: imx: disable autosuspend on remove (git-fixes).\n- i2c: imx: release DMA channels on probe error (git-fixes).\n- i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes (stable-fixes).\n- i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions \u003c 1.1 (git-fixes).\n- i3c: mipi-i3c-hci: Switch PIO data allocation to devm_kzalloc() (stable-fixes).\n- i3c: mipi-i3c-hci: Tolerate i3c_master_add_i3c_dev_locked() failures in DAA (stable-fixes).\n- ibmveth: Add multi buffers rx replenishment hcall support (jsc#PED-16852).\n- ibmvnic: Fix hardcoded NUM_RX_STATS/NUM_TX_STATS with dynamic sizeof (jsc#PED-16854).\n- ibmvnic: Increase max subcrq indirect entries with fallback (jsc#PED-16854).\n- ibmvnic: Use ndo_get_stats64 to fix inaccurate SAR reporting (jsc#PED-16854).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: kionix-kx022a: Fix array boundary check (git-fixes).\n- iio: accel: kxcjk-1013: reject duplicate event disable (git-fixes).\n- iio: accel: mma8452: switch to non-devm request_threaded_irq() (stable-fixes).\n- iio: accel: sca3000: fix frequency divider condition check (git-fixes).\n- iio: adc: max1363: sign-extend bipolar differential channel reads (git-fixes).\n- iio: adc: qcom-spmi-iadc: balance enable_irq_wake() on driver unbind (stable-fixes).\n- iio: adc: stm32-adc: fix check on internal channel availability (git-fixes).\n- iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure (git-fixes).\n- iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls (git-fixes).\n- iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind (git-fixes).\n- iio: buffer: Ensure bounce buffer used for unaligned case is zeroed (git-fixes).\n- iio: buffer: serialize buffer teardown with mode claims (git-fixes).\n- iio: frequency: admv1013: fix wrong channel field used in admv1013_read_raw() (git-fixes).\n- iio: gyro: adis16136: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16400: fix unprotected debugfs reads (git-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: gp2ap020a00f: drain irq_work after free_irq (git-fixes).\n- iio: light: stk3310: Deal with the ps interrupt issue in PM (stable-fixes).\n- iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup (git-fixes).\n- iio: proximity: isl29501: Fix return type of isl29501_register_write (git-fixes).\n- iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure (git-fixes).\n- iio: proximity: sx9324: Correct proximity channel resolution (git-fixes).\n- iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler (git-fixes).\n- iio: trigger: cancel reenable_work before freeing trigger (git-fixes).\n- inode: make __iget() a static inline (bsc#1282383).\n- Input: adp5588-keys - cache GPIO state before registering the gpiochip (git-fixes).\n- Input: aiptek - validate raw macro indices before updating state (stable-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Redmi Book Pro 16 2026 (git-fixes).\n- Input: cyttsp5 - clamp the HID report size before memcpy (git-fixes).\n- Input: eeti_ts - publish the OF module alias (git-fixes).\n- Input: evdev - zero absinfo before partial copy in EVIOCSABS (git-fixes).\n- Input: i8042 - add quirk for Acer Aspire Go 15 AG15-42P (stable-fixes).\n- Input: rmi_smbus - fix out-of-bounds read in rmi_smb_write_block() (git-fixes).\n- Input: s6sy761 - fix resume ordering and restore sensing (git-fixes).\n- Input: soc_button_array - check btns_desc-\u003epackage.count (git-fixes).\n- Input: soc_button_array - fix MS Surface Pro 11 probe failure (git-fixes).\n- Input: synaptics - disable InterTouch on ThinkPad T440p (board id 2722) (stable-fixes).\n- Input: synaptics - limit T440p InterTouch quirk to LEN0036 (git-fixes).\n- Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound (git-fixes).\n- Input: trackpoint - fix the inertia attribute name in the ABI document (git-fixes).\n- Input: xpad - add support for Azeron devices (stable-fixes).\n- Input: xpad - add support for Victrix Pro BFG Controller (stable-fixes).\n- Input: xpad - fix PDP Marvel Xbox 360 controller (git-fixes).\n- Input: zero ff_effect before compat copy in input_ff_effect_from_user (git-fixes).\n- integrity: Check for NULL returned by asymmetric_key_public_key (stable-fixes).\n- iommu/s390: Fix NULL dereference in iova_to_phys() with ZPCI_TABLE_TYPE_RFX (git-fixes).\n- kernel-binary.spec.in: Fix syntax error.\n- KEYS: encrypted: fix integer overflow of datablob_len (git-fixes).\n- keys: fix lost wakeup when reaping a dead key type (git-fixes).\n- KEYS: trusted: Fix tpm2_load_cmd() boundary check (git-fixes).\n- KVM: arm64: vgic: Don't leak the SPI array when init is retried (git-fixes).\n- KVM: arm64: vgic: Free gic_kvm_info on initialization failure (git-fixes).\n- KVM: nVMX: Always flush vpid02 on first use (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: s390: pci: Fix aisb calculation (bsc#1277451).\n- KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic (bsc#1277451).\n- KVM: s390: pci: Fix GISC refcount leak on AIF enable failure (bsc#1277451).\n- KVM: s390: pci: Fix handling of AIF enable without AISB (bsc#1277451).\n- KVM: s390: pci: Fix memory accounting for pinned/unpinned pages (bsc#1277451).\n- KVM: s390: pci: Fix missing error codes and memory unaccounting (bsc#1277451).\n- KVM: s390: pci: Fix NULL dereference on AIBV allocation failure (bsc#1277451).\n- KVM: s390: pci: Fix resource leak on IRQ registration failure (bsc#1277451).\n- KVM: s390: pci: Reject adapter interrupt forwarding if already enabled (bsc#1277451).\n- KVM: s390: pci: Validate AIBV and AISB before pinning guest pages (bsc#1277451).\n- KVM: VMX: Prioritize DR7.GD=1 #DB over CPL\u003e0 #GP on Intel (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- KVM: x86: Manually check DR4/5 write values to fix SVM intercept priority (git-fixes).\n- KVM: x86: Prioritize #UD on MOV DR over #GP due to non-zero CPL (git-fixes).\n- KVM: x86: Prioritize DR7.GD #DB over #GP due to illegal DR6/7 value (git-fixes).\n- KVM: x86: Treat any non-zero return from set_dr() as a faulting condition (git-fixes).\n- leds: pca9532: Don't stop blinking for non-zero brightness (stable-fixes).\n- leds: uleds: Return -EFAULT on copy_to_user() failure (stable-fixes).\n- media: dm1105: fix missing error check for dma_alloc_coherent (stable-fixes).\n- media: em28xx-video: fix missing res_free() on init_usb_xfer failure (stable-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: imon: Add iMON VFD HID OEM v1.2 key mappings (stable-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: rc: mceusb: Add support for 04eb:e033 (stable-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: video-i2c: fix buffer queue ordering (stable-fixes).\n- media: video-i2c: use vb2_video_unregister_device on driver removal (stable-fixes).\n- memstick: ms_block: destroy io_queue workqueue on removal (git-fixes).\n- mfd: db8500-prcmu: Remove needless return in three void APIs (stable-fixes).\n- mfd: rsmu: Add 8a34002 support (stable-fixes).\n- mmc: core: Add validation for host-provided max_segs (stable-fixes).\n- mmc: core: Cancel SDIO IRQ work before freeing host (git-fixes).\n- mmc: core: Fix OF node reference leak on card add failure (git-fixes).\n- mmc: davinci: avoid NULL deref of host-\u003edata in IRQ handler (stable-fixes).\n- mmc: davinci: fix mmc_add_host order in probe (stable-fixes).\n- mmc: hsq: Fix use-after-free in retry work (git-fixes).\n- mmc: mxcmmc: cancel data work and watchdog on remove (git-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2E SoC (stable-fixes).\n- mmc: renesas_sdhi: Add OF entry for RZ/G2N SoC (stable-fixes).\n- mmc: rtsx_pci_sdmmc: ignore broken write-protect on ThinkPad X260 (stable-fixes).\n- mmc: sdhci-of-aspeed: Remove children before releasing SDC resources (git-fixes).\n- mmc: sdhci_am654: Reset command and data lines on failed tuning (git-fixes).\n- mmc: sdio_uart: fix xmit_fifo leak when the port table is full (git-fixes).\n- mmc: sh_mmcif: initialize IRQ-thread mutex before requesting interrupt (git-fixes).\n- mmc: spi: reset bytes_xfered before retrying CRC failures (git-fixes).\n- mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ (git-fixes).\n- mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB (git-fixes).\n- mtd: spinand: fix zero oobavail when no ECC engine is used (git-fixes).\n- net/ibmveth: fix comment typos in ibmveth.c (jsc#PED-16852).\n- net: ibmveth: added KUnit tests for some buffer pool functions (jsc#PED-16852).\n- net: ibmveth: Indented struct ibmveth_adapter correctly (jsc#PED-16852).\n- net: ibmveth: Refactored veth_pool_store for better maintainability (jsc#PED-16852).\n- net: ibmveth: Reset the adapter when unexpected states are detected (jsc#PED-16852).\n- net: mana: Clear RDMA teardown and suspend state in mana_rdma_probe() (git-fixes).\n- net: mana: Reserve extra CQ slot for the fence completion CQE (git-fixes).\n- net: mana: restore the XDP program pointer when pre-allocation fails (git-fixes).\n- net: page_pool: Remove zone/policy GFP flags when allocating XArray entries (git-fixes).\n- net: tls: Pass union tls_crypto_context pointer to memzero_explicit (bsc#1267564 jsc#PED-16401).\n- net: usb: catc: bound the RX packet length in catc_rx_done() (git-fixes).\n- net: usb: cdc_mbim: add MeiG Smart SRM821 to ZLP whitelist (stable-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: lan78xx: Fix URB reference leak in lan78xx_submit_deferred_urbs() (git-fixes).\n- net: usb: pegasus: don't rely on id table pointer arithmetic (stable-fixes).\n- net: usb: qmi_wwan: add MeiG SRM813Q (stable-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (stable-fixes).\n- net: usb: sr9700: include receive overhead in the length check (git-fixes).\n- net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value (git-fixes).\n- net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain (git-fixes).\n- net: wwan: t7xx: Add delay between MD and SAP suspend (stable-fixes).\n- net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() (git-fixes).\n- nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() (git-fixes).\n- nfc: llcp: fix -ENOMEM on connect with zero-length service name (git-fixes).\n- nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() (git-fixes).\n- nfc: llcp: Fix race condition in accept_queue lifecycle (git-fixes).\n- nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure (git-fixes).\n- nfc: llcp: fix slab-out-of-bounds reads when logging service names (git-fixes).\n- nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() (git-fixes).\n- nfc: nfcmrvl: validate helper command length before pull (git-fixes).\n- nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() (git-fixes).\n- nfc: port100: reject frames whose declared length exceeds the received data (git-fixes).\n- nfc: st21nfca: validate ISO15693 inventory length (git-fixes).\n- nfc: st21nfca: validate received frame size (git-fixes).\n- nfc: virtual_ncidev: Add missing ioctl compat handler (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- of: property: add missing kerneldoc for of_graph_get_endpoint_count() (stable-fixes).\n- PCI/MSI: Enable memory decoding before restoring MSI-X messages (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI/proc: Fix race between pci_proc_init() and pci_bus_add_device() (stable-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (stable-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (stable-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (stable-fixes).\n- PCI: Accept AtomicOps already enabled by the hypervisor (git-fixes).\n- PCI: altera: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Avoid SBR for Qualcomm WCN6855/WCN7850 WiFi, SDX62/SDX65 modems (stable-fixes).\n- PCI: iproc: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: mediatek: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: rockchip: Protect root bus removal with rescan lock (stable-fixes).\n- PCI: Stop setting cached power state to 'unknown' on unbind (stable-fixes).\n- PCI: switchtec: Add Gen6 Device IDs (stable-fixes).\n- PCI: Wait for device readiness after D3hot -\u003e D0uninitialized transition (stable-fixes).\n- PCI: xgene: Drop unnecessary OF node reference (git-fixes).\n- PCI: xgene: Drop XGENE_PCIE_IP_VER_UNKN (stable-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix PLL calc divisor overflow (git-fixes).\n- phy: mediatek: phy-mtk-hdmi-mt8195: Fix TMDS clk bit ratio setting (git-fixes).\n- pinctrl: meson: Fix typo in s4 group name (git-fixes).\n- pinctrl: single: free the IRQ on domain creation failure (git-fixes).\n- platform/x86: dell-laptop: add Inspiron N5110 to touchpad LED quirk table (stable-fixes).\n- platform/x86: hp-bioscfg: bound ordered-list parsing by the package count (stable-fixes).\n- platform/x86: hp-bioscfg: pass validated element count to package parsers (stable-fixes).\n- platform/x86: intel-hid: Add HP ProBook x360 440 G1 to button_array_table (stable-fixes).\n- power: sequencing: don't call .post_enable() if pwrseq_unit_enable() failed (git-fixes).\n- power: sequencing: fix NULL-pointer dereference in pwrseq_device_register() (git-fixes).\n- power: sequencing: fix NULL-pointer dereference in pwrseq_unit_new() (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: sc2731_charger: Convert to platform remove callback returning void (stable-fixes).\n- powerpc/crash: stop watchdogs before booting kdump kernel (bsc#1277705 ltc#220979).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/perf: Add power12 Base Performance Monitoring support (jsc#PED-16906).\n- powerpc/perf: Set cpumode flags using sample address (jsc#PED-16906).\n- powerpc/pseries: Handle and log pseries-wdt registration failures (bsc#1277705 ltc#220979).\n- powerpc/pseries: Limit PVR list to 16 entries for CAS negotiation (jsc#PED-16906).\n- powerpc/pseries: Move H_WATCHDOG definitions to a common header (bsc#1277705 ltc#220979).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Add Power12 architected mode (jsc#PED-16906).\n- powerpc: Add Power12 raw mode (jsc#PED-16906).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- RDMA/core: Fix potential use after free in counter_release() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_destroy_cq_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_destroy_srq_user() (git-fixes).\n- RDMA/core: Fix potential use after free in ib_free_cq() (git-fixes).\n- RDMA/core: Fix use after free in ib_query_qp() (git-fixes).\n- RDMA/counter: Fix incorrect port index in rdma_counter_init() error cleanup (git-fixes).\n- RDMA/erdma: Use IRQ-safe XArray helpers for QP and CQ tables (git-fixes).\n- RDMA/hfi1: Align probe error unwinding with device removal (git-fixes).\n- RDMA/hfi1: Allocate device data after PCI initialization (git-fixes).\n- RDMA/hfi1: Create workqueues before device initialization (git-fixes).\n- RDMA/hfi1: Defer device creation until probe succeeds (git-fixes).\n- RDMA/hfi1: Drop device data from hfi1_validate_rcvhdrcnt() (git-fixes).\n- RDMA/hfi1: Free RX data on late probe failure (git-fixes).\n- RDMA/hfi1: Initialize debugfs after probe completes (git-fixes).\n- RDMA/hfi1: Pass PCI device to hfi1_pcie_init() (git-fixes).\n- RDMA/hfi1: Preserve unit 0 on (git-fixes).\n- RDMA/hfi1: Remove redundant NULL checks in create_workqueues() (git-fixes).\n- RDMA/hfi1: Remove redundant PCI device ID validation (git-fixes).\n- RDMA/hfi1: Stop flushing the global IB workqueue (git-fixes).\n- RDMA/irdma: Add a refcount to track user ring MR associations (git-fixes).\n- RDMA/irdma: Add irdma_cq fields to track pbl allocations (git-fixes).\n- RDMA/irdma: Deduplicate the irdma_del_memlist logic (git-fixes).\n- RDMA/rvt: Return NULL after port allocation failure (git-fixes).\n- ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() (bsc#1277896).\n- rtc: aspeed: add AST2700 compatible (stable-fixes).\n- rtc: bq32000: add delay between RTC reads (stable-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- selftests: tls: add getsockopt test (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add key_generation argument to tls_crypto_info_init (bsc#1267564 jsc#PED-16401).\n- selftests: tls: add rekey tests (bsc#1267564 jsc#PED-16401).\n- serial: 8250: fix possible ISR soft lockup (stable-fixes).\n- serial: 8250_bcm7271: fix use-after-free in brcmuart_remove() (git-fixes).\n- serial: tegra: don't clear the Tx FIFO on an Rx-only reset (git-fixes).\n- serial: vt8500: Fix clock reference leak in vt8500_serial_probe() (git-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- soc: qcom: geni-se: Correct QUP Core ICC vote constants (git-fixes).\n- soundwire: cadence_master: wait and cancel cdns-\u003ework before clock stop (git-fixes).\n- soundwire: dmi-quirks: Disable ghost Realtek devices (stable-fixes).\n- soundwire: intel: Move suspend tracking from trigger to pm suspend (stable-fixes).\n- soundwire: only handle alert events when the peripheral is attached (stable-fixes).\n- soundwire: validate DT compatible before parsing it (stable-fixes).\n- spi: Add NULL check for spi_get_device_id() in spi_get_device_match_data() (stable-fixes).\n- spi: core: Abort active target transfer on controller suspend (stable-fixes).\n- spi: davinci: Unset POWERDOWN bit when releasing resources (stable-fixes).\n- spi: dw-dma: Wait for controller idle before completing Tx (stable-fixes).\n- spi: dw: fix wrong RX_SAMPLE_DLY setting after resume (stable-fixes).\n- spi: spi-qcom-qspi: Fix incomplete error handling in runtime PM (stable-fixes).\n- spi: xilinx: let transfers timeout in case of no IRQ (stable-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- thermal/drivers/qcom/tsens: Atomic temperature read with hardware-guided retries (stable-fixes).\n- thermal/drivers/tegra/soctherma: Switch to devm cooling device registration (stable-fixes).\n- thermal: gov_step_wise: Fix stale mitigation vote with non-zero lower bounds (git-fixes).\n- thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() (stable-fixes).\n- thunderbolt: Fix KASAN reported use-after-free when request is canceled (git-fixes).\n- thunderbolt: Improve multi-display DisplayPort tunnel allocation (stable-fixes).\n- thunderbolt: Increase timeout for Configuration Ready bit (stable-fixes).\n- thunderbolt: Keep the domain reference while processing hotplug (stable-fixes).\n- thunderbolt: Keep XDomain reference during the lifetime of a service (stable-fixes).\n- thunderbolt: Reject oversized XDomain properties responses (git-fixes).\n- thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() (stable-fixes).\n- thunderbolt: Set tb-\u003eroot_switch to NULL when domain is stopped (stable-fixes).\n- thunderbolt: Verify Router Ready bit is set after router enumeration (stable-fixes).\n- tls: add counters for rekey (bsc#1267564 jsc#PED-16401).\n- tls: block decryption when a rekey is pending (bsc#1267564 jsc#PED-16401).\n- tls: implement rekey for TLS1.3 (bsc#1267564 jsc#PED-16401).\n- tls: skip setting sk_write_space on rekey (bsc#1267564 jsc#PED-16401).\n- tty: serial: qcom_geni_serial: Keep console RX functional after deep idle (git-fixes).\n- tty: vt: fix memory leak in vc_allocate() (git-fixes).\n- usb-storage: ene_ub6250: fix race between scan work and probe (stable-fixes).\n- USB: cdc-acm: fix racy TIOCMIWAIT implementation (git-fixes).\n- USB: cdc-acm: skip URB restart in port_shutdown if disconnected (git-fixes).\n- USB: cdc-acm: start bulk-IN polling when ALWAYS_POLL_CTRL is set (stable-fixes).\n- usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe (git-fixes).\n- usb: cdns3: fix use-after-free in cdns3_gadget_exit() (git-fixes).\n- usb: chipidea: tegra: disable runtime PM on resume failure (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: clear both ep_in and ep_out for non-ep0 control endpoints (git-fixes).\n- usb: core: hcd: fix possible deadlock in rh control transfers (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: dwc3: am62: Fix runtime PM usage count leak on probe error path (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed-vhub: cancel wake work on device removal (git-fixes).\n- usb: gadget: aspeed_udc: avoid past-the-end iterator in dequeue (stable-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: aspeed_udc: Convert to platform remove callback returning void (stable-fixes).\n- USB: gadget: dummy-hcd: Fix wait for outstanding request completions (git-fixes).\n- usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC (git-fixes).\n- usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd (git-fixes).\n- USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() (stable-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- usb: gadget: goku_udc: avoid NULL deref of dev-\u003edriver in INT_USBRESET log (stable-fixes).\n- usb: gadget: udc: skip pullup() if already connected (stable-fixes).\n- usb: host: add ARCH_AIROHA in XHCI MTK dependency (stable-fixes).\n- usb: hub: use shorter 120ms post resume hold for SS root hubs (git-fixes).\n- usb: image: mdc800: change kmalloc() to kzalloc() (stable-fixes).\n- USB: make to_usb_driver() use container_of_const() (stable-fixes).\n- usb: octeon-hcd: fix the FIFO-flush timeout computation (git-fixes).\n- usb: ohci-da8xx: disable controller wakeup on cleanup (git-fixes).\n- usb: ohci-s3c2410: disable controller wakeup on removal (git-fixes).\n- usb: ohci-st: disable controller wakeup on removal (git-fixes).\n- USB: serial: fix driver deregistration order (git-fixes).\n- USB: serial: fix dynamic id driver deregistration race (git-fixes).\n- USB: serial: fix port tear down use-after-free (git-fixes).\n- USB: serial: quatech2: fix baud rate overflow (git-fixes).\n- usb: serial: spcp8x5: don't store usb_device_id (stable-fixes).\n- USB: serial: ssu100: fix baud rate overflow (git-fixes).\n- usb: storage: sierra_ms: reject short SWoC info transfers (git-fixes).\n- usb: typec: anx7411 - stop the IRQ before destroying the workqueue (git-fixes).\n- usb: typec: tcpm: recover after failure to start the frs ams (git-fixes).\n- usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect() (git-fixes).\n- usb: typec: ucsi: displayport: Current CAM OOB index fixup (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: Get the connector fwnode based on reg value (git-fixes).\n- usb: typec: ucsi: glink: fix use-after-free of ucsi on remove (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: usbtmc: don't store usb_device_id (stable-fixes).\n- usb: xhci: use cached HCSPARAMS1 value (stable-fixes).\n- usb: xusbatm: don't rely on id table pointer arithmetic (stable-fixes).\n- usbip: vhci_hcd: fix NULL deref in status_show_vhci (stable-fixes).\n- watchdog: da9062: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog (git-fixes).\n- watchdog: digicolor: Avoid division by zero (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix premature reset during timeout update (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Propagate error code in resume() (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: rtd119x: Avoid division by zero (git-fixes).\n- watchdog: sp5100_tco: Fix pci_dev reference leak in sp5100_tco_init() (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath9k_htc: don't store usb_device_id (stable-fixes).\n- wifi: ath11k: cleanup arsta in ath11k_mac_peer_cleanup_all() (git-fixes).\n- wifi: ath11k: Fix error handling in ath11k_wmi_p2p_noa_event() (git-fixes).\n- wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi (stable-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath11k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: ath11k: implement handling of P2P NoA event (stable-fixes).\n- wifi: ath12k: fix stride mismatch in mac_phy_caps_parse() (git-fixes).\n- wifi: brcmfmac: fix lost 802.1x TX completion wakeup (git-fixes).\n- wifi: brcmsmac: fix UAF in brcms_free_timer() (git-fixes).\n- wifi: cfg80211: check IP header size in cfg80211_classify8021d() (git-fixes).\n- wifi: cfg80211: don't filter by BSS type when removing stale entries (git-fixes).\n- wifi: cfg80211: don't get the radio mask for netdev-less wdevs (git-fixes).\n- wifi: cfg80211: expose cfg80211_chandef_get_width() (stable-fixes).\n- wifi: cfg80211: fix width unit in cfg80211_radio_chandef_valid() (git-fixes).\n- wifi: cfg80211: only group hidden BSSes with beacon entries (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: skip regulatory for punctured subchannels (stable-fixes).\n- wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie() (stable-fixes).\n- wifi: cfg80211: validate rx/tx MLME callback frame lengths before access (stable-fixes).\n- wifi: iwlegacy: fix broadcast stations deallocation (git-fixes).\n- wifi: iwlwifi: acpi: validate WGDS table revision index (stable-fixes).\n- wifi: iwlwifi: bound aligned TLV advance in FW parser (stable-fixes).\n- wifi: iwlwifi: mei: add support for SAP version 4 (stable-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mvm: add a check on the tid coming from the firmware (stable-fixes).\n- wifi: iwlwifi: mvm: fix a possible underflow (stable-fixes).\n- wifi: iwlwifi: mvm: fix an off-by-1 boundary check (stable-fixes).\n- wifi: iwlwifi: mvm: fix out-of-bounds tid_data access in BA notif (stable-fixes).\n- wifi: iwlwifi: mvm: fix sched scan IE sizing (stable-fixes).\n- wifi: iwlwifi: mvm: parse beacon notif per layout (stable-fixes).\n- wifi: iwlwifi: mvm: validate mac_link_id in session protect notif (stable-fixes).\n- wifi: iwlwifi: mvm: validate sta_id in BA window status notif (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: libertas: reject short monitor TX frames (stable-fixes).\n- wifi: libipw: fix key index receive bound checks (stable-fixes).\n- wifi: libipw: reject too-short association responses (git-fixes).\n- wifi: libipw: reject too-short beacon and probe responses (git-fixes).\n- wifi: mac80211: abort chanswitch when leaving a mesh (git-fixes).\n- wifi: mac80211: add HE 6 GHz capability in the scan elems len (git-fixes).\n- wifi: mac80211: always allow transmitting null-data on TXQs (stable-fixes).\n- wifi: mac80211: avoid WARN in set_bitrate_mask when sdata not in driver (git-fixes).\n- wifi: mac80211: don't access the TSF of a down interface (git-fixes).\n- wifi: mac80211: don't allow injecting frames wider than the chanctx (git-fixes).\n- wifi: mac80211: don't allow link changes when iface is down (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't offload TC setup on AP_VLAN interfaces (git-fixes).\n- wifi: mac80211: don't RCU-dereference the mesh CSA settings we just set (git-fixes).\n- wifi: mac80211: don't start a ROC while scanning (git-fixes).\n- wifi: mac80211: explicitly disable FTM responder on AP stop (stable-fixes).\n- wifi: mac80211: ibss: wait for in-flight TX on disconnect (stable-fixes).\n- wifi: mac80211: mesh: release the channel if start fails (git-fixes).\n- wifi: mac80211: mesh: reset the CSA state when leaving (git-fixes).\n- wifi: mac80211: only operate on TDLS peers in the TDLS code (git-fixes).\n- wifi: mac80211: require a peer station for TDLS setup confirm (git-fixes).\n- wifi: mac80211: reset state when starting AP fails (git-fixes).\n- wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown (git-fixes).\n- wifi: mac80211: set up the TX info early to fix failure paths (git-fixes).\n- wifi: mac80211: suppress chanctx warning for debugfs reset (git-fixes).\n- wifi: mac80211: unlist vifs when their netdev is unregistered (git-fixes).\n- wifi: mac80211: validate deauth frame length before reason access (stable-fixes).\n- wifi: mt76: mt7915: fix chainmask handling for non-dbdc phys on band 1 (git-fixes).\n- wifi: mt76: mt7915: report RX chain signal for all RX paths (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: add Netgear A8500 USB device ID (stable-fixes).\n- wifi: mt76: mt7925: handle 320MHz bandwidth in RXV and TXS (stable-fixes).\n- wifi: mt76: mt7925: populate EHT 320MHz MCS map in sta_rec (stable-fixes).\n- wifi: mt76: transform aspm_conf for pci_disable_link_state (stable-fixes).\n- wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length (git-fixes).\n- wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path (git-fixes).\n- wifi: mwifiex: replace one-element arrays with flexible array members (stable-fixes).\n- wifi: mwifiex: validate action frame fixed fields (git-fixes).\n- wifi: mwifiex: validate scan response extents (git-fixes).\n- wifi: nl80211: reject beacons with bad HE operation (stable-fixes).\n- wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST (git-fixes).\n- wifi: p54: validate curve data length in the calibration curve converters (git-fixes).\n- wifi: ralink: RT2X00: init EEPROM properly (stable-fixes).\n- wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers (stable-fixes).\n- wifi: rsi: fix heap OOB write on key removal (git-fixes).\n- wifi: rsi: validate beacon length before fixed buffer copy (stable-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtw88: Add NULL check for chip-\u003eedcca_th in rtw_fw_adaptivity_result() (stable-fixes).\n- wifi: rtw88: Fix the random 'error beacon valid' messages for USB (stable-fixes).\n- wifi: rtw88: TX QOS Null data the same way as Null data (stable-fixes).\n- wifi: rtw89: cleanup unused rtwdev::roc_work (stable-fixes).\n- wifi: rtw89: pci: enable LTR based on pcie control register (stable-fixes).\n- wifi: rtw89: phy: check length before parsing PHY status IE (stable-fixes).\n- wifi: virt_wifi: don't transfer operstate before register (git-fixes).\n- wifi: virt_wifi: free skb when disconnected (git-fixes).\n- wifi: wilc1000: fix out-of-bounds read in P2P public action frames (git-fixes).\n- wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() (git-fixes).\n- wifi: wlcore: release runtime PM ref on regdomain config failure (git-fixes).\n- x86/mce: Add support for physical address valid bit (jsc#PED-16968).\n- x86/mm: Fix pmd_modify() dropping the dirty bit (bsc#1275455).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951).\n- xfs: don't free cowblocks from under dirty pagecache on unshare (bsc#1278709).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n- xhci: Prevent queuing new commands if xhci is inaccessible (stable-fixes).\n","status":"published","published":"2026-10-16T13:33:59Z","modified":"2026-10-17T10:00:05.985817162Z","updated_at":"2026-11-02T15:54:05.838224Z"},{"id":"USN-8567-1","title":"linux, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320)\n","status":"published","published":"2026-07-20T15:36:35Z","modified":"2026-11-07T01:46:48.030854859Z","updated_at":"2026-11-07T01:56:38.538236Z"},{"id":"USN-8574-1","title":"linux-gcp-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-21T09:51:58Z","modified":"2026-11-09T12:46:41.603455464Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8574-2","title":"linux-fips, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T07:48:36Z","modified":"2026-11-09T12:48:51.609882158Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8574-3","title":"linux-ibm, linux-ibm-6.8, linux-nvidia-tegra, linux-xilinx vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-28T07:23:25Z","modified":"2026-11-09T12:49:17.012782847Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-1","title":"linux-oracle-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-23T07:57:09Z","modified":"2026-11-09T12:46:39.626735177Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-2","title":"linux-aws vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-24T10:14:09Z","modified":"2026-11-09T12:46:40.833371554Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-3","title":"linux-aws-6.8, linux-aws-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-28T07:25:50Z","modified":"2026-11-09T12:49:11.651297869Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8596-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23226, CVE-2026-23227, CVE-2026-23244, CVE-2026-23245,\nCVE-2026-23246, CVE-2026-23253, CVE-2026-23255, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23276, CVE-2026-23277, CVE-2026-23279,\nCVE-2026-23281, CVE-2026-23284, CVE-2026-23285, CVE-2026-23286,\nCVE-2026-23287, CVE-2026-23289, CVE-2026-23290, CVE-2026-23291,\nCVE-2026-23292, CVE-2026-23293, CVE-2026-23296, CVE-2026-23298,\nCVE-2026-23300, CVE-2026-23302, CVE-2026-23303, CVE-2026-23304,\nCVE-2026-23306, CVE-2026-23307, CVE-2026-23308, CVE-2026-23310,\nCVE-2026-23312, CVE-2026-23313, CVE-2026-23315, CVE-2026-23317,\nCVE-2026-23318, CVE-2026-23319, CVE-2026-23321, CVE-2026-23324,\nCVE-2026-23325, CVE-2026-23330, CVE-2026-23334, CVE-2026-23335,\nCVE-2026-23336, CVE-2026-23339, CVE-2026-23340, CVE-2026-23343,\nCVE-2026-23347, CVE-2026-23352, CVE-2026-23356, CVE-2026-23357,\nCVE-2026-23359, CVE-2026-23360, CVE-2026-23361, CVE-2026-23362,\nCVE-2026-23363, CVE-2026-23364, CVE-2026-23365, CVE-2026-23367,\nCVE-2026-23368, CVE-2026-23369, CVE-2026-23370, CVE-2026-23372,\nCVE-2026-23374, CVE-2026-23375, CVE-2026-23378, CVE-2026-23379,\nCVE-2026-23381, CVE-2026-23382, CVE-2026-23383, CVE-2026-23386,\nCVE-2026-23387, CVE-2026-23388, CVE-2026-23389, CVE-2026-23391,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439,\nCVE-2026-23440, CVE-2026-23441, CVE-2026-23442, CVE-2026-23444,\nCVE-2026-23446, CVE-2026-23447, CVE-2026-23448, CVE-2026-23449,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23456, CVE-2026-23457,\nCVE-2026-23458, CVE-2026-23460, CVE-2026-23461, CVE-2026-23462,\nCVE-2026-23463, CVE-2026-23464, CVE-2026-23465, CVE-2026-23468,\nCVE-2026-23470, CVE-2026-23474, CVE-2026-23475, CVE-2026-31389,\nCVE-2026-31391, CVE-2026-31392, CVE-2026-31393, CVE-2026-31394,\nCVE-2026-31396, CVE-2026-31399, CVE-2026-31400, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31412, CVE-2026-31413, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31421, CVE-2026-31422,\nCVE-2026-31423, CVE-2026-31424, CVE-2026-31425, CVE-2026-31426,\nCVE-2026-31427, CVE-2026-31428, CVE-2026-31429, CVE-2026-31430,\nCVE-2026-31432, CVE-2026-31433, CVE-2026-31434, CVE-2026-31438,\nCVE-2026-31439, CVE-2026-31440, CVE-2026-31441, CVE-2026-31446,\nCVE-2026-31447, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53354,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T08:06:00Z","modified":"2026-11-09T12:48:44.712103783Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8606-1","title":"linux-azure, linux-azure-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\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  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\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  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, 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-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\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-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, 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-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43378, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43383, CVE-2026-43384, CVE-2026-43386,\nCVE-2026-43387, CVE-2026-43395, CVE-2026-43397, CVE-2026-43405,\nCVE-2026-43406, CVE-2026-43407, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43414,\nCVE-2026-43415, CVE-2026-43419, CVE-2026-43420, CVE-2026-43421,\nCVE-2026-43424, CVE-2026-43425, CVE-2026-43426, CVE-2026-43427,\nCVE-2026-43428, CVE-2026-43429, CVE-2026-43430, CVE-2026-43432,\nCVE-2026-43436, CVE-2026-43437, CVE-2026-43439, CVE-2026-43441,\nCVE-2026-43445, CVE-2026-43448, CVE-2026-43449, CVE-2026-43450,\nCVE-2026-43451, CVE-2026-43452, CVE-2026-43453, CVE-2026-43455,\nCVE-2026-43456, CVE-2026-43457, CVE-2026-43458, CVE-2026-43459,\nCVE-2026-43466, CVE-2026-43467, CVE-2026-43468, CVE-2026-43469,\nCVE-2026-43471, CVE-2026-43472, CVE-2026-43473, CVE-2026-43475,\nCVE-2026-43476, CVE-2026-43480, CVE-2026-43483, CVE-2026-43484,\nCVE-2026-43488, CVE-2026-43490, CVE-2026-43491, CVE-2026-43492,\nCVE-2026-43493, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497,\nCVE-2026-43499, CVE-2026-43501, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45855, CVE-2026-45856, CVE-2026-45857, CVE-2026-45858,\nCVE-2026-45859, CVE-2026-45860, CVE-2026-45861, CVE-2026-45862,\nCVE-2026-45864, CVE-2026-45865, CVE-2026-45866, CVE-2026-45867,\nCVE-2026-45868, CVE-2026-45869, CVE-2026-45870, CVE-2026-45871,\nCVE-2026-45872, CVE-2026-45873, CVE-2026-45875, CVE-2026-45877,\nCVE-2026-45878, CVE-2026-45879, CVE-2026-45880, CVE-2026-45881,\nCVE-2026-45882, CVE-2026-45883, CVE-2026-45884, CVE-2026-45885,\nCVE-2026-45886, CVE-2026-45890, CVE-2026-45891, CVE-2026-45893,\nCVE-2026-45895, CVE-2026-45899, CVE-2026-45902, CVE-2026-45904,\nCVE-2026-45905, CVE-2026-45910, CVE-2026-45911, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45920, CVE-2026-45921,\nCVE-2026-45923, CVE-2026-45924, CVE-2026-45928, CVE-2026-45935,\nCVE-2026-45936, CVE-2026-45938, CVE-2026-45941, CVE-2026-45942,\nCVE-2026-45943, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45956, CVE-2026-45957, CVE-2026-45958,\nCVE-2026-45960, CVE-2026-45962, CVE-2026-45964, CVE-2026-45965,\nCVE-2026-45968, CVE-2026-45969, CVE-2026-45970, CVE-2026-45972,\nCVE-2026-45973, CVE-2026-45974, CVE-2026-45976, CVE-2026-45978,\nCVE-2026-45981, CVE-2026-45982, CVE-2026-45983, CVE-2026-45984,\nCVE-2026-45985, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46043,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46115, CVE-2026-46116, CVE-2026-46117,\nCVE-2026-46119, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122,\nCVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126,\nCVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46131,\nCVE-2026-46132, CVE-2026-46133, CVE-2026-46135, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46185, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46195, CVE-2026-46196,\nCVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200,\nCVE-2026-46201, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206,\nCVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46211,\nCVE-2026-46212, CVE-2026-46214, CVE-2026-46218, CVE-2026-46219,\nCVE-2026-46220, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227,\nCVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232,\nCVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236,\nCVE-2026-46238, CVE-2026-46241, CVE-2026-46243, CVE-2026-46244,\nCVE-2026-46246, CVE-2026-46247, CVE-2026-46249, CVE-2026-46250,\nCVE-2026-46251, CVE-2026-46253, CVE-2026-46254, CVE-2026-46255,\nCVE-2026-46259, CVE-2026-46260, CVE-2026-46261, CVE-2026-46265,\nCVE-2026-46266, CVE-2026-46267, CVE-2026-46270, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46289, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-46328, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:17:16Z","modified":"2026-11-07T01:46:10.910402805Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8607-1","title":"linux-azure-fde vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\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  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\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  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, 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-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, 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-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, 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-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, 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-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:20:29Z","modified":"2026-11-07T01:46:01.058375657Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8608-1","title":"linux-azure-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:23:19Z","modified":"2026-11-09T12:47:05.283755841Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8609-1","title":"linux-azure-fde-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\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  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\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  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, 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-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, 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-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, 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-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, 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-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:26:03Z","modified":"2026-11-07T01:45:29.525006235Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8619-1","title":"linux-hwe-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\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  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\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  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, 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-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\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-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, 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-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43362, CVE-2026-43363, CVE-2026-43365,\nCVE-2026-43366, CVE-2026-43368, CVE-2026-43370, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43378, CVE-2026-43380,\nCVE-2026-43381, CVE-2026-43382, CVE-2026-43383, CVE-2026-43384,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43406, CVE-2026-43407, CVE-2026-43408,\nCVE-2026-43409, CVE-2026-43411, CVE-2026-43412, CVE-2026-43413,\nCVE-2026-43414, CVE-2026-43415, CVE-2026-43419, CVE-2026-43420,\nCVE-2026-43421, CVE-2026-43424, CVE-2026-43425, CVE-2026-43426,\nCVE-2026-43427, CVE-2026-43428, CVE-2026-43429, CVE-2026-43430,\nCVE-2026-43432, CVE-2026-43436, CVE-2026-43437, CVE-2026-43439,\nCVE-2026-43441, CVE-2026-43445, CVE-2026-43448, CVE-2026-43449,\nCVE-2026-43450, CVE-2026-43451, CVE-2026-43452, CVE-2026-43453,\nCVE-2026-43455, CVE-2026-43456, CVE-2026-43457, CVE-2026-43458,\nCVE-2026-43459, CVE-2026-43466, CVE-2026-43467, CVE-2026-43468,\nCVE-2026-43469, CVE-2026-43471, CVE-2026-43472, CVE-2026-43473,\nCVE-2026-43475, CVE-2026-43476, CVE-2026-43480, CVE-2026-43483,\nCVE-2026-43484, CVE-2026-43488, CVE-2026-43490, CVE-2026-43491,\nCVE-2026-43492, CVE-2026-43493, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43501, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45847, CVE-2026-45848, CVE-2026-45849, CVE-2026-45851,\nCVE-2026-45852, CVE-2026-45855, CVE-2026-45856, CVE-2026-45857,\nCVE-2026-45858, CVE-2026-45859, CVE-2026-45860, CVE-2026-45861,\nCVE-2026-45862, CVE-2026-45864, CVE-2026-45865, CVE-2026-45866,\nCVE-2026-45867, CVE-2026-45868, CVE-2026-45869, CVE-2026-45870,\nCVE-2026-45871, CVE-2026-45872, CVE-2026-45873, CVE-2026-45875,\nCVE-2026-45877, CVE-2026-45878, CVE-2026-45879, CVE-2026-45880,\nCVE-2026-45881, CVE-2026-45882, CVE-2026-45883, CVE-2026-45884,\nCVE-2026-45885, CVE-2026-45886, CVE-2026-45890, CVE-2026-45891,\nCVE-2026-45893, CVE-2026-45895, CVE-2026-45899, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45911,\nCVE-2026-45912, CVE-2026-45913, CVE-2026-45914, CVE-2026-45915,\nCVE-2026-45916, CVE-2026-45917, CVE-2026-45919, CVE-2026-45920,\nCVE-2026-45921, CVE-2026-45923, CVE-2026-45924, CVE-2026-45928,\nCVE-2026-45935, CVE-2026-45936, CVE-2026-45938, CVE-2026-45941,\nCVE-2026-45942, CVE-2026-45943, CVE-2026-45946, CVE-2026-45947,\nCVE-2026-45948, CVE-2026-45954, CVE-2026-45956, CVE-2026-45957,\nCVE-2026-45958, CVE-2026-45960, CVE-2026-45962, CVE-2026-45964,\nCVE-2026-45965, CVE-2026-45968, CVE-2026-45969, CVE-2026-45970,\nCVE-2026-45972, 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-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45988, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46043, CVE-2026-46044, CVE-2026-46046, CVE-2026-46047,\nCVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052,\nCVE-2026-46053, CVE-2026-46056, CVE-2026-46058, CVE-2026-46061,\nCVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065,\nCVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46072,\nCVE-2026-46073, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077,\nCVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46082,\nCVE-2026-46083, CVE-2026-46084, CVE-2026-46086, CVE-2026-46088,\nCVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092,\nCVE-2026-46094, CVE-2026-46098, CVE-2026-46099, CVE-2026-46101,\nCVE-2026-46102, CVE-2026-46103, CVE-2026-46106, CVE-2026-46107,\nCVE-2026-46108, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112,\nCVE-2026-46113, CVE-2026-46114, CVE-2026-46115, CVE-2026-46116,\nCVE-2026-46117, CVE-2026-46119, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46135,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46185,\nCVE-2026-46186, CVE-2026-46187, CVE-2026-46189, CVE-2026-46190,\nCVE-2026-46191, CVE-2026-46193, CVE-2026-46194, CVE-2026-46195,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46243,\nCVE-2026-46244, CVE-2026-46246, CVE-2026-46247, CVE-2026-46249,\nCVE-2026-46250, CVE-2026-46251, CVE-2026-46253, CVE-2026-46254,\nCVE-2026-46255, CVE-2026-46259, CVE-2026-46260, CVE-2026-46261,\nCVE-2026-46265, CVE-2026-46266, CVE-2026-46267, CVE-2026-46270,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46289,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-46328, CVE-2026-52911,\nCVE-2026-52920, CVE-2026-52925, CVE-2026-52933, CVE-2026-52936,\nCVE-2026-52951, CVE-2026-52954, CVE-2026-52955, CVE-2026-52957,\nCVE-2026-52958, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963,\nCVE-2026-52964, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969,\nCVE-2026-52970, CVE-2026-52974, CVE-2026-52975, CVE-2026-52977,\nCVE-2026-52981, CVE-2026-52982, CVE-2026-52984, CVE-2026-52985,\nCVE-2026-52986, CVE-2026-52989, CVE-2026-52990, CVE-2026-52992,\nCVE-2026-52993, CVE-2026-52995, CVE-2026-52998, CVE-2026-52999,\nCVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004,\nCVE-2026-53006, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013,\nCVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53021,\nCVE-2026-53022, CVE-2026-53023, CVE-2026-53032, CVE-2026-53033,\nCVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037,\nCVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53043,\nCVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048,\nCVE-2026-53049, CVE-2026-53050, CVE-2026-53052, CVE-2026-53056,\nCVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061,\nCVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065,\nCVE-2026-53066, CVE-2026-53068, CVE-2026-53069, CVE-2026-53071,\nCVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075,\nCVE-2026-53076, CVE-2026-53077, CVE-2026-53082, CVE-2026-53083,\nCVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53088,\nCVE-2026-53093, CVE-2026-53094, CVE-2026-53096, CVE-2026-53097,\nCVE-2026-53098, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112,\nCVE-2026-53115, CVE-2026-53117, CVE-2026-53122, CVE-2026-53123,\nCVE-2026-53126, CVE-2026-53128, CVE-2026-53130, CVE-2026-53279,\nCVE-2026-53287, CVE-2026-53289, CVE-2026-53291, CVE-2026-53293,\nCVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53303,\nCVE-2026-53304, CVE-2026-53306, CVE-2026-53309, CVE-2026-53314,\nCVE-2026-53320, CVE-2026-53369, CVE-2026-53374, CVE-2026-53375,\nCVE-2026-53376, CVE-2026-53379, CVE-2026-63838, CVE-2026-63843,\nCVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847,\nCVE-2026-63848, CVE-2026-63851, CVE-2026-63852, CVE-2026-63854,\nCVE-2026-63855, CVE-2026-63856, CVE-2026-63860, CVE-2026-63861,\nCVE-2026-63862, CVE-2026-63865)\n","status":"published","published":"2026-07-28T07:28:45Z","modified":"2026-11-07T01:45:56.683802514Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8665-1","title":"linux-raspi, linux-raspi-realtime vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\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  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-52911, CVE-2026-52920, CVE-2026-52925, CVE-2026-52933,\nCVE-2026-52936, CVE-2026-52951, CVE-2026-52954, CVE-2026-52955,\nCVE-2026-52957, CVE-2026-52958, CVE-2026-52961, CVE-2026-52962,\nCVE-2026-52963, CVE-2026-52964, CVE-2026-52967, CVE-2026-52968,\nCVE-2026-52969, CVE-2026-52970, CVE-2026-52974, CVE-2026-52975,\nCVE-2026-52977, CVE-2026-52981, CVE-2026-52982, CVE-2026-52984,\nCVE-2026-52985, CVE-2026-52986, CVE-2026-52989, CVE-2026-52990,\nCVE-2026-52992, CVE-2026-52993, CVE-2026-52995, CVE-2026-52998,\nCVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003,\nCVE-2026-53004, CVE-2026-53006, CVE-2026-53011, CVE-2026-53012,\nCVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016,\nCVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53032,\nCVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036,\nCVE-2026-53037, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041,\nCVE-2026-53043, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047,\nCVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53052,\nCVE-2026-53056, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060,\nCVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064,\nCVE-2026-53065, CVE-2026-53066, CVE-2026-53068, CVE-2026-53069,\nCVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074,\nCVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53082,\nCVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086,\nCVE-2026-53088, CVE-2026-53093, CVE-2026-53094, CVE-2026-53096,\nCVE-2026-53097, CVE-2026-53098, CVE-2026-53110, CVE-2026-53111,\nCVE-2026-53112, CVE-2026-53115, CVE-2026-53117, CVE-2026-53122,\nCVE-2026-53123, CVE-2026-53126, CVE-2026-53128, CVE-2026-53130,\nCVE-2026-53279, CVE-2026-53287, CVE-2026-53289, CVE-2026-53291,\nCVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296,\nCVE-2026-53303, CVE-2026-53304, CVE-2026-53306, CVE-2026-53309,\nCVE-2026-53314, CVE-2026-53320, CVE-2026-53369, CVE-2026-53374,\nCVE-2026-53375, CVE-2026-53376, CVE-2026-53379, CVE-2026-63838,\nCVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846,\nCVE-2026-63847, CVE-2026-63848, CVE-2026-63851, CVE-2026-63852,\nCVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63860,\nCVE-2026-63861, CVE-2026-63862, CVE-2026-63865, CVE-2026-64164,\nCVE-2026-64587)\n","status":"published","published":"2026-08-20T23:31:14Z","modified":"2026-11-09T12:48:40.63232576Z","updated_at":"2026-11-07T01:56:47.245871Z"}]}}