{"id":"CVE-2026-23317","aliases":["AZL-80714","BELL-CVE-2026-23317","CLSA-2026-1786352940","DEBIAN-CVE-2026-23317","EUVD-2026-15264","GHSA-x2vc-23cg-h9h7","MGASA-2026-0097","MGASA-2026-0098","OESA-2026-2311","OESA-2026-2418","OESA-2026-2493","OESA-2026-3704","ROOT-OS-DEBIAN-12-CVE-2026-23317","ROOT-OS-UBUNTU-2404-CVE-2026-23317","SUSE-SU-2026:1573-1","SUSE-SU-2026:1574-1","SUSE-SU-2026:1606-1","SUSE-SU-2026:1643-1","SUSE-SU-2026:1661-1","SUSE-SU-2026:21114-1","SUSE-SU-2026:21123-1","SUSE-SU-2026:21255-1","SUSE-SU-2026:2134-1","SUSE-SU-2026:2149-1","SUSE-SU-2026:2159-1","SUSE-SU-2026:2172-1","SUSE-SU-2026:2176-1","SUSE-SU-2026:2181-1","SUSE-SU-2026:21834-1","SUSE-SU-2026:21841-1","SUSE-SU-2026:21845-1","SUSE-SU-2026:21860-1","SUSE-SU-2026:21886-1","SUSE-SU-2026:21887-1","SUSE-SU-2026:21888-1","SUSE-SU-2026:21889-1","SUSE-SU-2026:21890-1","SUSE-SU-2026:21891-1","SUSE-SU-2026:21892-1","SUSE-SU-2026:21893-1","SUSE-SU-2026:21896-1","SUSE-SU-2026:21900-1","SUSE-SU-2026:21901-1","SUSE-SU-2026:21902-1","SUSE-SU-2026:21903-1","SUSE-SU-2026:21904-1","SUSE-SU-2026:21905-1","SUSE-SU-2026:21906-1","SUSE-SU-2026:21907-1","SUSE-SU-2026:21910-1","SUSE-SU-2026:21921-1","SUSE-SU-2026:21922-1","SUSE-SU-2026:21923-1","SUSE-SU-2026:21924-1","SUSE-SU-2026:21925-1","SUSE-SU-2026:21926-1","SUSE-SU-2026:21927-1","SUSE-SU-2026:21928-1","SUSE-SU-2026:21929-1","SUSE-SU-2026:21932-1","SUSE-SU-2026:21933-1","SUSE-SU-2026:21934-1","SUSE-SU-2026:21935-1","SUSE-SU-2026:21936-1","SUSE-SU-2026:21937-1","SUSE-SU-2026:21938-1","SUSE-SU-2026:21939-1","SUSE-SU-2026:21942-1","SUSE-SU-2026:21958-1","SUSE-SU-2026:21959-1","SUSE-SU-2026:21960-1","SUSE-SU-2026:21962-1","SUSE-SU-2026:21963-1","SUSE-SU-2026:21969-1","SUSE-SU-2026:21970-1","SUSE-SU-2026:21972-1","SUSE-SU-2026:21979-1","SUSE-SU-2026:21982-1","SUSE-SU-2026:21983-1","SUSE-SU-2026:2199-1","SUSE-SU-2026:22030-1","SUSE-SU-2026:22031-1","SUSE-SU-2026:22033-1","SUSE-SU-2026:22038-1","UBUNTU-CVE-2026-23317","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","openSUSE-SU-2026:20826-1"],"aliases_more":3,"status":"published","title":"drm/vmwgfx: Return the correct value in vmw_translate_ptr functions","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00139,"percentile":0.03312,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-457","CWE-908"],"published":"2026-03-25T10:27:11Z","modified":"2026-11-07T01:46:48Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.130.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.80-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.167","6.6.130","6.12.77","6.18.17","6.19.7"],"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.8-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"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.74-r0"},{"fixed":"6.12.80-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els10"}]}],"bundled":147},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.19.7"}]}]},{"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.8-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.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.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~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.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-15.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-89.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-314.0.0.217.oe2203sp4"}]}],"bundled":31},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.1.12.150.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.13.139.oe2403"}]}],"bundled":30},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.3.29.160.oe2403sp3"}]}],"bundled":165},{"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 Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.1"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.37.2"}]}],"bundled":40},{"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.37.2"}]}],"bundled":40},{"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.37.1"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.127.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.127.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1.150500.6.71.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_37","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1.150500.6.71.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1.150500.6.71.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1.150500.6.71.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1.150500.6.71.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.144.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.33.1"}]}],"bundled":206},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.33.1"}]}],"bundled":206},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13-160000.4.3"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13-160000.4.3"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-livepatch-SLE16_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-livepatch-SLE16_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6-160000.1.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-livepatch-SLE16_Update_5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6-160000.1.1"}]}],"bundled":6},{"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: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"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"}],"references":[{"url":"https://git.kernel.org/stable/c/ce3a5cf139787c186d5d54336107298cacaad2b9","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/7e55d0788b362c93660b80cc5603031bbbdefa98","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/36cb28b6d303a81e6ed4536017090e85e0143e42","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/531f45589787799aa81b63e1e1f8e71db5d93dd1","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/149f028772fa2879d9316b924ce948a6a0877e45","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/5023ca80f9589295cb60735016e39fc5cc714243","tags":["Patch","web","report"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-784472.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23317","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-x2vc-23cg-h9h7"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23317","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1786352940.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52456","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21716","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21874","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37793","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39811","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40325","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23187","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31655","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43233","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43339","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43370","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43459","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53347","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64561","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23317.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-23317","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0097.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35281","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.121","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.122","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.123","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.124","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.125","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.126","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.127","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.128","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.129","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.130","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0098.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35282","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2311","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31515","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31521","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31523","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31592","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-31667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31674","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31682","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-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43049","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-43124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43284","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38183","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31447","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43470","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43472","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43492","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3704","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-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-43078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63887","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63956","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64306","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64355","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64380","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64382","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64456","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72217","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72330","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72339","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72400","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72425","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72459","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72460","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72465","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74338","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74406","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261573-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1226591","tags":["report"]},{"url":"https://bugzilla.suse.com/1243208","tags":["report"]},{"url":"https://bugzilla.suse.com/1245728","tags":["report"]},{"url":"https://bugzilla.suse.com/1251135","tags":["report"]},{"url":"https://bugzilla.suse.com/1251971","tags":["report"]},{"url":"https://bugzilla.suse.com/1252073","tags":["report"]},{"url":"https://bugzilla.suse.com/1252266","tags":["report"]},{"url":"https://bugzilla.suse.com/1252803","tags":["report"]},{"url":"https://bugzilla.suse.com/1253049","tags":["report"]},{"url":"https://bugzilla.suse.com/1253129","tags":["report"]},{"url":"https://bugzilla.suse.com/1255687","tags":["report"]},{"url":"https://bugzilla.suse.com/1256504","tags":["report"]},{"url":"https://bugzilla.suse.com/1256647","tags":["report"]},{"url":"https://bugzilla.suse.com/1256690","tags":["report"]},{"url":"https://bugzilla.suse.com/1257466","tags":["report"]},{"url":"https://bugzilla.suse.com/1257472","tags":["report"]},{"url":"https://bugzilla.suse.com/1257506","tags":["report"]},{"url":"https://bugzilla.suse.com/1257561","tags":["report"]},{"url":"https://bugzilla.suse.com/1257682","tags":["report"]},{"url":"https://bugzilla.suse.com/1257773","tags":["report"]},{"url":"https://bugzilla.suse.com/1257777","tags":["report"]},{"url":"https://bugzilla.suse.com/1258280","tags":["report"]},{"url":"https://bugzilla.suse.com/1258303","tags":["report"]},{"url":"https://bugzilla.suse.com/1258305","tags":["report"]},{"url":"https://bugzilla.suse.com/1258330","tags":["report"]},{"url":"https://bugzilla.suse.com/1258337","tags":["report"]},{"url":"https://bugzilla.suse.com/1258414","tags":["report"]},{"url":"https://bugzilla.suse.com/1258424","tags":["report"]},{"url":"https://bugzilla.suse.com/1258447","tags":["report"]},{"url":"https://bugzilla.suse.com/1258476","tags":["report"]},{"url":"https://bugzilla.suse.com/1259188","tags":["report"]},{"url":"https://bugzilla.suse.com/1259580","tags":["report"]},{"url":"https://bugzilla.suse.com/1259707","tags":["report"]},{"url":"https://bugzilla.suse.com/1259795","tags":["report"]},{"url":"https://bugzilla.suse.com/1259797","tags":["report"]},{"url":"https://bugzilla.suse.com/1259865","tags":["report"]},{"url":"https://bugzilla.suse.com/1259866","tags":["report"]},{"url":"https://bugzilla.suse.com/1259886","tags":["report"]},{"url":"https://bugzilla.suse.com/1259889","tags":["report"]},{"url":"https://bugzilla.suse.com/1259891","tags":["report"]},{"url":"https://bugzilla.suse.com/1259997","tags":["report"]},{"url":"https://bugzilla.suse.com/1259998","tags":["report"]},{"url":"https://bugzilla.suse.com/1260005","tags":["report"]},{"url":"https://bugzilla.suse.com/1260009","tags":["report"]},{"url":"https://bugzilla.suse.com/1260347","tags":["report"]},{"url":"https://bugzilla.suse.com/1260464","tags":["report"]},{"url":"https://bugzilla.suse.com/1260471","tags":["report"]},{"url":"https://bugzilla.suse.com/1260481","tags":["report"]},{"url":"https://bugzilla.suse.com/1260486","tags":["report"]},{"url":"https://bugzilla.suse.com/1260500","tags":["report"]},{"url":"https://bugzilla.suse.com/1260562","tags":["report"]},{"url":"https://bugzilla.suse.com/1260730","tags":["report"]},{"url":"https://bugzilla.suse.com/1260732","tags":["report"]},{"url":"https://bugzilla.suse.com/1260735","tags":["report"]},{"url":"https://bugzilla.suse.com/1260799","tags":["report"]},{"url":"https://bugzilla.suse.com/1261496","tags":["report"]},{"url":"https://bugzilla.suse.com/1261498","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31788","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261574-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1215492","tags":["report"]},{"url":"https://bugzilla.suse.com/1246057","tags":["report"]},{"url":"https://bugzilla.suse.com/1256675","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68818","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261606-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261643-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1253122","tags":["report"]},{"url":"https://bugzilla.suse.com/1259461","tags":["report"]},{"url":"https://bugzilla.suse.com/1261412","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23412","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261661-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621114-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1249998","tags":["report"]},{"url":"https://bugzilla.suse.com/1251186","tags":["report"]},{"url":"https://bugzilla.suse.com/1253455","tags":["report"]},{"url":"https://bugzilla.suse.com/1254306","tags":["report"]},{"url":"https://bugzilla.suse.com/1255084","tags":["report"]},{"url":"https://bugzilla.suse.com/1256645","tags":["report"]},{"url":"https://bugzilla.suse.com/1256784","tags":["report"]},{"url":"https://bugzilla.suse.com/1257183","tags":["report"]},{"url":"https://bugzilla.suse.com/1257473","tags":["report"]},{"url":"https://bugzilla.suse.com/1257732","tags":["report"]},{"url":"https://bugzilla.suse.com/1257755","tags":["report"]},{"url":"https://bugzilla.suse.com/1257814","tags":["report"]},{"url":"https://bugzilla.suse.com/1257952","tags":["report"]},{"url":"https://bugzilla.suse.com/1258286","tags":["report"]},{"url":"https://bugzilla.suse.com/1258293","tags":["report"]},{"url":"https://bugzilla.suse.com/1258338","tags":["report"]},{"url":"https://bugzilla.suse.com/1258340","tags":["report"]},{"url":"https://bugzilla.suse.com/1258376","tags":["report"]},{"url":"https://bugzilla.suse.com/1258389","tags":["report"]},{"url":"https://bugzilla.suse.com/1258524","tags":["report"]},{"url":"https://bugzilla.suse.com/1258832","tags":["report"]},{"url":"https://bugzilla.suse.com/1258849","tags":["report"]},{"url":"https://bugzilla.suse.com/1259870","tags":["report"]},{"url":"https://bugzilla.suse.com/1260497","tags":["report"]},{"url":"https://bugzilla.suse.com/1260527","tags":["report"]},{"url":"https://bugzilla.suse.com/1260544","tags":["report"]},{"url":"https://bugzilla.suse.com/1260550","tags":["report"]},{"url":"https://bugzilla.suse.com/1260580","tags":["report"]},{"url":"https://bugzilla.suse.com/1261507","tags":["report"]},{"url":"https://bugzilla.suse.com/1261669","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23419","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621123-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621255-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262134-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1259798","tags":["report"]},{"url":"https://bugzilla.suse.com/1260563","tags":["report"]},{"url":"https://bugzilla.suse.com/1260908","tags":["report"]},{"url":"https://bugzilla.suse.com/1264096","tags":["report"]},{"url":"https://bugzilla.suse.com/1265224","tags":["report"]},{"url":"https://bugzilla.suse.com/1265384","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-54518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46333","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262149-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262159-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262172-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262176-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262181-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621834-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1234634","tags":["report"]},{"url":"https://bugzilla.suse.com/1241259","tags":["report"]},{"url":"https://bugzilla.suse.com/1243603","tags":["report"]},{"url":"https://bugzilla.suse.com/1248754","tags":["report"]},{"url":"https://bugzilla.suse.com/1249104","tags":["report"]},{"url":"https://bugzilla.suse.com/1250951","tags":["report"]},{"url":"https://bugzilla.suse.com/1253471","tags":["report"]},{"url":"https://bugzilla.suse.com/1254518","tags":["report"]},{"url":"https://bugzilla.suse.com/1255160","tags":["report"]},{"url":"https://bugzilla.suse.com/1255360","tags":["report"]},{"url":"https://bugzilla.suse.com/1255459","tags":["report"]},{"url":"https://bugzilla.suse.com/1255752","tags":["report"]},{"url":"https://bugzilla.suse.com/1256288","tags":["report"]},{"url":"https://bugzilla.suse.com/1256865","tags":["report"]},{"url":"https://bugzilla.suse.com/1256867","tags":["report"]},{"url":"https://bugzilla.suse.com/1258518","tags":["report"]},{"url":"https://bugzilla.suse.com/1258718","tags":["report"]},{"url":"https://bugzilla.suse.com/1258826","tags":["report"]},{"url":"https://bugzilla.suse.com/1258850","tags":["report"]},{"url":"https://bugzilla.suse.com/1258854","tags":["report"]},{"url":"https://bugzilla.suse.com/1258855","tags":["report"]},{"url":"https://bugzilla.suse.com/1258856","tags":["report"]},{"url":"https://bugzilla.suse.com/1258857","tags":["report"]},{"url":"https://bugzilla.suse.com/1258933","tags":["report"]},{"url":"https://bugzilla.suse.com/1258961","tags":["report"]},{"url":"https://bugzilla.suse.com/1259186","tags":["report"]},{"url":"https://bugzilla.suse.com/1259199","tags":["report"]},{"url":"https://bugzilla.suse.com/1259222","tags":["report"]},{"url":"https://bugzilla.suse.com/1259420","tags":["report"]},{"url":"https://bugzilla.suse.com/1259535","tags":["report"]},{"url":"https://bugzilla.suse.com/1259672","tags":["report"]},{"url":"https://bugzilla.suse.com/1259799","tags":["report"]},{"url":"https://bugzilla.suse.com/1259806","tags":["report"]},{"url":"https://bugzilla.suse.com/1259857","tags":["report"]},{"url":"https://bugzilla.suse.com/1259868","tags":["report"]},{"url":"https://bugzilla.suse.com/1259869","tags":["report"]},{"url":"https://bugzilla.suse.com/1259871","tags":["report"]},{"url":"https://bugzilla.suse.com/1259873","tags":["report"]},{"url":"https://bugzilla.suse.com/1259878","tags":["report"]},{"url":"https://bugzilla.suse.com/1259994","tags":["report"]},{"url":"https://bugzilla.suse.com/1260010","tags":["report"]},{"url":"https://bugzilla.suse.com/1260012","tags":["report"]},{"url":"https://bugzilla.suse.com/1260018","tags":["report"]},{"url":"https://bugzilla.suse.com/1260428","tags":["report"]},{"url":"https://bugzilla.suse.com/1260468","tags":["report"]},{"url":"https://bugzilla.suse.com/1260483","tags":["report"]},{"url":"https://bugzilla.suse.com/1260484","tags":["report"]},{"url":"https://bugzilla.suse.com/1260485","tags":["report"]},{"url":"https://bugzilla.suse.com/1260489","tags":["report"]},{"url":"https://bugzilla.suse.com/1260504","tags":["report"]},{"url":"https://bugzilla.suse.com/1260505","tags":["report"]},{"url":"https://bugzilla.suse.com/1260507","tags":["report"]},{"url":"https://bugzilla.suse.com/1260514","tags":["report"]},{"url":"https://bugzilla.suse.com/1260523","tags":["report"]},{"url":"https://bugzilla.suse.com/1260526","tags":["report"]},{"url":"https://bugzilla.suse.com/1260528","tags":["report"]},{"url":"https://bugzilla.suse.com/1260529","tags":["report"]},{"url":"https://bugzilla.suse.com/1260530","tags":["report"]},{"url":"https://bugzilla.suse.com/1260531","tags":["report"]},{"url":"https://bugzilla.suse.com/1260532","tags":["report"]},{"url":"https://bugzilla.suse.com/1260533","tags":["report"]},{"url":"https://bugzilla.suse.com/1260536","tags":["report"]},{"url":"https://bugzilla.suse.com/1260537","tags":["report"]},{"url":"https://bugzilla.suse.com/1260538","tags":["report"]},{"url":"https://bugzilla.suse.com/1260541","tags":["report"]},{"url":"https://bugzilla.suse.com/1260546","tags":["report"]},{"url":"https://bugzilla.suse.com/1260549","tags":["report"]},{"url":"https://bugzilla.suse.com/1260551","tags":["report"]},{"url":"https://bugzilla.suse.com/1260552","tags":["report"]},{"url":"https://bugzilla.suse.com/1260555","tags":["report"]},{"url":"https://bugzilla.suse.com/1260561","tags":["report"]},{"url":"https://bugzilla.suse.com/1260566","tags":["report"]},{"url":"https://bugzilla.suse.com/1260571","tags":["report"]},{"url":"https://bugzilla.suse.com/1260572","tags":["report"]},{"url":"https://bugzilla.suse.com/1260573","tags":["report"]},{"url":"https://bugzilla.suse.com/1260576","tags":["report"]},{"url":"https://bugzilla.suse.com/1260581","tags":["report"]},{"url":"https://bugzilla.suse.com/1260593","tags":["report"]},{"url":"https://bugzilla.suse.com/1260613","tags":["report"]},{"url":"https://bugzilla.suse.com/1260728","tags":["report"]},{"url":"https://bugzilla.suse.com/1260729","tags":["report"]},{"url":"https://bugzilla.suse.com/1260731","tags":["report"]},{"url":"https://bugzilla.suse.com/1260798","tags":["report"]},{"url":"https://bugzilla.suse.com/1260800","tags":["report"]},{"url":"https://bugzilla.suse.com/1260801","tags":["report"]},{"url":"https://bugzilla.suse.com/1260807","tags":["report"]},{"url":"https://bugzilla.suse.com/1260811","tags":["report"]},{"url":"https://bugzilla.suse.com/1260996","tags":["report"]},{"url":"https://bugzilla.suse.com/1261020","tags":["report"]},{"url":"https://bugzilla.suse.com/1261149","tags":["report"]},{"url":"https://bugzilla.suse.com/1261287","tags":["report"]},{"url":"https://bugzilla.suse.com/1261288","tags":["report"]},{"url":"https://bugzilla.suse.com/1261295","tags":["report"]},{"url":"https://bugzilla.suse.com/1261348","tags":["report"]},{"url":"https://bugzilla.suse.com/1261410","tags":["report"]},{"url":"https://bugzilla.suse.com/1261503","tags":["report"]},{"url":"https://bugzilla.suse.com/1261504","tags":["report"]},{"url":"https://bugzilla.suse.com/1261505","tags":["report"]},{"url":"https://bugzilla.suse.com/1261550","tags":["report"]},{"url":"https://bugzilla.suse.com/1261555","tags":["report"]},{"url":"https://bugzilla.suse.com/1261581","tags":["report"]},{"url":"https://bugzilla.suse.com/1261582","tags":["report"]},{"url":"https://bugzilla.suse.com/1261584","tags":["report"]},{"url":"https://bugzilla.suse.com/1261585","tags":["report"]},{"url":"https://bugzilla.suse.com/1261592","tags":["report"]},{"url":"https://bugzilla.suse.com/1261601","tags":["report"]},{"url":"https://bugzilla.suse.com/1261602","tags":["report"]},{"url":"https://bugzilla.suse.com/1261617","tags":["report"]},{"url":"https://bugzilla.suse.com/1261618","tags":["report"]},{"url":"https://bugzilla.suse.com/1261629","tags":["report"]},{"url":"https://bugzilla.suse.com/1261632","tags":["report"]},{"url":"https://bugzilla.suse.com/1261635","tags":["report"]},{"url":"https://bugzilla.suse.com/1261636","tags":["report"]},{"url":"https://bugzilla.suse.com/1261637","tags":["report"]},{"url":"https://bugzilla.suse.com/1261638","tags":["report"]},{"url":"https://bugzilla.suse.com/1261641","tags":["report"]},{"url":"https://bugzilla.suse.com/1261644","tags":["report"]},{"url":"https://bugzilla.suse.com/1261645","tags":["report"]},{"url":"https://bugzilla.suse.com/1261648","tags":["report"]},{"url":"https://bugzilla.suse.com/1261679","tags":["report"]},{"url":"https://bugzilla.suse.com/1261685","tags":["report"]},{"url":"https://bugzilla.suse.com/1261686","tags":["report"]},{"url":"https://bugzilla.suse.com/1261687","tags":["report"]},{"url":"https://bugzilla.suse.com/1261692","tags":["report"]},{"url":"https://bugzilla.suse.com/1261694","tags":["report"]},{"url":"https://bugzilla.suse.com/1261700","tags":["report"]},{"url":"https://bugzilla.suse.com/1261702","tags":["report"]},{"url":"https://bugzilla.suse.com/1261703","tags":["report"]},{"url":"https://bugzilla.suse.com/1261707","tags":["report"]},{"url":"https://bugzilla.suse.com/1261710","tags":["report"]},{"url":"https://bugzilla.suse.com/1261713","tags":["report"]},{"url":"https://bugzilla.suse.com/1261714","tags":["report"]},{"url":"https://bugzilla.suse.com/1261719","tags":["report"]},{"url":"https://bugzilla.suse.com/1261738","tags":["report"]},{"url":"https://bugzilla.suse.com/1261750","tags":["report"]},{"url":"https://bugzilla.suse.com/1261751","tags":["report"]},{"url":"https://bugzilla.suse.com/1261752","tags":["report"]},{"url":"https://bugzilla.suse.com/1261768","tags":["report"]},{"url":"https://bugzilla.suse.com/1261778","tags":["report"]},{"url":"https://bugzilla.suse.com/1261779","tags":["report"]},{"url":"https://bugzilla.suse.com/1261780","tags":["report"]},{"url":"https://bugzilla.suse.com/1261781","tags":["report"]},{"url":"https://bugzilla.suse.com/1261786","tags":["report"]},{"url":"https://bugzilla.suse.com/1261788","tags":["report"]},{"url":"https://bugzilla.suse.com/1261789","tags":["report"]},{"url":"https://bugzilla.suse.com/1261796","tags":["report"]},{"url":"https://bugzilla.suse.com/1261797","tags":["report"]},{"url":"https://bugzilla.suse.com/1261896","tags":["report"]},{"url":"https://bugzilla.suse.com/1262019","tags":["report"]},{"url":"https://bugzilla.suse.com/1262053","tags":["report"]},{"url":"https://bugzilla.suse.com/1262054","tags":["report"]},{"url":"https://bugzilla.suse.com/1262055","tags":["report"]},{"url":"https://bugzilla.suse.com/1262061","tags":["report"]},{"url":"https://bugzilla.suse.com/1262063","tags":["report"]},{"url":"https://bugzilla.suse.com/1262074","tags":["report"]},{"url":"https://bugzilla.suse.com/1262078","tags":["report"]},{"url":"https://bugzilla.suse.com/1262086","tags":["report"]},{"url":"https://bugzilla.suse.com/1262087","tags":["report"]},{"url":"https://bugzilla.suse.com/1262099","tags":["report"]},{"url":"https://bugzilla.suse.com/1262100","tags":["report"]},{"url":"https://bugzilla.suse.com/1262101","tags":["report"]},{"url":"https://bugzilla.suse.com/1262179","tags":["report"]},{"url":"https://bugzilla.suse.com/1262181","tags":["report"]},{"url":"https://bugzilla.suse.com/1262245","tags":["report"]},{"url":"https://bugzilla.suse.com/1262250","tags":["report"]},{"url":"https://bugzilla.suse.com/1262480","tags":["report"]},{"url":"https://bugzilla.suse.com/1262601","tags":["report"]},{"url":"https://bugzilla.suse.com/1262616","tags":["report"]},{"url":"https://bugzilla.suse.com/1262617","tags":["report"]},{"url":"https://bugzilla.suse.com/1262627","tags":["report"]},{"url":"https://bugzilla.suse.com/1262662","tags":["report"]},{"url":"https://bugzilla.suse.com/1262665","tags":["report"]},{"url":"https://bugzilla.suse.com/1262671","tags":["report"]},{"url":"https://bugzilla.suse.com/1262673","tags":["report"]},{"url":"https://bugzilla.suse.com/1262709","tags":["report"]},{"url":"https://bugzilla.suse.com/1262725","tags":["report"]},{"url":"https://bugzilla.suse.com/1262731","tags":["report"]},{"url":"https://bugzilla.suse.com/1262750","tags":["report"]},{"url":"https://bugzilla.suse.com/1262752","tags":["report"]},{"url":"https://bugzilla.suse.com/1262758","tags":["report"]},{"url":"https://bugzilla.suse.com/1263001","tags":["report"]},{"url":"https://bugzilla.suse.com/1263012","tags":["report"]},{"url":"https://bugzilla.suse.com/1263018","tags":["report"]},{"url":"https://bugzilla.suse.com/1263044","tags":["report"]},{"url":"https://bugzilla.suse.com/1263048","tags":["report"]},{"url":"https://bugzilla.suse.com/1263052","tags":["report"]},{"url":"https://bugzilla.suse.com/1263064","tags":["report"]},{"url":"https://bugzilla.suse.com/1263074","tags":["report"]},{"url":"https://bugzilla.suse.com/1263077","tags":["report"]},{"url":"https://bugzilla.suse.com/1263085","tags":["report"]},{"url":"https://bugzilla.suse.com/1263093","tags":["report"]},{"url":"https://bugzilla.suse.com/1263095","tags":["report"]},{"url":"https://bugzilla.suse.com/1263104","tags":["report"]},{"url":"https://bugzilla.suse.com/1263107","tags":["report"]},{"url":"https://bugzilla.suse.com/1263131","tags":["report"]},{"url":"https://bugzilla.suse.com/1263135","tags":["report"]},{"url":"https://bugzilla.suse.com/1263138","tags":["report"]},{"url":"https://bugzilla.suse.com/1263140","tags":["report"]},{"url":"https://bugzilla.suse.com/1263141","tags":["report"]},{"url":"https://bugzilla.suse.com/1263165","tags":["report"]},{"url":"https://bugzilla.suse.com/1263176","tags":["report"]},{"url":"https://bugzilla.suse.com/1263255","tags":["report"]},{"url":"https://bugzilla.suse.com/1263556","tags":["report"]},{"url":"https://bugzilla.suse.com/1263562","tags":["report"]},{"url":"https://bugzilla.suse.com/1263582","tags":["report"]},{"url":"https://bugzilla.suse.com/1263592","tags":["report"]},{"url":"https://bugzilla.suse.com/1263593","tags":["report"]},{"url":"https://bugzilla.suse.com/1263595","tags":["report"]},{"url":"https://bugzilla.suse.com/1263596","tags":["report"]},{"url":"https://bugzilla.suse.com/1263604","tags":["report"]},{"url":"https://bugzilla.suse.com/1263668","tags":["report"]},{"url":"https://bugzilla.suse.com/1263815","tags":["report"]},{"url":"https://bugzilla.suse.com/1263882","tags":["report"]},{"url":"https://bugzilla.suse.com/1263901","tags":["report"]},{"url":"https://bugzilla.suse.com/1263931","tags":["report"]},{"url":"https://bugzilla.suse.com/1263933","tags":["report"]},{"url":"https://bugzilla.suse.com/1263942","tags":["report"]},{"url":"https://bugzilla.suse.com/1263995","tags":["report"]},{"url":"https://bugzilla.suse.com/1264014","tags":["report"]},{"url":"https://bugzilla.suse.com/1264059","tags":["report"]},{"url":"https://bugzilla.suse.com/1264082","tags":["report"]},{"url":"https://bugzilla.suse.com/1264097","tags":["report"]},{"url":"https://bugzilla.suse.com/1264183","tags":["report"]},{"url":"https://bugzilla.suse.com/1264233","tags":["report"]},{"url":"https://bugzilla.suse.com/1264427","tags":["report"]},{"url":"https://bugzilla.suse.com/1264469","tags":["report"]},{"url":"https://bugzilla.suse.com/1264586","tags":["report"]},{"url":"https://bugzilla.suse.com/1264674","tags":["report"]},{"url":"https://bugzilla.suse.com/1264837","tags":["report"]},{"url":"https://bugzilla.suse.com/1264848","tags":["report"]},{"url":"https://bugzilla.suse.com/1265085","tags":["report"]},{"url":"https://bugzilla.suse.com/1265116","tags":["report"]},{"url":"https://bugzilla.suse.com/1265119","tags":["report"]},{"url":"https://bugzilla.suse.com/1265144","tags":["report"]},{"url":"https://bugzilla.suse.com/1265308","tags":["report"]},{"url":"https://bugzilla.suse.com/1265421","tags":["report"]},{"url":"https://bugzilla.suse.com/1265449","tags":["report"]},{"url":"https://bugzilla.suse.com/1265456","tags":["report"]},{"url":"https://bugzilla.suse.com/1265626","tags":["report"]},{"url":"https://bugzilla.suse.com/1265846","tags":["report"]},{"url":"https://bugzilla.suse.com/1265960","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-14027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43503","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621841-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621845-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621860-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621886-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621887-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621888-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621889-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621890-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621891-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621892-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621893-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621896-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621900-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621901-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621902-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621903-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621904-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621905-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621906-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621907-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621910-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621921-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621922-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621923-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621924-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621925-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621926-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621927-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621928-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621929-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621932-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621933-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621934-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621935-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621936-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621937-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621938-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621939-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621942-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621958-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621959-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621960-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621962-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621963-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621969-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621970-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621972-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621979-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621982-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621983-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262199-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622030-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622031-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622033-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622038-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622039-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622040-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202622042-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-23317","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23317","tags":["report"]},{"url":"https://git.kernel.org/linus/5023ca80f9589295cb60735016e39fc5cc714243","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-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-31689","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"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23317","title":"drm/vmwgfx: Return the correct value in vmw_translate_ptr functions","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T10:27:11.884Z","modified":"2026-10-19T18:35:41.612Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-457"],"updated_at":"2026-11-02T13:42:15.603999Z"}],"euvd":[{"id":"EUVD-2026-15264","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T10:27:11Z","modified":"2026-10-19T18:35:41Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T16:59:49.594293Z"}],"ghsa":[{"id":"GHSA-x2vc-23cg-h9h7","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T12:30:22Z","modified":"2026-10-19T21:33:33Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-457","CWE-908"],"updated_at":"2026-11-02T15:13:58.795037Z"}],"nvd":[{"id":"CVE-2026-23317","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T11:16:28.22Z","modified":"2026-10-19T19:17:45.5Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-908","CWE-457"],"updated_at":"2026-11-02T14:12:11.077116Z"}],"osv":[{"id":"BELL-CVE-2026-23317","status":"published","published":"2026-03-26T06:08:23.977216Z","modified":"2026-06-25T07:18:34.571400427Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:23.315185Z"},{"id":"CVE-2026-23317","title":"drm/vmwgfx: Return the correct value in vmw_translate_ptr functions","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T10:27:11.884Z","modified":"2026-10-28T02:30:50.587032542Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:58.749922Z"},{"id":"DEBIAN-CVE-2026-23317","description":"In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: Return the correct value in vmw_translate_ptr functions  Before the referenced fixes these functions used a lookup function that returned a pointer. This was changed to another lookup function that returned an error code with the pointer becoming an out parameter.  The error path when the lookup failed was not changed to reflect this change and the code continued to return the PTR_ERR of the now uninitialized pointer. This could cause the vmw_translate_ptr functions to return success when they actually failed causing further uninitialized and OOB accesses.","status":"published","published":"2026-03-25T11:16:28.22Z","modified":"2026-10-23T18:05:35.913528325Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:53.516942Z"},{"id":"OESA-2026-2311","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\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Defer sub-object cleanup in export put callbacks\n\nsvc_export_put() calls path_put() and auth_domain_put() immediately\nwhen the last reference drops, before the RCU grace period. RCU\nreaders in e_show() and c_show() access both ex_path (via\nseq_path/d_path) and ex_client-\u0026gt;name (via seq_escape) without\nholding a reference. If cache_clean removes the entry and drops the\nlast reference concurrently, the sub-objects are freed while still\nin use, producing a NULL pointer dereference in d_path.\n\nCommit 2530766492ec (\u0026quot;nfsd: fix UAF when access ex_uuid or\nex_stats\u0026quot;) moved kfree of ex_uuid and ex_stats into the\ncall_rcu callback, but left path_put() and auth_domain_put() running\nbefore the grace period because both may sleep and call_rcu\ncallbacks execute in softirq context.\n\nReplace call_rcu/kfree_rcu with queue_rcu_work(), which defers the\ncallback until after the RCU grace period and executes it in process\ncontext where sleeping is permitted. This allows path_put() and\nauth_domain_put() to be moved into the deferred callback alongside\nthe other resource releases. Apply the same fix to expkey_put(),\nwhich has the identical pattern with ek_path and ek_client.\n\nA dedicated workqueue scopes the shutdown drain to only NFSD\nexport release work items; flushing the shared\nsystem_unbound_wq would stall on unrelated work from other\nsubsystems. nfsd_export_shutdown() uses rcu_barrier() followed\nby flush_workqueue() to ensure all deferred release callbacks\ncomplete before the export caches are destroyed.\n\nReviwed-by: Jeff Layton \u0026lt;(CVE-2026-31404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix use-after-free in bond_xmit_broadcast()\n\nbond_xmit_broadcast() reuses the original skb for the last slave\n(determined by bond_is_last_slave()) and clones it for others.\nConcurrent slave enslave/release can mutate the slave list during\nRCU-protected iteration, changing which slave is \u0026quot;last\u0026quot; mid-loop.\nThis causes the original skb to be double-consumed (double-freed).\n\nReplace the racy bond_is_last_slave() check with a simple index\ncomparison (i + 1 == slaves_count) against the pre-snapshot slave\ncount taken via READ_ONCE() before the loop.  This preserves the\nzero-copy optimization for the last slave while making the \u0026quot;last\u0026quot;\ndetermination stable against concurrent list mutations.\n\nThe UAF can trigger the following crash:\n\n==================================================================\nBUG: KASAN: slab-use-after-free in skb_clone\nRead of size 8 at addr ffff888100ef8d40 by task exploit/147\n\nCPU: 1 UID: 0 PID: 147 Comm: exploit Not tainted 7.0.0-rc3+ #4 PREEMPTLAZY\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl (lib/dump_stack.c:123)\n print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n kasan_report (mm/kasan/report.c:597)\n skb_clone (include/linux/skbuff.h:1724 include/linux/skbuff.h:1792 include/linux/skbuff.h:3396 net/core/skbuff.c:2108)\n bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5334)\n bond_start_xmit (drivers/net/bonding/bond_main.c:5567 drivers/net/bonding/bond_main.c:5593)\n dev_hard_start_xmit (include/linux/netdevice.h:5325 include/linux/netdevice.h:5334 net/core/dev.c:3871 net/core/dev.c:3887)\n __dev_queue_xmit (include/linux/netdevice.h:3601 net/core/dev.c:4838)\n ip6_finish_output2 (include/net/neighbour.h:540 include/net/neighbour.h:554 net/ipv6/ip6_output.c:136)\n ip6_finish_output (net/ipv6/ip6_output.c:208 net/ipv6/ip6_output.c:219)\n ip6_output (net/ipv6/ip6_output.c:250)\n ip6_send_skb (net/ipv6/ip6_output.c:1985)\n udp_v6_send_skb (net/ipv6/udp.c:1442)\n udpv6_sendmsg (net/ipv6/udp.c:1733)\n __sys_sendto (net/socket.c:730 net/socket.c:742 net/socket.c:2206)\n __x64_sys_sendto (net/socket.c:2209)\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\nAllocated by task 147:\n\nFreed by task 147:\n\nThe buggy address belongs to the object at ffff888100ef8c80\n which belongs to the cache skbuff_head_cache of size 224\nThe buggy address is located 192 bytes inside of\n freed 224-byte region [ffff888100ef8c80, ffff888100ef8d60)\n\nMemory state around the buggy address:\n ffff888100ef8c00: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc\n ffff888100ef8c80: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n\u0026gt;ffff888100ef8d00: fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc\n                                                    ^\n ffff888100ef8d80: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb\n ffff888100ef8e00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n==================================================================(CVE-2026-31419)\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\next4: avoid infinite loops caused by residual data\n\nOn the mkdir/mknod path, when mapping logical blocks to physical blocks,\nif inserting a new extent into the extent tree fails (in this example,\nbecause the file system disabled the huge file feature when marking the\ninode as dirty), ext4_ext_map_blocks() only calls ext4_free_blocks() to\nreclaim the physical block without deleting the corresponding data in\nthe extent tree. This causes subsequent mkdir operations to reference\nthe previously reclaimed physical block number again, even though this\nphysical block is already being used by the xattr block. Therefore, a\nsituation arises where both the directory and xattr are using the same\nbuffer head block in memory simultaneously.\n\nThe above causes ext4_xattr_block_set() to enter an infinite loop about\n\u0026quot;inserted\u0026quot; and cannot release the inode lock, ultimately leading to the\n143s blocking problem mentioned in [1].\n\nIf the metadata is corrupted, then trying to remove some extent space\ncan do even more harm. Also in case EXT4_GET_BLOCKS_DELALLOC_RESERVE\nwas passed, remove space wrongly update quota information.\nJan Kara suggests distinguishing between two cases:\n\n1) The error is ENOSPC or EDQUOT - in this case the filesystem is fully\nconsistent and we must maintain its consistency including all the\naccounting. However these errors can happen only early before we\u0026apos;ve\ninserted the extent into the extent tree. So current code works correctly\nfor this case.\n\n2) Some other error - this means metadata is corrupted. We should strive to\ndo as few modifications as possible to limit damage. So I\u0026apos;d just skip\nfreeing of allocated blocks.\n\n[1]\nINFO: task syz.0.17:5995 blocked for more than 143 seconds.\nCall Trace:\n inode_lock_nested include/linux/fs.h:1073 [inline]\n __start_dirop fs/namei.c:2923 [inline]\n start_dirop fs/namei.c:2934 [inline](CVE-2026-31448)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: do not expire session on binding failure\n\nWhen a multichannel session binding request fails (e.g. wrong password),\nthe error path unconditionally sets sess-\u0026gt;state = SMB2_SESSION_EXPIRED.\nHowever, during binding, sess points to the target session looked up via\nksmbd_session_lookup_slowpath() -- which belongs to another connection\u0026apos;s\nuser. This allows a remote attacker to invalidate any active session by\nsimply sending a binding request with a wrong password (DoS).\n\nFix this by skipping session expiration when the failed request was\na binding attempt, since the session does not belong to the current\nconnection. The reference taken by ksmbd_session_lookup_slowpath() is\nstill correctly released via ksmbd_user_session_put().(CVE-2026-31476)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix fanout UAF in packet_release() via NETDEV_UP race\n\n`packet_release()` has a race window where `NETDEV_UP` can re-register a\nsocket into a fanout group\u0026apos;s `arr[]` array. The re-registration is not\ncleaned up by `fanout_release()`, leaving a dangling pointer in the fanout\narray.\n`packet_release()` does NOT zero `po-\u0026gt;num` in its `bind_lock` section.\nAfter releasing `bind_lock`, `po-\u0026gt;num` is still non-zero and `po-\u0026gt;ifindex`\nstill matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`\nthat already found the socket in `sklist` can re-register the hook.\nFor fanout sockets, this re-registration calls `__fanout_link(sk, po)`\nwhich adds the socket back into `f-\u0026gt;arr[]` and increments `f-\u0026gt;num_members`,\nbut does NOT increment `f-\u0026gt;sk_ref`.\n\nThe fix sets `po-\u0026gt;num` to zero in `packet_release` while `bind_lock` is\nheld to prevent NETDEV_UP from linking, preventing the race window.\n\nThis bug was found following an additional audit with Claude Code based\non CVE-2025-38617.(CVE-2026-31504)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_key: validate families in pfkey_send_migrate()\n\nsyzbot was able to trigger a crash in skb_put() [1]\n\nIssue is that pfkey_send_migrate() does not check old/new families,\nand that set_ipsecrequest() @family argument was truncated,\nthus possibly overfilling the skb.\n\nValidate families early, do not wait set_ipsecrequest().\n\n[1]\n\nskbuff: skb_over_panic: text:ffffffff8a752120 len:392 put:16 head:ffff88802a4ad040 data:ffff88802a4ad040 tail:0x188 end:0x180 dev:\u0026lt;NULL\u0026gt;\n kernel BUG at net/core/skbuff.c:214 !\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_over_panic net/core/skbuff.c:219 [inline]\n  skb_put+0x159/0x210 net/core/skbuff.c:2655\n  skb_put_zero include/linux/skbuff.h:2788 [inline]\n  set_ipsecrequest net/key/af_key.c:3532 [inline]\n  pfkey_send_migrate+0x1270/0x2e50 net/key/af_key.c:3636\n  km_migrate+0x155/0x260 net/xfrm/xfrm_state.c:2848\n  xfrm_migrate+0x2140/0x2450 net/xfrm/xfrm_policy.c:4705\n  xfrm_do_migrate+0x8ff/0xaa0 net/xfrm/xfrm_user.c:3150(CVE-2026-31515)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmodule: Fix kernel panic when a symbol st_shndx is out of bounds\n\nThe module loader doesn\u0026apos;t check for bounds of the ELF section index in\nsimplify_symbols():\n\n       for (i = 1; i \u0026lt; symsec-\u0026gt;sh_size / sizeof(Elf_Sym); i++) {\n\t\tconst char *name = info-\u0026gt;strtab + sym[i].st_name;\n\n\t\tswitch (sym[i].st_shndx) {\n\t\tcase SHN_COMMON:\n\n\t\t[...]\n\n\t\tdefault:\n\t\t\t/* Divert to percpu allocation if a percpu var. */\n\t\t\tif (sym[i].st_shndx == info-\u0026gt;index.pcpu)\n\t\t\t\tsecbase = (unsigned long)mod_percpu(mod);\n\t\t\telse\n  /** HERE --\u0026gt; **/\t\tsecbase = info-\u0026gt;sechdrs[sym[i].st_shndx].sh_addr;\n\t\t\tsym[i].st_value += secbase;\n\t\t\tbreak;\n\t\t}\n\t}\n\nA symbol with an out-of-bounds st_shndx value, for example 0xffff\n(known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:\n\n  BUG: unable to handle page fault for address: ...\n  RIP: 0010:simplify_symbols+0x2b2/0x480\n  ...\n  Kernel panic - not syncing: Fatal exception\n\nThis can happen when module ELF is legitimately using SHN_XINDEX or\nwhen it is corrupted.\n\nAdd a bounds check in simplify_symbols() to validate that st_shndx is\nwithin the valid range before using it.\n\nThis issue was discovered due to a bug in llvm-objcopy, see relevant\ndiscussion for details [1].\n\n[1] https://lore.kernel.org/linux-modules/(CVE-2026-31521)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: ensure we\u0026apos;re polling a polled queue\n\nA user can change the polled queue count at run time. There\u0026apos;s a brief\nwindow during a reset where a hipri task may try to poll that queue\nbefore the block layer has updated the queue maps, which would race with\nthe now interrupt driven queue and may cause double completions.(CVE-2026-31523)\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\nspi: spi-dw-dma: fix print error log when wait finish transaction\n\nIf an error occurs, the device may not have a current message. In this\ncase, the system will crash.\n\nIn this case, it\u0026apos;s better to use dev from the struct ctlr (struct spi_controller*).(CVE-2026-31560)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u0026gt;lock\n\nTake and hold kvm-\u0026gt;lock for before checking sev_guest() in\nsev_mem_enc_register_region(), as sev_guest() isn\u0026apos;t stable unless kvm-\u0026gt;lock\nis held (or KVM can guarantee KVM_SEV_INIT{2} has completed and can\u0026apos;t\nrollack state).  If KVM_SEV_INIT{2} fails, KVM can end up trying to add to\na not-yet-initialized sev-\u0026gt;regions_list, e.g. triggering a #GP\n\n  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI\n  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n  CPU: 110 UID: 0 PID: 72717 Comm: syz.15.11462 Tainted: G     U  W  O        6.16.0-smp-DEV #1 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024\n  RIP: 0010:sev_mem_enc_register_region+0x3f0/0x4f0 ../include/linux/list.h:83\n  Code: \u0026lt;41\u0026gt; 80 3c 04 00 74 08 4c 89 ff e8 f1 c7 a2 00 49 39 ed 0f 84 c6 00\n  RSP: 0018:ffff88838647fbb8 EFLAGS: 00010256\n  RAX: dffffc0000000000 RBX: 1ffff92015cf1e0b RCX: dffffc0000000000\n  RDX: 0000000000000000 RSI: 0000000000001000 RDI: ffff888367870000\n  RBP: ffffc900ae78f050 R08: ffffea000d9e0007 R09: 1ffffd4001b3c000\n  R10: dffffc0000000000 R11: fffff94001b3c001 R12: 0000000000000000\n  R13: ffff8982ab0bde00 R14: ffffc900ae78f058 R15: 0000000000000000\n  FS:  00007f34e9dc66c0(0000) GS:ffff89ee64d33000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007fe180adef98 CR3: 000000047210e000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kvm_arch_vm_ioctl+0xa72/0x1240 ../arch/x86/kvm/x86.c:7371\n   kvm_vm_ioctl+0x649/0x990 ../virt/kvm/kvm_main.c:5363\n   __se_sys_ioctl+0x101/0x170 ../fs/ioctl.c:51\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x6f/0x1f0 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f34e9f7e9a9\n  Code: \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007f34e9dc6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007f34ea1a6080 RCX: 00007f34e9f7e9a9\n  RDX: 0000200000000280 RSI: 000000008010aebb RDI: 0000000000000007\n  RBP: 00007f34ea000d69 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\n  R13: 0000000000000000 R14: 00007f34ea1a6080 R15: 00007ffce77197a8\n   \u0026lt;/TASK\u0026gt;\n\nwith a syzlang reproducer that looks like:\n\n  syz_kvm_add_vcpu$x86(0x0, \u0026amp;(0x7f0000000040)={0x0, \u0026amp;(0x7f0000000180)=ANY=[], 0x70}) (async)\n  syz_kvm_add_vcpu$x86(0x0, \u0026amp;(0x7f0000000080)={0x0, \u0026amp;(0x7f0000000180)=ANY=[@ANYBLOB=\u0026quot;...\u0026quot;], 0x4f}) (async)\n  r0 = openat$kvm(0xffffffffffffff9c, \u0026amp;(0x7f0000000200), 0x0, 0x0)\n  r1 = ioctl$KVM_CREATE_VM(r0, 0xae01, 0x0)\n  r2 = openat$kvm(0xffffffffffffff9c, \u0026amp;(0x7f0000000240), 0x0, 0x0)\n  r3 = ioctl$KVM_CREATE_VM(r2, 0xae01, 0x0)\n  ioctl$KVM_SET_CLOCK(r3, 0xc008aeba, \u0026amp;(0x7f0000000040)={0x1, 0x8, 0x0, 0x5625e9b0}) (async)\n  ioctl$KVM_SET_PIT2(r3, 0x8010aebb, \u0026amp;(0x7f0000000280)={[...], 0x5}) (async)\n  ioctl$KVM_SET_PIT2(r1, 0x4070aea0, 0x0) (async)\n  r4 = ioctl$KVM_CREATE_VM(0xffffffffffffffff, 0xae01, 0x0)\n  openat$kvm(0xffffffffffffff9c, 0x0, 0x0, 0x0) (async)\n  ioctl$KVM_SET_USER_MEMORY_REGION(r4, 0x4020ae46, \u0026amp;(0x7f0000000400)={0x0, 0x0, 0x0, 0x2000, \u0026amp;(0x7f0000001000/0x2000)=nil}) (async)\n  r5 = ioctl$KVM_CREATE_VCPU(r4, 0xae41, 0x2)\n  close(r0) (async)\n  openat$kvm(0xffffffffffffff9c, \u0026amp;(0x7f0000000000), 0x8000, 0x0) (async)\n  ioctl$KVM_SET_GUEST_DEBUG(r5, 0x4048ae9b, \u0026amp;(0x7f0000000300)={0x4376ea830d46549b, 0x0, [0x46, 0x0, 0x0, 0x0, 0x0, 0x1000]}) (async)\n  ioctl$KVM_RUN(r5, 0xae80, 0x0)\n\nOpportunistically use guard() to avoid having to define a new error label\nand goto usage.(CVE-2026-31592)\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\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\naf_unix: read UNIX_DIAG_VFS data under unix_state_lock\n\nExact UNIX diag lookups hold a reference to the socket, but not to\nu-\u0026gt;path. Meanwhile, unix_release_sock() clears u-\u0026gt;path under\nunix_state_lock() and drops the path reference after unlocking.\n\nRead the inode and device numbers for UNIX_DIAG_VFS while holding\nunix_state_lock(), then emit the netlink attribute after dropping the\nlock.\n\nThis keeps the VFS data stable while the reply is being built.(CVE-2026-31673)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check()\n\nReject rt match rules whose addrnr exceeds IP6T_RT_HOPS.\n\nrt_mt6() expects addrnr to stay within the bounds of rtinfo-\u0026gt;addrs[].\nValidate addrnr during rule installation so malformed rules are rejected\nbefore the match logic can use an out-of-range value.(CVE-2026-31674)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: validate MPLS set/set_masked payload length\n\nvalidate_set() accepted OVS_KEY_ATTR_MPLS as variable-sized payload for\nSET/SET_MASKED actions. In action handling, OVS expects fixed-size\nMPLS key data (struct ovs_key_mpls).\n\nUse the already normalized key_len (masked case included) and reject\nnon-matching MPLS action key sizes.\n\nReject invalid MPLS action payload lengths early.(CVE-2026-31679)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: br_nd_send: linearize skb before parsing ND options\n\nbr_nd_send() parses neighbour discovery options from ns-\u0026gt;opt[] and\nassumes that these options are in the linear part of request.\n\nIts callers only guarantee that the ICMPv6 header and target address\nare available, so the option area can still be non-linear. Parsing\nns-\u0026gt;opt[] in that case can access data past the linear buffer.\n\nLinearize request before option parsing and derive ns from the linear\nnetwork header.(CVE-2026-31682)\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\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\nxen/privcmd: fix double free via VMA splitting\n\nprivcmd_vm_ops defines .close (privcmd_close), but neither .may_split\nnor .open. When userspace does a partial munmap() on a privcmd mapping,\nthe kernel splits the VMA via __split_vma(). Since may_split is NULL,\nthe split is allowed. vm_area_dup() copies vm_private_data (a pages\narray allocated in alloc_empty_pages()) into the new VMA without any\nfixup, because there is no .open callback.\n\nBoth VMAs now point to the same pages array. When the unmapped portion\nis closed, privcmd_close() calls:\n    - xen_unmap_domain_gfn_range()\n    - xen_free_unpopulated_pages()\n    - kvfree(pages)\n\nThe surviving VMA still holds the dangling pointer. When it is later\ndestroyed, the same sequence runs again, which leads to a double free.\n\nFix this issue by adding a .may_split callback denying the VMA split.\n\nThis is XSA-487 / CVE-2026-31787(CVE-2026-31787)\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\nHID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure\n\nPresently, if the force feedback initialisation fails when probing the\nLogitech G920 Driving Force Racing Wheel for Xbox One, an error number\nwill be returned and propagated before the userspace infrastructure\n(sysfs and /dev/input) has been torn down.  If userspace ignores the\nerrors and continues to use its references to these dangling entities, a\nUAF will promptly follow.\n\nWe have 2 options; continue to return the error, but ensure that all of\nthe infrastructure is torn down accordingly or continue to treat this\ncondition as a warning by emitting the message but returning success.\nIt is thought that the original author\u0026apos;s intention was to emit the\nwarning but keep the device functional, less the force feedback feature,\nso let\u0026apos;s go with that.(CVE-2026-43049)\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\npstore: ram_core: fix incorrect success return when vmap() fails\n\nIn persistent_ram_vmap(), vmap() may return NULL on failure.\n\nIf offset is non-zero, adding offset_in_page(start) causes the function\nto return a non-NULL pointer even though the mapping failed.\npersistent_ram_buffer_map() therefore incorrectly returns success.\n\nSubsequent access to prz-\u0026gt;buffer may dereference an invalid address\nand cause crashes.\n\nAdd proper NULL checking for vmap() failures.(CVE-2026-43124)\n\nIn the Linux kernel xfrm/ESP (IPsec) subsystem, when appending pipe pages to network packets (skb) via zero-copy mechanisms such as splice() / MSG_SPLICE_PAGES, IPv4/IPv6 datagram paths are not correctly marked with the SKBFL_SHARED_FRAG flag. The ESP receive path incorrectly treats these externally owned shared pages as private data, skipping the COW (copy-on-write) step and performing in-place decryption directly, allowing an attacker to pollute otherwise read-only pages in the page cache. Combined with CVE-2026-43500, a complete exploit chain can be formed, allowing local unprivileged users to obtain root privileges. This vulnerability affects almost all Linux distributions since 2017 (kernel ~ 4.10), including Ubuntu, RHEL, AlmaLinux, Debian, Fedora, etc. A public PoC has been released and signs of active exploitation have been observed.(CVE-2026-43284)","status":"published","published":"2026-05-15T11:11:16Z","modified":"2026-08-18T01:19:53.815507371Z","cvss":[{"version":"3.1","score":9.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"OESA-2026-2418","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:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400Call Trace: \u0026lt;TASK\u0026gt; kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.(CVE-2024-56760)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: fix nfs_release_folio() to not deadlock via kcompactd writeback\n\nAdd PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so\nnfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.\n\nOtherwise NFS can deadlock waiting for kcompactd enduced writeback which\nrecurses back to NFS (which triggers writeback to NFSD via NFS loopback\nmount on the same host, NFSD blocks waiting for XFS\u0026apos;s call to\n__filemap_get_folio):\n\n6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.\n\n{---\n[58] \u0026quot;kcompactd0\u0026quot;\n[\u0026lt;0\u0026gt;] folio_wait_bit+0xe8/0x200\n[\u0026lt;0\u0026gt;] folio_wait_writeback+0x2b/0x80\n[\u0026lt;0\u0026gt;] nfs_wb_folio+0x80/0x1b0 [nfs]\n[\u0026lt;0\u0026gt;] nfs_release_folio+0x68/0x130 [nfs]\n[\u0026lt;0\u0026gt;] split_huge_page_to_list_to_order+0x362/0x840\n[\u0026lt;0\u0026gt;] migrate_pages_batch+0x43d/0xb90\n[\u0026lt;0\u0026gt;] migrate_pages_sync+0x9a/0x240\n[\u0026lt;0\u0026gt;] migrate_pages+0x93c/0x9f0\n[\u0026lt;0\u0026gt;] compact_zone+0x8e2/0x1030\n[\u0026lt;0\u0026gt;] compact_node+0xdb/0x120\n[\u0026lt;0\u0026gt;] kcompactd+0x121/0x2e0\n[\u0026lt;0\u0026gt;] kthread+0xcf/0x100\n[\u0026lt;0\u0026gt;] ret_from_fork+0x31/0x40\n[\u0026lt;0\u0026gt;] ret_from_fork_asm+0x1a/0x30\n---}\n\n[(CVE-2025-21908)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio\n\nCommit b15c87263a69 (\u0026quot;hwpoison, memory_hotplug: allow hwpoisoned pages to\nbe offlined) add page poison checks in do_migrate_range in order to make\noffline hwpoisoned page possible by introducing isolate_lru_page and\ntry_to_unmap for hwpoisoned page.  However folio lock must be held before\ncalling try_to_unmap.  Add it to fix this problem.\n\nWarning will be produced if folio is not locked during unmap:\n\n  ------------[ cut here ]------------\n  kernel BUG at ./include/linux/swapops.h:400!\n  Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G        W          6.13.0-rc1-00016-g3c434c7ee82a-dirty #41\n  Tainted: [W]=WARN\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n  pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : try_to_unmap_one+0xb08/0xd3c\n  lr : try_to_unmap_one+0x3dc/0xd3c\n  Call trace:\n   try_to_unmap_one+0xb08/0xd3c (P)\n   try_to_unmap_one+0x3dc/0xd3c (L)\n   rmap_walk_anon+0xdc/0x1f8\n   rmap_walk+0x3c/0x58\n   try_to_unmap+0x88/0x90\n   unmap_poisoned_folio+0x30/0xa8\n   do_migrate_range+0x4a0/0x568\n   offline_pages+0x5a4/0x670\n   memory_block_action+0x17c/0x374\n   memory_subsys_offline+0x3c/0x78\n   device_offline+0xa4/0xd0\n   state_store+0x8c/0xf0\n   dev_attr_store+0x18/0x2c\n   sysfs_kf_write+0x44/0x54\n   kernfs_fop_write_iter+0x118/0x1a8\n   vfs_write+0x3a8/0x4bc\n   ksys_write+0x6c/0xf8\n   __arm64_sys_write+0x1c/0x28\n   invoke_syscall+0x44/0x100\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x30/0xd0\n   el0t_64_sync_handler+0xc8/0xcc\n   el0t_64_sync+0x198/0x19c\n  Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000)\n  ---[ end trace 0000000000000000 ]---(CVE-2025-21931)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Bridge, fix the crash caused by LAG state check\n\nWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event is\ntriggered. Driver finds the lower devices (PFs) to flush all the\noffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns\nfalse if one of PF is unloaded. In such case,\nmlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of\nthe alive PF, and the flush is skipped.\n\nBesides, the bridge fdb entry\u0026apos;s lastuse is updated in mlx5 bridge\nevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be\nignored in this case because the upper interface for bond is deleted,\nand the entry will never be aged because lastuse is never updated.\n\nTo make things worse, as the entry is alive, mlx5 bridge workqueue\nkeeps sending that event, which is then handled by kernel bridge\nnotifier. It causes the following crash when accessing the passed bond\nnetdev which is already destroyed.\n\nTo fix this issue, remove such checks. LAG state is already checked in\ncommit 15f8f168952f (\u0026quot;net/mlx5: Bridge, verify LAG state when adding\nbond to bridge\u0026quot;), driver still need to skip offload if LAG becomes\ninvalid state after initialization.\n\n Oops: stack segment: 0000 [#1] SMP\n CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core]\n RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge]\n Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 \u0026lt;4c\u0026gt; 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7\n RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297\n RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff\n RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0\n RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8\n R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60\n R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000\n FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die_body+0x1a/0x60\n  ? die+0x38/0x60\n  ? do_trap+0x10b/0x120\n  ? do_error_trap+0x64/0xa0\n  ? exc_stack_segment+0x33/0x50\n  ? asm_exc_stack_segment+0x22/0x30\n  ? br_switchdev_event+0x2c/0x110 [bridge]\n  ? sched_balance_newidle.isra.149+0x248/0x390\n  notifier_call_chain+0x4b/0xa0\n  atomic_notifier_call_chain+0x16/0x20\n  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]\n  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]\n  process_scheduled_works+0x81/0x390\n  worker_thread+0x106/0x250\n  ? bh_worker+0x110/0x110\n  kthread+0xb7/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n  \u0026lt;/TASK\u0026gt;(CVE-2025-21970)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Prevent creation of classes with TC_H_ROOT\n\nThe function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination\ncondition when traversing up the qdisc tree to update parent backlog\ncounters. However, if a class is created with classid TC_H_ROOT, the\ntraversal terminates prematurely at this class instead of reaching the\nactual root qdisc, causing parent statistics to be incorrectly maintained.\nIn case of DRR, this could lead to a crash as reported by Mingi Cho.\n\nPrevent the creation of any Qdisc class with classid TC_H_ROOT\n(0xFFFFFFFF) across all qdisc types, as suggested by Jamal.(CVE-2025-21971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched: address a potential NULL pointer dereference in the GRED scheduler.\n\nIf kzalloc in gred_init returns a NULL pointer, the code follows the\nerror handling path, invoking gred_destroy. This, in turn, calls\ngred_offload, where memset could receive a NULL pointer as input,\npotentially leading to a kernel crash.\n\nWhen table-\u0026gt;opt is NULL in gred_init(), gred_change_table_def()\nis not called yet, so it is not necessary to call -\u0026gt;ndo_setup_tc()\nin gred_offload().(CVE-2025-21980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: switchdev: Convert blocking notification chain to a raw one\n\nA blocking notification chain uses a read-write semaphore to protect the\nintegrity of the chain. The semaphore is acquired for writing when\nadding / removing notifiers to / from the chain and acquired for reading\nwhen traversing the chain and informing notifiers about an event.\n\nIn case of the blocking switchdev notification chain, recursive\nnotifications are possible which leads to the semaphore being acquired\ntwice for reading and to lockdep warnings being generated [1].\n\nSpecifically, this can happen when the bridge driver processes a\nSWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications\nabout deferred events when calling switchdev_deferred_process().\n\nFix this by converting the notification chain to a raw notification\nchain in a similar fashion to the netdev notification chain. Protect\nthe chain using the RTNL mutex by acquiring it when modifying the chain.\nEvents are always informed under the RTNL mutex, but add an assertion in\ncall_switchdev_blocking_notifiers() to make sure this is not violated in\nthe future.\n\nMaintain the \u0026quot;blocking\u0026quot; prefix as events are always emitted from process\ncontext and listeners are allowed to block.\n\n[1]:\nWARNING: possible recursive locking detected\n6.14.0-rc4-custom-g079270089484 #1 Not tainted\n--------------------------------------------\nip/52731 is trying to acquire lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nbut task is already holding lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0\n----\nlock((switchdev_blocking_notif_chain).rwsem);\nlock((switchdev_blocking_notif_chain).rwsem);\n\n*** DEADLOCK ***\nMay be due to missing lock nesting notation\n3 locks held by ip/52731:\n #0: ffffffff84f795b0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x727/0x1dc0\n #1: ffffffff8731f628 (\u0026amp;net-\u0026gt;rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x790/0x1dc0\n #2: ffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nstack backtrace:\n...\n? __pfx_down_read+0x10/0x10\n? __pfx_mark_lock+0x10/0x10\n? __pfx_switchdev_port_attr_set_deferred+0x10/0x10\nblocking_notifier_call_chain+0x58/0xa0\nswitchdev_port_attr_notify.constprop.0+0xb3/0x1b0\n? __pfx_switchdev_port_attr_notify.constprop.0+0x10/0x10\n? mark_held_locks+0x94/0xe0\n? switchdev_deferred_process+0x11a/0x340\nswitchdev_port_attr_set_deferred+0x27/0xd0\nswitchdev_deferred_process+0x164/0x340\nbr_switchdev_port_unoffload+0xc8/0x100 [bridge]\nbr_switchdev_blocking_event+0x29f/0x580 [bridge]\nnotifier_call_chain+0xa2/0x440\nblocking_notifier_call_chain+0x6e/0xa0\nswitchdev_bridge_port_unoffload+0xde/0x1a0\n...(CVE-2025-21986)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix fence reference count leak\n\nThe last_scheduled fence leaks when an entity is being killed and adding\nthe cleanup callback fails.\n\nDecrement the reference count of prev when dma_fence_add_callback()\nfails, ensuring proper balance.\n\n[phasta: add git tag info for stable kernel](CVE-2025-21995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn\u0026apos;t have an integer wrapping bug.(CVE-2025-22001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: dummy: force synchronous probing\n\nSometimes I get a NULL pointer dereference at boot time in kobject_get()\nwith the following call stack:\n\nanatop_regulator_probe()\n devm_regulator_register()\n  regulator_register()\n   regulator_resolve_supply()\n    kobject_get()\n\nBy placing some extra BUG_ON() statements I could verify that this is\nraised because probing of the \u0026apos;dummy\u0026apos; regulator driver is not completed\n(\u0026apos;dummy_regulator_rdev\u0026apos; is still NULL).\n\nIn the JTAG debugger I can see that dummy_regulator_probe() and\nanatop_regulator_probe() can be run by different kernel threads\n(kworker/u4:*).  I haven\u0026apos;t further investigated whether this can be\nchanged or if there are other possibilities to force synchronization\nbetween these two probe routines.  On the other hand I don\u0026apos;t expect much\nboot time penalty by probing the \u0026apos;dummy\u0026apos; regulator synchronously.(CVE-2025-22009)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspufs: fix a leak in spufs_create_context()\n\nLeak fixes back in 2008 missed one case - if we are trying to set affinity\nand spufs_mkdir() fails, we need to drop the reference to neighbor.(CVE-2025-22071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;smb: client: fix TCP timers deadlock after rmmod\u0026quot;\n\nThis reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.\n\nCommit e9f2517a3e18 (\u0026quot;smb: client: fix TCP timers deadlock after\nrmmod\u0026quot;) is intended to fix a null-ptr-deref in LOCKDEP, which is\nmentioned as CVE-2024-54680, but is actually did not fix anything;\nThe issue can be reproduced on top of it. [0]\n\nAlso, it reverted the change by commit ef7134c7fc48 (\u0026quot;smb: client:\nFix use-after-free of network namespace.\u0026quot;) and introduced a real\nissue by reviving the kernel TCP socket.\n\nWhen a reconnect happens for a CIFS connection, the socket state\ntransitions to FIN_WAIT_1.  Then, inet_csk_clear_xmit_timers_sync()\nin tcp_close() stops all timers for the socket.\n\nIf an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1\nforever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.\n\nUsually, FIN can be retransmitted by the peer, but if the peer aborts\nthe connection, the issue comes into reality.\n\nI warned about this privately by pointing out the exact report [1],\nbut the bogus fix was finally merged.\n\nSo, we should not stop the timers to finally kill the connection on\nour side in that case, meaning we must not use a kernel socket for\nTCP whose sk-\u0026gt;sk_net_refcnt is 0.\n\nThe kernel socket does not have a reference to its netns to make it\npossible to tear down netns without cleaning up every resource in it.\n\nFor example, tunnel devices use a UDP socket internally, but we can\ndestroy netns without removing such devices and let it complete\nduring exit.  Otherwise, netns would be leaked when the last application\ndied.\n\nHowever, this is problematic for TCP sockets because TCP has timers to\nclose the connection gracefully even after the socket is close()d.  The\nlifetime of the socket and its netns is different from the lifetime of\nthe underlying connection.\n\nIf the socket user does not maintain the netns lifetime, the timer could\nbe fired after the socket is close()d and its netns is freed up, resulting\nin use-after-free.\n\nActually, we have seen so many similar issues and converted such sockets\nto have a reference to netns.\n\nThat\u0026apos;s why I converted the CIFS client socket to have a reference to\nnetns (sk-\u0026gt;sk_net_refcnt == 1), which is somehow mentioned as out-of-scope\nof CIFS and technically wrong in e9f2517a3e18, but **is in-scope and right\nfix**.\n\nRegarding the LOCKDEP issue, we can prevent the module unload by\nbumping the module refcount when switching the LOCKDDEP key in\nsock_lock_init_class_and_name(). [2]\n\nFor a while, let\u0026apos;s revert the bogus fix.\n\nNote that now we can use sk_net_refcnt_upgrade() for the socket\nconversion, but I\u0026apos;ll do so later separately to make backport easy.(CVE-2025-22077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: venus: hfi_parser: add check to avoid out of bound access\n\nThere is a possibility that init_codecs is invoked multiple times during\nmanipulated payload from video firmware. In such case, if codecs_count\ncan get incremented to value more than MAX_CODEC_NUM, there can be OOB\naccess. Reset the count so that it always starts from beginning.(CVE-2025-23157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.(CVE-2025-37740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.(CVE-2025-37748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix dangling pointer in krb_authenticate\n\nkrb_authenticate frees sess-\u0026gt;user and does not set the pointer\nto NULL. It calls ksmbd_krb5_authenticate to reinitialise\nsess-\u0026gt;user but that function may return without doing so. If\nthat happens then smb2_sess_setup, which calls krb_authenticate,\nwill be accessing free\u0026apos;d memory when it later uses sess-\u0026gt;user.(CVE-2025-37778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe()\n\ndevm_kasprintf() returns NULL when memory allocation fails. Currently,\navs_component_probe() does not check for this case, which results in a\nNULL pointer dereference.(CVE-2025-37793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsound/virtio: Fix cancel_sync warnings on uninitialized work_structs\n\nBetty reported hitting the following warning:\n\n[    8.709131][  T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182\n...\n[    8.713282][  T221] Call trace:\n[    8.713365][  T221]  __flush_work+0x8d0/0x914\n[    8.713468][  T221]  __cancel_work_sync+0xac/0xfc\n[    8.713570][  T221]  cancel_work_sync+0x24/0x34\n[    8.713667][  T221]  virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.713868][  T221]  virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.714035][  T221]  virtio_dev_probe+0x28c/0x390\n[    8.714139][  T221]  really_probe+0x1bc/0x4c8\n...\n\nIt seems we\u0026apos;re hitting the error path in virtsnd_probe(), which\ntriggers a virtsnd_remove() which iterates over the substreams\ncalling cancel_work_sync() on the elapsed_period work_struct.\n\nLooking at the code, from earlier in:\nvirtsnd_probe()-\u0026gt;virtsnd_build_devs()-\u0026gt;virtsnd_pcm_parse_cfg()\n\nWe set snd-\u0026gt;nsubstreams, allocate the snd-\u0026gt;substreams, and if\nwe then hit an error on the info allocation or something in\nvirtsnd_ctl_query_info() fails, we will exit without having\ninitialized the elapsed_period work_struct.\n\nWhen that error path unwinds we then call virtsnd_remove()\nwhich as long as the substreams array is allocated, will iterate\nthrough calling cancel_work_sync() on the uninitialized work\nstruct hitting this warning.\n\nTakashi Iwai suggested this fix, which initializes the substreams\nstructure right after allocation, so that if we hit the error\npaths we avoid trying to cleanup uninitialized data.\n\nNote: I have not yet managed to reproduce the issue myself, so\nthis patch has had limited testing.\n\nFeedback or thoughts would be appreciated!(CVE-2025-37805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where \u0026apos;generic_handle_irq\u0026apos; was\nreplaced with \u0026apos;handle_nested_irq\u0026apos;. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.(CVE-2025-37815)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy-\u0026gt;cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.(CVE-2025-37831)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: avoid NULL pointer dereference in dbg call\n\ncifs_server_dbg() implies server to be non-NULL so\nmove call under condition to avoid NULL pointer dereference.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37844)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: debugfs hang_hws skip GPU with MES\n\ndebugfs hang_hws is used by GPU reset test with HWS, for MES this crash\nthe kernel with NULL pointer access because dqm-\u0026gt;packet_mgr is not setup\nfor MES path.\n\nSkip GPU with MES for now, MES hang_hws debugfs interface will be\nsupported later.(CVE-2025-37853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d-\u0026gt;name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\u0026quot;ice: Fix some null pointer dereference issues in ice_ptp.c\u0026quot;).\n\nThis issue is found by our static analysis tool(CVE-2025-37881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Consistently treat platform_max as control value\n\nThis reverts commit 9bdd10d57a88 (\u0026quot;ASoC: ops: Shift tested values in\nsnd_soc_put_volsw() by +min\u0026quot;), and makes some additional related\nupdates.\n\nThere are two ways the platform_max could be interpreted; the maximum\nregister value, or the maximum value the control can be set to. The\npatch moved from treating the value as a control value to a register\none. When the patch was applied it was technically correct as\nsnd_soc_limit_volume() also used the register interpretation. However,\neven then most of the other usages treated platform_max as a\ncontrol value, and snd_soc_limit_volume() has since been updated to\nalso do so in commit fb9ad24485087 (\u0026quot;ASoC: ops: add correct range\ncheck for limiting volume\u0026quot;). That patch however, missed updating\nsnd_soc_put_volsw() back to the control interpretation, and fixing\nsnd_soc_info_volsw_range(). The control interpretation makes more\nsense as limiting is typically done from the machine driver, so it is\nappropriate to use the customer facing representation rather than the\ninternal codec representation. Update all the code to consistently use\nthis interpretation of platform_max.\n\nFinally, also add some comments to the soc_mixer_control struct to\nhopefully avoid further patches switching between the two approaches.(CVE-2025-37889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Balance device refcount when destroying devices\n\nUsing device_find_child() to lookup the proper SCMI device to destroy\ncauses an unbalance in device refcount, since device_find_child() calls an\nimplicit get_device(): this, in turns, inhibits the call of the provided\nrelease methods upon devices destruction.\n\nAs a consequence, one of the structures that is not freed properly upon\ndestruction is the internal struct device_private dev-\u0026gt;p populated by the\ndrivers subsystem core.\n\nKMemleak detects this situation since loading/unloding some SCMI driver\ncauses related devices to be created/destroyed without calling any\ndevice_release method.\n\nunreferenced object 0xffff00000f583800 (size 512):\n  comm \u0026quot;insmod\u0026quot;, pid 227, jiffies 4294912190\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 60 36 1d 8a 00 80 ff ff  ........`6......\n  backtrace (crc 114e2eed):\n    kmemleak_alloc+0xbc/0xd8\n    __kmalloc_cache_noprof+0x2dc/0x398\n    device_add+0x954/0x12d0\n    device_register+0x28/0x40\n    __scmi_device_create.part.0+0x1bc/0x380\n    scmi_device_create+0x2d0/0x390\n    scmi_create_protocol_devices+0x74/0xf8\n    scmi_device_request_notifier+0x1f8/0x2a8\n    notifier_call_chain+0x110/0x3b0\n    blocking_notifier_call_chain+0x70/0xb0\n    scmi_driver_register+0x350/0x7f0\n    0xffff80000a3b3038\n    do_one_initcall+0x12c/0x730\n    do_init_module+0x1dc/0x640\n    load_module+0x4b20/0x5b70\n    init_module_from_file+0xec/0x158\n\n$ ./scripts/faddr2line ./vmlinux device_add+0x954/0x12d0\ndevice_add+0x954/0x12d0:\nkmalloc_noprof at include/linux/slab.h:901\n(inlined by) kzalloc_noprof at include/linux/slab.h:1037\n(inlined by) device_private_init at drivers/base/core.c:3510\n(inlined by) device_add at drivers/base/core.c:3561\n\nBalance device refcount by issuing a put_device() on devices found via\ndevice_find_child().(CVE-2025-37905)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: avoid NULL pointer dereference in skb_dequeue()\n\nA NULL pointer dereference can occur in skb_dequeue() when processing a\nQCA firmware crash dump on WCN7851 (0489:e0f3).\n\n[ 93.672166] Bluetooth: hci0: ACL memdump size(589824)\n\n[ 93.672475] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[ 93.672517] Workqueue: hci0 hci_devcd_rx [bluetooth]\n[ 93.672598] RIP: 0010:skb_dequeue+0x50/0x80\n\nThe issue stems from handle_dump_pkt_qca() returning 0 even when a dump\npacket is successfully processed. This is because it incorrectly\nforwards the return value of hci_devcd_init() (which returns 0 on\nsuccess). As a result, the caller (btusb_recv_acl_qca() or\nbtusb_recv_evt_qca()) assumes the packet was not handled and passes it\nto hci_recv_frame(), leading to premature kfree() of the skb.\n\nLater, hci_devcd_rx() attempts to dequeue the same skb from the dump\nqueue, resulting in a NULL pointer dereference.\n\nFix this by:\n1. Making handle_dump_pkt_qca() return 0 on success and negative errno\n   on failure, consistent with kernel conventions.\n2. Splitting dump packet detection into separate functions for ACL\n   and event packets for better structure and readability.\n\nThis ensures dump packets are properly identified and consumed, avoiding\ndouble handling and preventing NULL pointer access.(CVE-2025-37918)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix deadlock\n\nThis patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock\nfunctions to the UCSI driver. ucsi_con_mutex_lock ensures the connector\nmutex is only locked if a connection is established and the partner pointer\nis valid. This resolves a deadlock scenario where\nucsi_displayport_remove_partner holds con-\u0026gt;mutex waiting for\ndp_altmode_work to complete while dp_altmode_work attempts to acquire it.(CVE-2025-37967)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Refactor remove call with idxd_cleanup() helper\n\nThe idxd_cleanup() helper cleans up perfmon, interrupts, internals and\nso on. Refactor remove call with the idxd_cleanup() helper to avoid code\nduplication. Note, this also fixes the missing put_device() for idxd\ngroups, enginces and wqs.(CVE-2025-38014)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Annotate FDB data races\n\nThe \u0026apos;used\u0026apos; and \u0026apos;updated\u0026apos; fields in the FDB entry structure can be\naccessed concurrently by multiple threads, leading to reports such as\n[1]. Can be reproduced using [2].\n\nSuppress these reports by annotating these accesses using\nREAD_ONCE() / WRITE_ONCE().\n\n[1]\nBUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit\n\nwrite to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0:\n vxlan_xmit+0xb29/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2:\n vxlan_xmit+0xadf/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nvalue changed: 0x00000000fffbac6e -\u0026gt; 0x00000000fffbac6f\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\n[2]\n #!/bin/bash\n\n set +H\n echo whitelist \u0026gt; /sys/kernel/debug/kcsan\n echo !vxlan_xmit \u0026gt; /sys/kernel/debug/kcsan\n\n ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1\n bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1\n taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;\n taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;(CVE-2025-38037)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Set dma_mask for ffa devices\n\nSet dma_mask for FFA devices, otherwise DMA allocation using the device pointer\nlead to following warning:\n\nWARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124(CVE-2025-38043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix use-after-free in cifs_fill_dirent\n\nThere is a race condition in the readdir concurrency process, which may\naccess the rsp buffer after it has been released, triggering the\nfollowing KASAN warning.\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs]\n Read of size 4 at addr ffff8880099b819c by task a.out/342975\n\n CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x53/0x70\n  print_report+0xce/0x640\n  kasan_report+0xb8/0xf0\n  cifs_fill_dirent+0xb03/0xb60 [cifs]\n  cifs_readdir+0x12cb/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f996f64b9f9\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89\n f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01\n f0 ff ff  0d f7 c3 0c 00 f7 d8 64 89 8\n RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e\n RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88\n R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 408:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  __kasan_slab_alloc+0x6e/0x70\n  kmem_cache_alloc_noprof+0x117/0x3d0\n  mempool_alloc_noprof+0xf2/0x2c0\n  cifs_buf_get+0x36/0x80 [cifs]\n  allocate_buffers+0x1d2/0x330 [cifs]\n  cifs_demultiplex_thread+0x22b/0x2690 [cifs]\n  kthread+0x394/0x720\n  ret_from_fork+0x34/0x70\n  ret_from_fork_asm+0x1a/0x30\n\n Freed by task 342979:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x37/0x50\n  kmem_cache_free+0x2b8/0x500\n  cifs_buf_release+0x3c/0x70 [cifs]\n  cifs_readdir+0x1c97/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents64+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n The buggy address belongs to the object at ffff8880099b8000\n  which belongs to the cache cifs_request of size 16588\n The buggy address is located 412 bytes inside of\n  freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8\n head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n anon flags: 0x80000000000040(head|node=0|zone=1)\n page_type: f5(slab)\n raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff\n head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n \u0026gt;ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                             ^\n  ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ==================================================================\n\nPOC is available in the link [1].\n\nThe problem triggering process is as follows:\n\nProcess 1                       Process 2\n-----------------------------------\n---truncated---(CVE-2025-38051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n\tInvalid read at addr 0x102877002, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\tInvalid write at addr 0x102877A44, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\t...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.(CVE-2025-38064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: CPPC: Fix NULL pointer dereference when nosmp is used\n\nWith nosmp in cmdline, other CPUs are not brought up, leaving\ntheir cpc_desc_ptr NULL. CPU0\u0026apos;s iteration via for_each_possible_cpu()\ndereferences these NULL pointers, causing panic.\n\nPanic backtrace:\n\n[    0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8\n...\n[    0.403255] [\u0026lt;ffffffff809a5818\u0026gt;] cppc_allow_fast_switch+0x6a/0xd4\n...\nKernel panic - not syncing: Attempted to kill init!\n\n[ rjw: New subject ](CVE-2025-38113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: add missing NULL check for gve_alloc_pending_packet() in TX DQO\n\ngve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()\ndid not check for this case before dereferencing the returned pointer.\n\nAdd a missing NULL check to prevent a potential NULL pointer\ndereference when allocation fails.\n\nThis improves robustness in low-memory scenarios.(CVE-2025-38122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: wwan: t7xx: Fix napi rx poll issue\n\nWhen driver handles the napi rx polling requests, the netdev might\nhave been released by the dellink logic triggered by the disconnect\noperation on user plane. However, in the logic of processing skb in\npolling, an invalid netdev is still being used, which causes a panic.\n\nBUG: kernel NULL pointer dereference, address: 00000000000000f1\nOops: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:dev_gro_receive+0x3a/0x620\n[...]\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die_body+0x68/0xb0\n ? page_fault_oops+0x379/0x3e0\n ? exc_page_fault+0x4f/0xa0\n ? asm_exc_page_fault+0x22/0x30\n ? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]\n ? dev_gro_receive+0x3a/0x620\n napi_gro_receive+0xad/0x170\n t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]\n t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]\n net_rx_action+0x103/0x470\n irq_exit_rcu+0x13a/0x310\n sysvec_apic_timer_interrupt+0x56/0x90\n \u0026lt;/IRQ\u0026gt;(CVE-2025-38123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: prevent deactivate active config while enabling the config\n\nWhile enable active config via cscfg_csdev_enable_active_config(),\nactive config could be deactivated via configfs\u0026apos; sysfs interface.\nThis could make UAF issue in below scenario:\n\nCPU0                                          CPU1\n(sysfs enable)                                load module\n                                              cscfg_load_config_sets()\n                                              activate config. // sysfs\n                                              (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\nlock(csdev-\u0026gt;cscfg_csdev_lock)\n// here load config activate by CPU1\nunlock(csdev-\u0026gt;cscfg_csdev_lock)\n\n                                              deactivate config // sysfs\n                                              (sys_activec_cnt == 0)\n                                              cscfg_unload_config_sets()\n                                              unload module\n\n// access to config_desc which freed\n// while unloading module.\ncscfg_csdev_enable_config\n\nTo address this, use cscfg_config_desc\u0026apos;s active_cnt as a reference count\n which will be holded when\n    - activate the config.\n    - enable the activated config.\nand put the module reference when config_active_cnt == 0.(CVE-2025-38131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: mscc: Fix memory leak when using one step timestamping\n\nFix memory leak when running one-step timestamping. When running\none-step sync timestamping, the HW is configured to insert the TX time\ninto the frame, so there is no reason to keep the skb anymore. As in\nthis case the HW will never generate an interrupt to say that the frame\nwas timestamped, then the frame will never released.\nFix this by freeing the frame in case of one-step timestamping.(CVE-2025-38148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix error flow upon firmware failure for RQ destruction\n\nUpon RQ destruction if the firmware command fails which is the\nlast resource to be destroyed some SW resources were already cleaned\nregardless of the failure.\n\nNow properly rollback the object to its original state upon such failure.\n\nIn order to avoid a use-after free in case someone tries to destroy the\nobject again, which results in the following kernel trace:\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE)\nCPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G           OE     -------  ---  6.12.0-54.el10.aarch64 #1\nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\nHardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : refcount_warn_saturate+0xf4/0x148\nlr : refcount_warn_saturate+0xf4/0x148\nsp : ffff80008b81b7e0\nx29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001\nx26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00\nx23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000\nx20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006\nx17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f\nx14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78\nx11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90\nx8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff\nx5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600\nCall trace:\n refcount_warn_saturate+0xf4/0x148\n mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib]\n mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib]\n mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib]\n ib_destroy_wq_user+0x30/0xc0 [ib_core]\n uverbs_free_wq+0x28/0x58 [ib_uverbs]\n destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs]\n uverbs_destroy_uobject+0x48/0x240 [ib_uverbs]\n __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs]\n uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs]\n ib_uverbs_close+0x2c/0x100 [ib_uverbs]\n __fput+0xd8/0x2f0\n __fput_sync+0x50/0x70\n __arm64_sys_close+0x40/0x90\n invoke_syscall.constprop.0+0x74/0xd0\n do_el0_svc+0x48/0xe8\n el0_svc+0x44/0x1d0\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x1a4/0x1a8(CVE-2025-38161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()\n\nBefore calling lan743x_ptp_io_event_clock_get(), the \u0026apos;channel\u0026apos; value\nis checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8).\nThis seems correct and aligns with the PTP interrupt status register\n(PTP_INT_STS) specifications.\n\nHowever, lan743x_ptp_io_event_clock_get() writes to ptp-\u0026gt;extts[] with\nonly LAN743X_PTP_N_EXTTS(4) elements, using channel as an index:\n\n    lan743x_ptp_io_event_clock_get(..., u8 channel,...)\n    {\n        ...\n        /* Update Local timestamp */\n        extts = \u0026amp;ptp-\u0026gt;extts[channel];\n        extts-\u0026gt;ts.tv_sec = sec;\n        ...\n    }\n\nTo avoid an out-of-bounds write and utilize all the supported GPIO\ninputs, set LAN743X_PTP_N_EXTTS to 8.\n\nDetected using the static analysis tool - Svace.(CVE-2025-38183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: sch_sfq: reject invalid perturb period\n\nGerrard Tai reported that SFQ perturb_period has no range check yet,\nand this can be used to trigger a race condition fixed in a separate patch.\n\nWe want to make sure ctl-\u0026gt;perturb_period * HZ will not overflow\nand is positive.\n\n\ntc qd add dev lo root sfq perturb -10   # negative value : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 1000000000 # too big : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 2000000 # acceptable value\ntc -s -d qd sh dev lo\nqdisc sfq 8005: root refcnt 2 limit 127p quantum 64Kb depth 127 flows 128 divisor 1024 perturb 2000000sec\n Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)\n backlog 0b 0p requeues 0(CVE-2025-38193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njffs2: check that raw node were preallocated before writing summary\n\nSyzkaller detected a kernel bug in jffs2_link_node_ref, caused by fault\ninjection in jffs2_prealloc_raw_node_refs. jffs2_sum_write_sumnode doesn\u0026apos;t\ncheck return value of jffs2_prealloc_raw_node_refs and simply lets any\nerror propagate into jffs2_sum_write_data, which eventually calls\njffs2_link_node_ref in order to link the summary to an expectedly allocated\nnode.\n\nkernel BUG at fs/jffs2/nodelist.c:592!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 31277 Comm: syz-executor.7 Not tainted 6.1.128-syzkaller-00139-ge10f83ca10a1 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:jffs2_link_node_ref+0x570/0x690 fs/jffs2/nodelist.c:592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n jffs2_sum_write_data fs/jffs2/summary.c:841 [inline]\n jffs2_sum_write_sumnode+0xd1a/0x1da0 fs/jffs2/summary.c:874\n jffs2_do_reserve_space+0xa18/0xd60 fs/jffs2/nodemgmt.c:388\n jffs2_reserve_space+0x55f/0xaa0 fs/jffs2/nodemgmt.c:197\n jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362\n jffs2_write_end+0x726/0x15d0 fs/jffs2/file.c:301\n generic_perform_write+0x314/0x5d0 mm/filemap.c:3856\n __generic_file_write_iter+0x2ae/0x4d0 mm/filemap.c:3973\n generic_file_write_iter+0xe3/0x350 mm/filemap.c:4005\n call_write_iter include/linux/fs.h:2265 [inline]\n do_iter_readv_writev+0x20f/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10c/0x170 fs/splice.c:950\n splice_direct_to_actor+0x337/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nFix this issue by checking return value of jffs2_prealloc_raw_node_refs\nbefore calling jffs2_sum_write_data.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-38194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix softlockup with mTHP swapin\n\nFollowing softlockup can be easily reproduced on my test machine with:\n\necho always \u0026gt; /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled\nswapon /dev/zram0 # zram0 is a 48G swap device\nmkdir -p /sys/fs/cgroup/memory/test\necho 1G \u0026gt; /sys/fs/cgroup/test/memory.max\necho $BASHPID \u0026gt; /sys/fs/cgroup/test/cgroup.procs\nwhile true; do\n    dd if=/dev/zero of=/tmp/test.img bs=1M count=5120\n    cat /tmp/test.img \u0026gt; /dev/null\n    rm /tmp/test.img\ndone\n\nThen after a while:\nwatchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787]\nModules linked in: zram virtiofs\nCPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G             L      6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)·\nTainted: [L]=SOFTLOCKUP\nHardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015\nRIP: 0010:mpol_shared_policy_lookup+0xd/0x70\nCode: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 \u0026lt;48\u0026gt; 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8\nRSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202\nRAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001\nRDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518\nRBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001\nR13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000\nFS:  00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n shmem_alloc_folio+0x31/0xc0\n shmem_swapin_folio+0x309/0xcf0\n ? filemap_get_entry+0x117/0x1e0\n ? xas_load+0xd/0xb0\n ? filemap_get_entry+0x101/0x1e0\n shmem_get_folio_gfp+0x2ed/0x5b0\n shmem_file_read_iter+0x7f/0x2e0\n vfs_read+0x252/0x330\n ksys_read+0x68/0xf0\n do_syscall_64+0x4c/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f03f9a46991\nCode: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec\nRSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991\nRDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003\nRBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380\nR10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000\nR13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\n\nThe reason is simple, readahead brought some order 0 folio in swap cache,\nand the swapin mTHP folio being allocated is in conflict with it, so\nswapcache_prepare fails and causes shmem_swap_alloc_folio to return\n-EEXIST, and shmem simply retries again and again causing this loop.\n\nFix it by applying a similar fix for anon mTHP swapin.\n\nThe performance change is very slight, time of swapin 10g zero folios\nwith shmem (test for 12 times):\nBefore:  2.47s\nAfter:   2.48s\n\n[(CVE-2025-38241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/group_cpus: fix NULL pointer dereference from group_cpus_evenly()\n\nWhile testing null_blk with configfs, echo 0 \u0026gt; poll_queues will trigger\nfollowing panic:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000010\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 27 UID: 0 PID: 920 Comm: bash Not tainted 6.15.0-02023-gadbdb95c8696-dirty #1238 PREEMPT(undef)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\nRIP: 0010:__bitmap_or+0x48/0x70\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __group_cpus_evenly+0x822/0x8c0\n group_cpus_evenly+0x2d9/0x490\n blk_mq_map_queues+0x1e/0x110\n null_map_queues+0xc9/0x170 [null_blk]\n blk_mq_update_queue_map+0xdb/0x160\n blk_mq_update_nr_hw_queues+0x22b/0x560\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_poll_queues_store+0xa4/0x130 [null_blk]\n configfs_write_iter+0x109/0x1d0\n vfs_write+0x26e/0x6f0\n ksys_write+0x79/0x180\n __x64_sys_write+0x1d/0x30\n x64_sys_call+0x45c4/0x45f0\n do_syscall_64+0xa5/0x240\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nRoot cause is that numgrps is set to 0, and ZERO_SIZE_PTR is returned from\nkcalloc(), and later ZERO_SIZE_PTR will be deferenced.\n\nFix the problem by checking numgrps first in group_cpus_evenly(), and\nreturn NULL directly if numgrps is zero.\n\n[(CVE-2025-38255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix NULL pointer deference on eir_get_service_data\n\nThe len parameter is considered optional so it can be NULL so it cannot\nbe used for skipping to next entry of EIR_SERVICE_DATA.(CVE-2025-38304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Verify content returned by parse_int_array()\n\nThe first element of the returned array stores its length. If it is 0,\nany manipulation beyond the element at index 0 ends with null-ptr-deref.(CVE-2025-38307)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Log an error when close_all_cached_dirs fails\n\nUnder low-memory conditions, close_all_cached_dirs() can\u0026apos;t move the\ndentries to a separate list to dput() them once the locks are dropped.\nThis will result in a \u0026quot;Dentry still in use\u0026quot; error, so add an error\nmessage that makes it clear this is what happened:\n\n[  495.281119] CIFS: VFS: \\\\otters.example.com\\share Out of memory while dropping dentries\n[  495.281595] ------------[ cut here ]------------\n[  495.281887] BUG: Dentry ffff888115531138{i=78,n=/}  still in use (2) [unmount of cifs cifs]\n[  495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0\n\nAlso, bail out of looping through all tcons as soon as a single\nallocation fails, since we\u0026apos;re already in trouble, and kmalloc() attempts\nfor subseqeuent tcons are likely to fail just like the first one did.(CVE-2025-38321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: fix acpi parse and parseext cache leaks\n\nACPICA commit 8829e70e1360c81e7a5a901b5d4f48330e021ea5\n\nI\u0026apos;m Seunghun Han, and I work for National Security Research Institute of\nSouth Korea.\n\nI have been doing a research on ACPI and found an ACPI cache leak in ACPI\nearly abort cases.\n\nBoot log of ACPI cache leak is as follows:\n[    0.352414] ACPI: Added _OSI(Module Device)\n[    0.353182] ACPI: Added _OSI(Processor Device)\n[    0.353182] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.353182] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.356028] ACPI: Unable to start the ACPI Interpreter\n[    0.356799] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.360215] kmem_cache_destroy Acpi-State: Slab cache still has objects\n[    0.360648] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #10\n[    0.361273] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.361873] Call Trace:\n[    0.362243]  ? dump_stack+0x5c/0x81\n[    0.362591]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.362944]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.363296]  ? acpi_os_delete_cache+0xa/0x10\n[    0.363646]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.364000]  ? acpi_terminate+0xa/0x14\n[    0.364000]  ? acpi_init+0x2af/0x34f\n[    0.364000]  ? __class_create+0x4c/0x80\n[    0.364000]  ? video_setup+0x7f/0x7f\n[    0.364000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.364000]  ? do_one_initcall+0x4e/0x1a0\n[    0.364000]  ? kernel_init_freeable+0x189/0x20a\n[    0.364000]  ? rest_init+0xc0/0xc0\n[    0.364000]  ? kernel_init+0xa/0x100\n[    0.364000]  ? ret_from_fork+0x25/0x30\n\nI analyzed this memory leak in detail. I found that “Acpi-State” cache and\n“Acpi-Parse” cache were merged because the size of cache objects was same\nslab cache size.\n\nI finally found “Acpi-Parse” cache and “Acpi-parse_ext” cache were leaked\nusing SLAB_NEVER_MERGE flag in kmem_cache_create() function.\n\nReal ACPI cache leak point is as follows:\n[    0.360101] ACPI: Added _OSI(Module Device)\n[    0.360101] ACPI: Added _OSI(Processor Device)\n[    0.360101] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.361043] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.364016] ACPI: Unable to start the ACPI Interpreter\n[    0.365061] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.368174] kmem_cache_destroy Acpi-Parse: Slab cache still has objects\n[    0.369332] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.371256] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.372000] Call Trace:\n[    0.372000]  ? dump_stack+0x5c/0x81\n[    0.372000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.372000]  ? acpi_ut_delete_caches+0x56/0x7b\n[    0.372000]  ? acpi_terminate+0xa/0x14\n[    0.372000]  ? acpi_init+0x2af/0x34f\n[    0.372000]  ? __class_create+0x4c/0x80\n[    0.372000]  ? video_setup+0x7f/0x7f\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? do_one_initcall+0x4e/0x1a0\n[    0.372000]  ? kernel_init_freeable+0x189/0x20a\n[    0.372000]  ? rest_init+0xc0/0xc0\n[    0.372000]  ? kernel_init+0xa/0x100\n[    0.372000]  ? ret_from_fork+0x25/0x30\n[    0.388039] kmem_cache_destroy Acpi-parse_ext: Slab cache still has objects\n[    0.389063] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.390557] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.392000] Call Trace:\n[    0.392000]  ? dump_stack+0x5c/0x81\n[    0.392000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.392000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.392000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.392000]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.392000]  ? acpi_terminate+0xa/0x14\n[    0.392000]  ? acpi_init+0x2af/0x3\n---truncated---(CVE-2025-38344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmaple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()\n\nTemporarily clear the preallocation flag when explicitly requesting\nallocations.  Pre-existing allocations are already counted against the\nrequest through mas_node_count_gfp(), but the allocations will not happen\nif the MA_STATE_PREALLOC flag is set.  This flag is meant to avoid\nre-allocating in bulk allocation mode, and to detect issues with\npreallocation calculations.\n\nThe MA_STATE_PREALLOC flag should also always be set on zero allocations\nso that detection of underflow allocations will print a WARN_ON() during\nconsumption.\n\nUser visible effect of this flaw is a WARN_ON() followed by a null pointer\ndereference when subsequent requests for larger number of nodes is\nignored, such as the vma merge retry in mmap_region() caused by drivers\naltering the vma flags (which happens in v6.6, at least)(CVE-2025-38364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_* TOCTOU\n\nTransport assignment may race with module unload. Protect new_transport\nfrom becoming a stale pointer.\n\nThis also takes care of an insecure call in vsock_use_local_transport();\nadd a lockdep assert.\n\nBUG: unable to handle page fault for address: fffffbfff8056000\nOops: Oops: 0000 [#1] SMP KASAN\nRIP: 0010:vsock_assign_transport+0x366/0x600\nCall Trace:\n vsock_connect+0x59c/0xc40\n __sys_connect+0xe8/0x100\n __x64_sys_connect+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38461)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_{g2h,h2g} TOCTOU\n\nvsock_find_cid() and vsock_dev_do_ioctl() may race with module unload.\ntransport_{g2h,h2g} may become NULL after the NULL check.\n\nIntroduce vsock_transport_local_cid() to protect from a potential\nnull-ptr-deref.\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_find_cid+0x47/0x90\nCall Trace:\n __vsock_bind+0x4b2/0x720\n vsock_bind+0x90/0xe0\n __sys_bind+0x14d/0x1e0\n __x64_sys_bind+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0\nCall Trace:\n __x64_sys_ioctl+0x12d/0x190\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38462)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in crypt_message when using async crypto\n\nThe CVE-2024-50047 fix removed asynchronous crypto handling from\ncrypt_message(), assuming all crypto operations are synchronous.\nHowever, when hardware crypto accelerators are used, this can cause\nuse-after-free crashes:\n\n  crypt_message()\n    // Allocate the creq buffer containing the req\n    creq = smb2_get_aead_req(..., \u0026amp;req);\n\n    // Async encryption returns -EINPROGRESS immediately\n    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);\n\n    // Free creq while async operation is still in progress\n    kvfree_sensitive(creq, ...);\n\nHardware crypto modules often implement async AEAD operations for\nperformance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,\nthe operation completes asynchronously. Without crypto_wait_req(),\nthe function immediately frees the request buffer, leading to crashes\nwhen the driver later accesses the freed memory.\n\nThis results in a use-after-free condition when the hardware crypto\ndriver later accesses the freed request structure, leading to kernel\ncrashes with NULL pointer dereferences.\n\nThe issue occurs because crypto_alloc_aead() with mask=0 doesn\u0026apos;t\nguarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in\nthe mask, async implementations can be selected.\n\nFix by restoring the async crypto handling:\n- DECLARE_CRYPTO_WAIT(wait) for completion tracking\n- aead_request_set_callback() for async completion notification\n- crypto_wait_req() to wait for operation completion\n\nThis ensures the request buffer isn\u0026apos;t freed until the crypto operation\ncompletes, whether synchronous or asynchronous, while preserving the\nCVE-2024-50047 fix.(CVE-2025-38488)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns\n\nWhat we want is to verify there is that clone won\u0026apos;t expose something\nhidden by a mount we wouldn\u0026apos;t be able to undo.  \u0026quot;Wouldn\u0026apos;t be able to undo\u0026quot;\nmay be a result of MNT_LOCKED on a child, but it may also come from\nlacking admin rights in the userns of the namespace mount belongs to.\n\nclone_private_mnt() checks the former, but not the latter.\n\nThere\u0026apos;s a number of rather confusing CAP_SYS_ADMIN checks in various\nuserns during the mount, especially with the new mount API; they serve\ndifferent purposes and in case of clone_private_mnt() they usually,\nbut not always end up covering the missing check mentioned above.(CVE-2025-38499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n\u0026apos;socket state prevent any additional subflow creation\u0026apos; protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field \u0026apos;allow_infinite_fallback\u0026apos; is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write.(CVE-2025-38552)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: use aead_request_free to match aead_request_alloc\n\nUse aead_request_free() instead of kfree() to properly free memory\nallocated by aead_request_alloc(). This ensures sensitive crypto data\nis zeroed before being freed.(CVE-2025-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Check governor before using governor-\u0026gt;name\n\nCommit 96ffcdf239de (\u0026quot;PM / devfreq: Remove redundant governor_name from\nstruct devfreq\u0026quot;) removes governor_name and uses governor-\u0026gt;name to replace\nit. But devfreq-\u0026gt;governor may be NULL and directly using\ndevfreq-\u0026gt;governor-\u0026gt;name may cause null pointer exception. Move the check of\ngovernor to before using governor-\u0026gt;name.(CVE-2025-38609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: fix refcount leak on table dump\n\nThere is a reference count leak in ctnetlink_dump_table():\n      if (res \u0026lt; 0) {\n                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general); // HERE\n                cb-\u0026gt;args[1] = (unsigned long)ct;\n                ...\n\nWhile its very unlikely, its possible that ct == last.\nIf this happens, then the refcount of ct was already incremented.\nThis 2nd increment is never undone.\n\nThis prevents the conntrack object from being released, which in turn\nkeeps prevents cnet-\u0026gt;count from dropping back to 0.\n\nThis will then block the netns dismantle (or conntrack rmmod) as\nnf_conntrack_cleanup_net_list() will wait forever.\n\nThis can be reproduced by running conntrack_resize.sh selftest in a loop.\nIt takes ~20 minutes for me on a preemptible kernel on average before\nI see a runaway kworker spinning in nf_conntrack_cleanup_net_list.\n\nOne fix would to change this to:\n        if (res \u0026lt; 0) {\n\t\tif (ct != last)\n\t                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general);\n\nBut this reference counting isn\u0026apos;t needed in the first place.\nWe can just store a cookie value instead.\n\nA followup patch will do the same for ctnetlink_exp_dump_table,\nit looks to me as if this has the same problem and like\nctnetlink_dump_table, we only need a \u0026apos;skip hint\u0026apos;, not the actual\nobject so we can apply the same cookie strategy there as well.(CVE-2025-38721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don\u0026apos;t know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don\u0026apos;t have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it\u0026apos;s\nzero length.(CVE-2025-39682)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: samsung: Fix UBSAN panic in samsung_clk_init()\n\nWith UBSAN_ARRAY_BOUNDS=y, I\u0026apos;m hitting the below panic due to\ndereferencing `ctx-\u0026gt;clk_data.hws` before setting\n`ctx-\u0026gt;clk_data.num = nr_clks`. Move that up to fix the crash.\n\n  UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n  \u0026lt;snip\u0026gt;\n  Call trace:\n   samsung_clk_init+0x110/0x124 (P)\n   samsung_clk_init+0x48/0x124 (L)\n   samsung_cmu_register_one+0x3c/0xa0\n   exynos_arm64_register_cmu+0x54/0x64\n   __gs101_cmu_top_of_clk_init_declare+0x28/0x60\n   ...(CVE-2025-39728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: Prevent file descriptor table allocations exceeding INT_MAX\n\nWhen sysctl_nr_open is set to a very high value (for example, 1073741816\nas set by systemd), processes attempting to use file descriptors near\nthe limit can trigger massive memory allocation attempts that exceed\nINT_MAX, resulting in a WARNING in mm/slub.c:\n\n  WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288\n\nThis happens because kvmalloc_array() and kvmalloc() check if the\nrequested size exceeds INT_MAX and emit a warning when the allocation is\nnot flagged with __GFP_NOWARN.\n\nSpecifically, when nr_open is set to 1073741816 (0x3ffffff8) and a\nprocess calls dup2(oldfd, 1073741880), the kernel attempts to allocate:\n- File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes\n- Multiple bitmaps: ~400MB\n- Total allocation size: \u0026gt; 8GB (exceeding INT_MAX = 2,147,483,647)\n\nReproducer:\n1. Set /proc/sys/fs/nr_open to 1073741816:\n   # echo 1073741816 \u0026gt; /proc/sys/fs/nr_open\n\n2. Run a program that uses a high file descriptor:\n   #include \u0026lt;unistd.h\u0026gt;\n   #include \u0026lt;sys/resource.h\u0026gt;\n\n   int main() {\n       struct rlimit rlim = {1073741824, 1073741824};\n       setrlimit(RLIMIT_NOFILE, \u0026amp;rlim);\n       dup2(2, 1073741880);  // Triggers the warning\n       return 0;\n   }\n\n3. Observe WARNING in dmesg at mm/slub.c:5027\n\nsystemd commit a8b627a introduced automatic bumping of fs.nr_open to the\nmaximum possible value. The rationale was that systems with memory\ncontrol groups (memcg) no longer need separate file descriptor limits\nsince memory is properly accounted. However, this change overlooked\nthat:\n\n1. The kernel\u0026apos;s allocation functions still enforce INT_MAX as a maximum\n   size regardless of memcg accounting\n2. Programs and tests that legitimately test file descriptor limits can\n   inadvertently trigger massive allocations\n3. The resulting allocations (\u0026gt;8GB) are impractical and will always fail\n\nsystemd\u0026apos;s algorithm starts with INT_MAX and keeps halving the value\nuntil the kernel accepts it. On most systems, this results in nr_open\nbeing set to 1073741816 (0x3ffffff8), which is just under 1GB of file\ndescriptors.\n\nWhile processes rarely use file descriptors near this limit in normal\noperation, certain selftests (like\ntools/testing/selftests/core/unshare_test.c) and programs that test file\ndescriptor limits can trigger this issue.\n\nFix this by adding a check in alloc_fdtable() to ensure the requested\nallocation size does not exceed INT_MAX. This causes the operation to\nfail with -EMFILE instead of triggering a kernel warning and avoids the\nimpractical \u0026gt;8GB memory allocation request.(CVE-2025-39756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM\n\nWhen performing Generic Segmentation Offload (GSO) on an IPv6 packet that\ncontains extension headers, the kernel incorrectly requests checksum offload\nif the egress device only advertises NETIF_F_IPV6_CSUM feature, which has\na strict contract: it supports checksum offload only for plain TCP or UDP\nover IPv6 and explicitly does not support packets with extension headers.\nThe current GSO logic violates this contract by failing to disable the feature\nfor packets with extension headers, such as those used in GREoIPv6 tunnels.\n\nThis violation results in the device being asked to perform an operation\nit cannot support, leading to a `skb_warn_bad_offload` warning and a collapse\nof network throughput. While device TSO/USO is correctly bypassed in favor\nof software GSO for these packets, the GSO stack must be explicitly told not\nto request checksum offload.\n\nMask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4\nin gso_features_check if the IPv6 header contains extension headers to compute\nchecksum in software.\n\nThe exception is a BIG TCP extension, which, as stated in commit\n68e068cabd2c6c53 (\u0026quot;net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\u0026quot;):\n\u0026quot;The feature is only enabled on devices that support BIG TCP TSO.\nThe header is only present for PF_PACKET taps like tcpdump,\nand not transmitted by physical devices.\u0026quot;\n\nkernel log output (truncated):\nWARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_checksum_help+0x12a/0x1f0\n validate_xmit_skb+0x1a3/0x2d0\n validate_xmit_skb_list+0x4f/0x80\n sch_direct_xmit+0x1a2/0x380\n __dev_xmit_skb+0x242/0x670\n __dev_queue_xmit+0x3fc/0x7f0\n ip6_finish_output2+0x25e/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]\n ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]\n dev_hard_start_xmit+0x63/0x1c0\n __dev_queue_xmit+0x6d0/0x7f0\n ip6_finish_output2+0x214/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n inet6_csk_xmit+0xeb/0x150\n __tcp_transmit_skb+0x555/0xa80\n tcp_write_xmit+0x32a/0xe90\n tcp_sendmsg_locked+0x437/0x1110\n tcp_sendmsg+0x2f/0x50\n...\nskb linear:   00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e\nskb linear:   00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00\nskb linear:   00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00\nskb linear:   00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00\nskb linear:   00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9\nskb linear:   00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01\nskb linear:   00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a(CVE-2025-39770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: initialize more fields in sctp_v6_from_sk()\n\nsyzbot found that sin6_scope_id was not properly initialized,\nleading to undefined behavior.\n\nClear sin6_scope_id and sin6_flowinfo.\n\nBUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983\n  sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390\n  sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452\n  sctp_get_port net/sctp/socket.c:8523 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n  x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nLocal variable addr.i.i created at:\n  sctp_get_port net/sctp/socket.c:8515 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930(CVE-2025-39812)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix buffer free/clear order in deferred receive path\n\nFix a use-after-free window by correcting the buffer release sequence in\nthe deferred receive path. The code freed the RQ buffer first and only\nthen cleared the context pointer under the lock. Concurrent paths (e.g.,\nABTS and the repost path) also inspect and release the same pointer under\nthe lock, so the old order could lead to double-free/UAF.\n\nNote that the repost path already uses the correct pattern: detach the\npointer under the lock, then free it after dropping the lock. The\ndeferred path should do the same.(CVE-2025-39841)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm\n\nWhen send a broadcast packet to a tap device, which was added to a bridge,\nbr_nf_local_in() is called to confirm the conntrack. If another conntrack\nwith the same hash value is added to the hash table, which can be\ntriggered by a normal packet to a non-bridge device, the below warning\nmay happen.\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 96 at net/bridge/br_netfilter_hooks.c:632 br_nf_local_in+0x168/0x200\n  CPU: 1 UID: 0 PID: 96 Comm: tap_send Not tainted 6.17.0-rc2-dirty #44 PREEMPT(voluntary)\n  RIP: 0010:br_nf_local_in+0x168/0x200\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   nf_hook_slow+0x3e/0xf0\n   br_pass_frame_up+0x103/0x180\n   br_handle_frame_finish+0x2de/0x5b0\n   br_nf_hook_thresh+0xc0/0x120\n   br_nf_pre_routing_finish+0x168/0x3a0\n   br_nf_pre_routing+0x237/0x5e0\n   br_handle_frame+0x1ec/0x3c0\n   __netif_receive_skb_core+0x225/0x1210\n   __netif_receive_skb_one_core+0x37/0xa0\n   netif_receive_skb+0x36/0x160\n   tun_get_user+0xa54/0x10c0\n   tun_chr_write_iter+0x65/0xb0\n   vfs_write+0x305/0x410\n   ksys_write+0x60/0xd0\n   do_syscall_64+0xa4/0x260\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nTo solve the hash conflict, nf_ct_resolve_clash() try to merge the\nconntracks, and update skb-\u0026gt;_nfct. However, br_nf_local_in() still use the\nold ct from local variable \u0026apos;nfct\u0026apos; after confirm(), which leads to this\nwarning.\n\nIf confirm() does not insert the conntrack entry and return NF_DROP, the\nwarning may also occur. There is no need to reserve the WARN_ON_ONCE, just\nremove it.(CVE-2025-39894)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer\n\nSince commit 7d5e9737efda (\u0026quot;net: rfkill: gpio: get the name and type from\ndevice property\u0026quot;) rfkill_find_type() gets called with the possibly\nuninitialized \u0026quot;const char *type_name;\u0026quot; local variable.\n\nOn x86 systems when rfkill-gpio binds to a \u0026quot;BCM4752\u0026quot; or \u0026quot;LNV4752\u0026quot;\nacpi_device, the rfkill-\u0026gt;type is set based on the ACPI acpi_device_id:\n\n        rfkill-\u0026gt;type = (unsigned)id-\u0026gt;driver_data;\n\nand there is no \u0026quot;type\u0026quot; property so device_property_read_string() will fail\nand leave type_name uninitialized, leading to a potential crash.\n\nrfkill_find_type() does accept a NULL pointer, fix the potential crash\nby initializing type_name to NULL.\n\nNote likely sofar this has not been caught because:\n\n1. Not many x86 machines actually have a \u0026quot;BCM4752\u0026quot;/\u0026quot;LNV4752\u0026quot; acpi_device\n2. The stack happened to contain NULL where type_name is stored(CVE-2025-39937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Clear tcp_sk(sk)-\u0026gt;fastopen_rsk in tcp_disconnect().\n\nsyzbot reported the splat below where a socket had tcp_sk(sk)-\u0026gt;fastopen_rsk\nin the TCP_ESTABLISHED state. [0]\n\nsyzbot reused the server-side TCP Fast Open socket as a new client before\nthe TFO socket completes 3WHS:\n\n  1. accept()\n  2. connect(AF_UNSPEC)\n  3. connect() to another destination\n\nAs of accept(), sk-\u0026gt;sk_state is TCP_SYN_RECV, and tcp_disconnect() changes\nit to TCP_CLOSE and makes connect() possible, which restarts timers.\n\nSince tcp_disconnect() forgot to clear tcp_sk(sk)-\u0026gt;fastopen_rsk, the\nretransmit timer triggered the warning and the intended packet was not\nretransmitted.\n\nLet\u0026apos;s call reqsk_fastopen_remove() in tcp_disconnect().\n\n[0]:\nWARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nModules linked in:\nCPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nCode: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 \u0026lt;0f\u0026gt; 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e\nRSP: 0018:ffffc900002f8d40 EFLAGS: 00010293\nRAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017\nRDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400\nRBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8\nR10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540\nR13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0\nFS:  0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_write_timer (net/ipv4/tcp_timer.c:738)\n call_timer_fn (kernel/time/timer.c:1747)\n __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372)\n timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135)\n tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035)\n __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1))\n tmigr_handle_remote (kernel/time/timer_migration.c:1096)\n handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580)\n irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39955)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-39980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - set NULL to qm-\u0026gt;debug.qm_diff_regs\n\nWhen the initialization of qm-\u0026gt;debug.acc_diff_reg fails,\nthe probe process does not exit. However, after qm-\u0026gt;debug.qm_diff_regs is\nfreed, it is not set to NULL. This can lead to a double free when the\nremove process attempts to free it again. Therefore, qm-\u0026gt;debug.qm_diff_regs\nshould be set to NULL after it is freed.(CVE-2025-40062)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn\u0026apos;t rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn\u0026apos;t find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.(CVE-2025-40078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - request reserved interrupt for virtual function\n\nThe device interrupt vector 3 is an error interrupt for\nphysical function and a reserved interrupt for virtual function.\nHowever, the driver has not registered the reserved interrupt for\nvirtual function. When allocating interrupts, the number of interrupts\nis allocated based on powers of two, which includes this interrupt.\nWhen the system enables GICv4 and the virtual function passthrough\nto the virtual machine, releasing the interrupt in the driver\ntriggers a warning.\n\nThe WARNING report is:\nWARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4\n\nTherefore, register a reserved interrupt for VF and set the\nIRQF_NO_AUTOEN flag to avoid that warning.(CVE-2025-40136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: avoid NULL dereference when chunk data buffer is missing\n\nchunk-\u0026gt;skb pointer is dereferenced in the if-block where it\u0026apos;s supposed\nto be NULL only.\n\nchunk-\u0026gt;skb can only be NULL if chunk-\u0026gt;head_skb is not. Check for frag_list\ninstead and do it just before replacing chunk-\u0026gt;skb. We\u0026apos;re sure that\notherwise chunk-\u0026gt;skb is non-NULL because of outer if() condition.(CVE-2025-40240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: remove never-working support for setting nsh fields\n\nThe validation of the set(nsh(...)) action is completely wrong.\nIt runs through the nsh_key_put_from_nlattr() function that is the\nsame function that validates NSH keys for the flow match and the\npush_nsh() action.  However, the set(nsh(...)) has a very different\nmemory layout.  Nested attributes in there are doubled in size in\ncase of the masked set().  That makes proper validation impossible.\n\nThere is also confusion in the code between the \u0026apos;masked\u0026apos; flag, that\nsays that the nested attributes are doubled in size containing both\nthe value and the mask, and the \u0026apos;is_mask\u0026apos; that says that the value\nwe\u0026apos;re parsing is the mask.  This is causing kernel crash on trying to\nwrite into mask part of the match with SW_FLOW_KEY_PUT() during\nvalidation, while validate_nsh() doesn\u0026apos;t allocate any memory for it:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary)\n  RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   validate_nsh+0x60/0x90 [openvswitch]\n   validate_set.constprop.0+0x270/0x3c0 [openvswitch]\n   __ovs_nla_copy_actions+0x477/0x860 [openvswitch]\n   ovs_nla_copy_actions+0x8d/0x100 [openvswitch]\n   ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch]\n   genl_family_rcv_msg_doit+0xdb/0x130\n   genl_family_rcv_msg+0x14b/0x220\n   genl_rcv_msg+0x47/0xa0\n   netlink_rcv_skb+0x53/0x100\n   genl_rcv+0x24/0x40\n   netlink_unicast+0x280/0x3b0\n   netlink_sendmsg+0x1f7/0x430\n   ____sys_sendmsg+0x36b/0x3a0\n   ___sys_sendmsg+0x87/0xd0\n   __sys_sendmsg+0x6d/0xd0\n   do_syscall_64+0x7b/0x2c0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe third issue with this process is that while trying to convert\nthe non-masked set into masked one, validate_set() copies and doubles\nthe size of the OVS_KEY_ATTR_NSH as if it didn\u0026apos;t have any nested\nattributes.  It should be copying each nested attribute and doubling\nthem in size independently.  And the process must be properly reversed\nduring the conversion back from masked to a non-masked variant during\nthe flow dump.\n\nIn the end, the only two outcomes of trying to use this action are\neither validation failure or a kernel crash.  And if somehow someone\nmanages to install a flow with such an action, it will most definitely\nnot do what it is supposed to, since all the keys and the masks are\nmixed up.\n\nFixing all the issues is a complex task as it requires re-writing\nmost of the validation code.\n\nGiven that and the fact that this functionality never worked since\nintroduction, let\u0026apos;s just remove it altogether.  It\u0026apos;s better to\nre-introduce it later with a proper implementation instead of trying\nto fix it in stable releases.(CVE-2025-40254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto\n\nsyzbot reported a possible shift-out-of-bounds [1]\n\nBlamed commit added rto_alpha_max and rto_beta_max set to 1000.\n\nIt is unclear if some sctp users are setting very large rto_alpha\nand/or rto_beta.\n\nIn order to prevent user regression, perform the test at run time.\n\nAlso add READ_ONCE() annotations as sysctl values can change under us.\n\n[1]\n\nUBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41\nshift exponent 64 is too large for 32-bit type \u0026apos;unsigned int\u0026apos;\nCPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:94 [inline]\n  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n  ubsan_epilogue lib/ubsan.c:233 [inline]\n  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494\n  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509\n  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502\n  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338\n  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]\n  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline](CVE-2025-40281)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: Prevent TOCTOU out-of-bounds write\n\nFor the following path not holding the sock lock,\n\n  sctp_diag_dump() -\u0026gt; sctp_for_each_endpoint() -\u0026gt; sctp_ep_dump()\n\nmake sure not to exceed bounds in case the address list has grown\nbetween buffer allocation (time-of-check) and write (time-of-use).(CVE-2025-40331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace BUG_ON with bounds check for map-\u0026gt;max_osd\n\nOSD indexes come from untrusted network packets. Boundary checks are\nadded to validate these against map-\u0026gt;max_osd.\n\n[ idryomov: drop BUG_ON in ceph_get_primary_affinity(), minor cosmetic\n  edits ](CVE-2025-68283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()\n\nThe len field originates from untrusted network packets. Boundary\nchecks have been added to prevent potential out-of-bounds writes when\ndecrypting the connection secret or processing service tickets.\n\n[ idryomov: changelog ](CVE-2025-68284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: lookup hci_conn on RX path on protocol side\n\nThe hdev lock/lookup/unlock/use pattern in the packet RX path doesn\u0026apos;t\nensure hci_conn* is not concurrently modified/deleted. This locking\nappears to be leftover from before conn_hash started using RCU\ncommit bf4c63252490b (\u0026quot;Bluetooth: convert conn hash to RCU\u0026quot;)\nand not clear if it had purpose since then.\n\nCurrently, there are code paths that delete hci_conn* from elsewhere\nthan the ordered hdev-\u0026gt;workqueue where the RX work runs in. E.g.\ncommit 5af1f84ed13a (\u0026quot;Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync\u0026quot;)\nintroduced some of these, and there probably were a few others before\nit.  It\u0026apos;s better to do the locking so that even if these run\nconcurrently no UAF is possible.\n\nMove the lookup of hci_conn and associated socket-specific conn to\nprotocol recv handlers, and do them within a single critical section\nto cover hci_conn* usage and lookup.\n\nsyzkaller has reported a crash that appears to be this issue:\n\n    [Task hdev-\u0026gt;workqueue]          [Task 2]\n                                    hci_disconnect_all_sync\n    l2cap_recv_acldata(hcon)\n                                      hci_conn_get(hcon)\n                                      hci_abort_conn_sync(hcon)\n                                        hci_dev_lock\n      hci_dev_lock\n                                        hci_conn_del(hcon)\n      v-------------------------------- hci_dev_unlock\n                                      hci_conn_put(hcon)\n      conn = hcon-\u0026gt;l2cap_data (UAF)(CVE-2025-68304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: Handle error code returned by ima_filter_rule_match()\n\nIn ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to\nthe rule being NULL, the function incorrectly skips the \u0026apos;if (!rc)\u0026apos; check\nand sets \u0026apos;result = true\u0026apos;. The LSM rule is considered a match, causing\nextra files to be measured by IMA.\n\nThis issue can be reproduced in the following scenario:\nAfter unloading the SELinux policy module via \u0026apos;semodule -d\u0026apos;, if an IMA\nmeasurement is triggered before ima_lsm_rules is updated,\nin ima_match_rules(), the first call to ima_filter_rule_match() returns\n-ESTALE. This causes the code to enter the \u0026apos;if (rc == -ESTALE \u0026amp;\u0026amp;\n!rule_reinitialized)\u0026apos; block, perform ima_lsm_copy_rule() and retry. In\nima_lsm_copy_rule(), since the SELinux module has been removed, the rule\nbecomes NULL, and the second call to ima_filter_rule_match() returns\n-ENOENT. This bypasses the \u0026apos;if (!rc)\u0026apos; check and results in a false match.\n\nCall trace:\n  selinux_audit_rule_match+0x310/0x3b8\n  security_audit_rule_match+0x60/0xa0\n  ima_match_rules+0x2e4/0x4a0\n  ima_match_policy+0x9c/0x1e8\n  ima_get_action+0x48/0x60\n  process_measurement+0xf8/0xa98\n  ima_bprm_check+0x98/0xd8\n  security_bprm_check+0x5c/0x78\n  search_binary_handler+0x6c/0x318\n  exec_binprm+0x58/0x1b8\n  bprm_execve+0xb8/0x130\n  do_execveat_common.isra.0+0x1a8/0x258\n  __arm64_sys_execve+0x48/0x68\n  invoke_syscall+0x50/0x128\n  el0_svc_common.constprop.0+0xc8/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x44/0x200\n  el0t_64_sync_handler+0x100/0x130\n  el0t_64_sync+0x3c8/0x3d0\n\nFix this by changing \u0026apos;if (!rc)\u0026apos; to \u0026apos;if (rc \u0026lt;= 0)\u0026apos; to ensure that error\ncodes like -ENOENT do not bypass the check and accidentally result in a\nsuccessful match.(CVE-2025-68740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u0026gt;stats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u0026lt;-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u0026gt;items[index] = \u0026amp;dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u0026gt;stats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(\u0026amp;stats-\u0026gt;syncp)\n---softirq end---\n\n  static_branch_dec(\u0026amp;cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.(CVE-2025-68742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: Avoid overflowing userspace buffer on stats query\n\nThe ethtool -S command operates across three ioctl calls:\nETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and\nETHTOOL_GSTATS for the values.\n\nIf the number of stats changes between these calls (e.g., due to device\nreconfiguration), userspace\u0026apos;s buffer allocation will be incorrect,\npotentially leading to buffer overflow.\n\nDrivers are generally expected to maintain stable stat counts, but some\ndrivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making\nthis scenario possible.\n\nSome drivers try to handle this internally:\n- bnad_get_ethtool_stats() returns early in case stats.n_stats is not\n  equal to the driver\u0026apos;s stats count.\n- micrel/ksz884x also makes sure not to write anything beyond\n  stats.n_stats and overflow the buffer.\n\nHowever, both use stats.n_stats which is already assigned with the value\nreturned from get_sset_count(), hence won\u0026apos;t solve the issue described\nhere.\n\nChange ethtool_get_strings(), ethtool_get_stats(),\nethtool_get_phy_stats() to not return anything in case of a mismatch\nbetween userspace\u0026apos;s size and get_sset_size(), to prevent buffer\noverflow.\nThe returned n_stats value will be equal to zero, to reflect that\nnothing has been returned.\n\nThis could result in one of two cases when using upstream ethtool,\ndepending on when the size change is detected:\n1. When detected in ethtool_get_strings():\n    # ethtool -S eth2\n    no stats available\n\n2. When detected in get stats, all stats will be reported as zero.\n\nBoth cases are presumably transient, and a subsequent ethtool call\nshould succeed.\n\nOther than the overflow avoidance, these two cases are very evident (no\noutput/cleared stats), which is arguably better than presenting\nincorrect/shifted stats.\nI also considered returning an error instead of a \u0026quot;silent\u0026quot; response, but\nthat seems more destructive towards userspace apps.\n\nNotes:\n- This patch does not claim to fix the inherent race, it only makes sure\n  that we do not overflow the userspace buffer, and makes for a more\n  predictable behavior.\n\n- RTNL lock is held during each ioctl, the race window exists between\n  the separate ioctl calls when the lock is released.\n\n- Userspace ethtool always fills stats.n_stats, but it is likely that\n  these stats ioctls are implemented in other userspace applications\n  which might not fill it. The added code checks that it\u0026apos;s not zero,\n  to prevent any regressions.(CVE-2025-68795)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: xattr: fix null pointer deref in ext4_raw_inode()\n\nIf ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),\niloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()\nlacks error checking, this will lead to a null pointer dereference\nin ext4_raw_inode(), called right after ext4_get_inode_loc().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68820)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: using the num_tqps in the vf driver to apply for resources\n\nCurrently, hdev-\u0026gt;htqp is allocated using hdev-\u0026gt;num_tqps, and kinfo-\u0026gt;tqp\nis allocated using kinfo-\u0026gt;num_tqps. However, kinfo-\u0026gt;num_tqps is set to\nmin(new_tqps, hdev-\u0026gt;num_tqps);  Therefore, kinfo-\u0026gt;num_tqps may be smaller\nthan hdev-\u0026gt;num_tqps, which causes some hdev-\u0026gt;htqp[i] to remain\nuninitialized in hclgevf_knic_setup().\n\nThus, this patch allocates hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp using hdev-\u0026gt;num_tqps,\nensuring that the lengths of hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp are consistent\nand that all elements are properly initialized.(CVE-2025-71064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset\n\n`qfq_class-\u0026gt;leaf_qdisc-\u0026gt;q.qlen \u0026gt; 0` does not imply that the class\nitself is active.\n\nTwo qfq_class objects may point to the same leaf_qdisc. This happens\nwhen:\n\n1. one QFQ qdisc is attached to the dev as the root qdisc, and\n\n2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()\n/ qdisc_put()) and is pending to be destroyed, as in function\ntc_new_tfilter.\n\nWhen packets are enqueued through the root QFQ qdisc, the shared\nleaf_qdisc-\u0026gt;q.qlen increases. At the same time, the second QFQ\nqdisc triggers qdisc_put and qdisc_destroy: the qdisc enters\nqfq_reset() with its own q-\u0026gt;q.qlen == 0, but its class\u0026apos;s leaf\nqdisc-\u0026gt;q.qlen \u0026gt; 0. Therefore, the qfq_reset would wrongly deactivate\nan inactive aggregate and trigger a null-deref in qfq_deactivate_agg:\n\n[    0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    0.903571] #PF: supervisor write access in kernel mode\n[    0.903860] #PF: error_code(0x0002) - not-present page\n[    0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0\n[    0.904502] Oops: Oops: 0002 [#1] SMP NOPTI\n[    0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE\n[    0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[    0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))\n[    0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0\n\nCode starting with the faulting instruction\n===========================================\n   0:\t0f 84 4d 01 00 00    \tje     0x153\n   6:\t48 89 70 18          \tmov    %rsi,0x18(%rax)\n   a:\t8b 4b 10             \tmov    0x10(%rbx),%ecx\n   d:\t48 c7 c2 ff ff ff ff \tmov    $0xffffffffffffffff,%rdx\n  14:\t48 8b 78 08          \tmov    0x8(%rax),%rdi\n  18:\t48 d3 e2             \tshl    %cl,%rdx\n  1b:\t48 21 f2             \tand    %rsi,%rdx\n  1e:\t48 2b 13             \tsub    (%rbx),%rdx\n  21:\t48 8b 30             \tmov    (%rax),%rsi\n  24:\t48 d3 ea             \tshr    %cl,%rdx\n  27:\t8b 4b 18             \tmov    0x18(%rbx),%ecx\n\t...\n[    0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246\n[    0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000\n[    0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[    0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000\n[    0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000\n[    0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880\n[    0.909179] FS:  000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000\n[    0.909572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0\n[    0.910247] PKRU: 55555554\n[    0.910391] Call Trace:\n[    0.910527]  \u0026lt;TASK\u0026gt;\n[    0.910638]  qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)\n[    0.910826]  qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)\n[    0.911040]  __qdisc_destroy (net/sched/sch_generic.c:1076)\n[    0.911236]  tc_new_tfilter (net/sched/cls_api.c:2447)\n[    0.911447]  rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\n[    0.911663]  ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)\n[    0.911894]  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n[    0.912100]  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n[    0.912296]  ? __alloc_skb (net/core/skbuff.c:706)\n[    0.912484]  netlink_sendmsg (net/netlink/af\n---truncated---(CVE-2026-22976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix reference count leak in bpf_prog_test_run_xdp()\n\nsyzbot is reporting\n\n  unregister_netdevice: waiting for sit0 to become free. Usage count = 2\n\nproblem. A debug printk() patch found that a refcount is obtained at\nxdp_convert_md_to_buff() from bpf_prog_test_run_xdp().\n\nAccording to commit ec94670fcb3b (\u0026quot;bpf: Support specifying ingress via\nxdp_md context in BPF_PROG_TEST_RUN\u0026quot;), the refcount obtained by\nxdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().\n\nTherefore, we can consider that the error handling path introduced by\ncommit 1c1949982524 (\u0026quot;bpf: introduce frags support to\nbpf_prog_test_run_xdp()\u0026quot;) forgot to call xdp_convert_buff_to_md().(CVE-2026-22994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a deadlock involving nfs_release_folio()\n\nWang Zhaolong reports a deadlock involving NFSv4.1 state recovery\nwaiting on kthreadd, which is attempting to reclaim memory by calling\nnfs_release_folio(). The latter cannot make progress due to state\nrecovery being needed.\n\nIt seems that the only safe thing to do here is to kick off a writeback\nof the folio, without waiting for completion, or else kicking off an\nasynchronous commit.(CVE-2026-23053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: maple: free entry on mas_store_gfp() failure\n\nregcache_maple_write() allocates a new block (\u0026apos;entry\u0026apos;) to merge\nadjacent ranges and then stores it with mas_store_gfp().\nWhen mas_store_gfp() fails, the new \u0026apos;entry\u0026apos; remains allocated and\nis never freed, leaking memory.\n\nFree \u0026apos;entry\u0026apos; on the failure path; on success continue freeing the\nreplaced neighbor blocks (\u0026apos;lower\u0026apos;, \u0026apos;upper\u0026apos;).(CVE-2026-23260)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: observe an RCU grace period in macvlan_common_newlink() error path\n\nvalis reported that a race condition still happens after my prior patch.\n\nmacvlan_common_newlink() might have made @dev visible before\ndetecting an error, and its caller will directly call free_netdev(dev).\n\nWe must respect an RCU period, either in macvlan or the core networking\nstack.\n\nAfter adding a temporary mdelay(1000) in macvlan_forward_source_one()\nto open the race window, valis repro was:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\nip link add mv0 link p2 type macvlan mode source\n\n(ip link add invalid% link p2 type macvlan mode source macaddr add\n00:00:00:00:00:20 \u0026amp;) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4\nPING 1.2.3.4 (1.2.3.4): 56 data bytes\nRTNETLINK answers: Invalid argument\n\nBUG: KASAN: slab-use-after-free in macvlan_forward_source\n(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nRead of size 8 at addr ffff888016bb89c0 by task e/175\n\nCPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\nCall Trace:\n\u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:123)\nprint_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nkasan_report (mm/kasan/report.c:597)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nmacvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\n? tasklet_init (kernel/softirq.c:983)\nmacvlan_handle_frame (drivers/net/macvlan.c:501)\n\nAllocated by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\n__kasan_kmalloc (mm/kasan/common.c:419)\n__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657\nmm/slub.c:7140)\nalloc_netdev_mqs (net/core/dev.c:12012)\nrtnl_create_link (net/core/rtnetlink.c:3648)\nrtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nFreed by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\nkasan_save_free_info (mm/kasan/generic.c:587)\n__kasan_slab_free (mm/kasan/common.c:287)\nkfree (mm/slub.c:6674 mm/slub.c:6882)\nrtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)(CVE-2026-23273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Fix recursive locking in __configfs_open_file()\n\nIn flush_write_buffer, \u0026amp;p-\u0026gt;frag_sem is acquired and then the loaded store\nfunction is called, which, here, is target_core_item_dbroot_store().  This\nfunction called filp_open(), following which these functions were called\n(in reverse order), according to the call trace:\n\n  down_read\n  __configfs_open_file\n  do_dentry_open\n  vfs_open\n  do_open\n  path_openat\n  do_filp_open\n  file_open_name\n  filp_open\n  target_core_item_dbroot_store\n  flush_write_buffer\n  configfs_write_iter\n\ntarget_core_item_dbroot_store() tries to validate the new file path by\ntrying to open the file path provided to it; however, in this case, the bug\nreport shows:\n\ndb_root: not a directory: /sys/kernel/config/target/dbroot\n\nindicating that the same configfs file was tried to be opened, on which it\nis currently working on. Thus, it is trying to acquire frag_sem semaphore\nof the same file of which it already holds the semaphore obtained in\nflush_write_buffer(), leading to acquiring the semaphore in a nested manner\nand a possibility of recursive locking.\n\nFix this by modifying target_core_item_dbroot_store() to use kern_path()\ninstead of filp_open() to avoid opening the file using filesystem-specific\nfunction __configfs_open_file(), and further modifying it to make this fix\ncompatible.(CVE-2026-23292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix refcount leak for tagset_refcnt\n\nThis leak will cause a hang when tearing down the SCSI host. For example,\niscsid hangs with the following call trace:\n\n[130120.652718] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured\n\nPID: 2528     TASK: ffff9d0408974e00  CPU: 3    COMMAND: \u0026quot;iscsid\u0026quot;\n #0 [ffffb5b9c134b9e0] __schedule at ffffffff860657d4\n #1 [ffffb5b9c134ba28] schedule at ffffffff86065c6f\n #2 [ffffb5b9c134ba40] schedule_timeout at ffffffff86069fb0\n #3 [ffffb5b9c134bab0] __wait_for_common at ffffffff8606674f\n #4 [ffffb5b9c134bb10] scsi_remove_host at ffffffff85bfe84b\n #5 [ffffb5b9c134bb30] iscsi_sw_tcp_session_destroy at ffffffffc03031c4 [iscsi_tcp]\n #6 [ffffb5b9c134bb48] iscsi_if_recv_msg at ffffffffc0292692 [scsi_transport_iscsi]\n #7 [ffffb5b9c134bb98] iscsi_if_rx at ffffffffc02929c2 [scsi_transport_iscsi]\n #8 [ffffb5b9c134bbf0] netlink_unicast at ffffffff85e551d6\n #9 [ffffb5b9c134bc38] netlink_sendmsg at ffffffff85e554ef(CVE-2026-23296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix preempt count leak in napi poll tracepoint\n\nUsing get_cpu() in the tracepoint assignment causes an obvious preempt\ncount leak because nothing invokes put_cpu() to undo it:\n\n  softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101?\n\nThis clearly has seen a lot of testing in the last 3+ years...\n\nUse smp_processor_id() instead.(CVE-2026-23313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim\n\nThe root cause of this bug is that when \u0026apos;bpf_link_put\u0026apos; reduces the\nrefcount of \u0026apos;shim_link-\u0026gt;link.link\u0026apos; to zero, the resource is considered\nreleased but may still be referenced via \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;cgroup_shim_find\u0026apos;. The actual cleanup of \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;bpf_shim_tramp_link_release\u0026apos; is deferred. During this window, another\nprocess can cause a use-after-free via \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n\nBased on Martin KaFai Lau\u0026apos;s suggestions, I have created a simple patch.\n\nTo fix this:\n   Add an atomic non-zero check in \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n   Only increment the refcount if it is not already zero.\n\nTesting:\n   I verified the fix by adding a delay in\n   \u0026apos;bpf_shim_tramp_link_release\u0026apos; to make the bug easier to trigger:\n\nstatic void bpf_shim_tramp_link_release(struct bpf_link *link)\n{\n\t/* ... */\n\tif (!shim_link-\u0026gt;trampoline)\n\t\treturn;\n\n+\tmsleep(100);\n\tWARN_ON_ONCE(bpf_trampoline_unlink_prog(\u0026amp;shim_link-\u0026gt;link,\n\t\tshim_link-\u0026gt;trampoline, NULL));\n\tbpf_trampoline_put(shim_link-\u0026gt;trampoline);\n}\n\nBefore the patch, running a PoC easily reproduced the crash(almost 100%)\nwith a call trace similar to KaiyanM\u0026apos;s report.\nAfter the patch, the bug no longer occurs even after millions of\niterations.(CVE-2026-23319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: defer freeing of boot services memory\n\nefi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE\nand EFI_BOOT_SERVICES_DATA using memblock_free_late().\n\nThere are two issue with that: memblock_free_late() should be used for\nmemory allocated with memblock_alloc() while the memory reserved with\nmemblock_reserve() should be freed with free_reserved_area().\n\nMore acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y\nefi_free_boot_services() is called before deferred initialization of the\nmemory map is complete.\n\nBenjamin Herrenschmidt reports that this causes a leak of ~140MB of\nRAM on EC2 t3a.nano instances which only have 512MB or RAM.\n\nIf the freed memory resides in the areas that memory map for them is\nstill uninitialized, they won\u0026apos;t be actually freed because\nmemblock_free_late() calls memblock_free_pages() and the latter skips\nuninitialized pages.\n\nUsing free_reserved_area() at this point is also problematic because\n__free_page() accesses the buddy of the freed page and that again might\nend up in uninitialized part of the memory map.\n\nDelaying the entire efi_free_boot_services() could be problematic\nbecause in addition to freeing boot services memory it updates\nefi.memmap without any synchronization and that\u0026apos;s undesirable late in\nboot when there is concurrency.\n\nMore robust approach is to only defer freeing of the EFI boot services\nmemory.\n\nSplit efi_free_boot_services() in two. First efi_unmap_boot_services()\ncollects ranges that should be freed into an array then\nefi_free_boot_services() later frees them after deferred init is complete.(CVE-2026-23352)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stack-out-of-bounds write in devmap\n\nget_upper_ifindexes() iterates over all upper devices and writes their\nindices into an array without checking bounds.\n\nAlso the callers assume that the max number of upper devices is\nMAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack,\nbut that assumption is not correct and the number of upper devices could\nbe larger than MAX_NEST_DEV (e.g., many macvlans), causing a\nstack-out-of-bounds write.\n\nAdd a max parameter to get_upper_ifindexes() to avoid the issue.\nWhen there are too many upper devices, return -EOVERFLOW and abort the\nredirect.\n\nTo reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with\nan XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS.\nThen send a packet to the device to trigger the XDP redirect path.(CVE-2026-23359)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin queue leak on controller reset\n\nWhen nvme_alloc_admin_tag_set() is called during a controller reset,\na previous admin queue may still exist. Release it properly before\nallocating a new one to avoid orphaning the old queue.\n\nThis fixes a regression introduced by commit 03b3bcd319b3 (\u0026quot;nvme: fix\nadmin request_queue lifetime\u0026quot;).(CVE-2026-23360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblktrace: fix __this_cpu_read/write in preemptible context\n\ntracing_record_cmdline() internally uses __this_cpu_read() and\n__this_cpu_write() on the per-CPU variable trace_cmdline_save, and\ntrace_save_cmdline() explicitly asserts preemption is disabled via\nlockdep_assert_preemption_disabled(). These operations are only safe\nwhen preemption is off, as they were designed to be called from the\nscheduler context (probe_wakeup_sched_switch() / probe_wakeup()).\n\n__blk_add_trace() was calling tracing_record_cmdline(current) early in\nthe blk_tracer path, before ring buffer reservation, from process\ncontext where preemption is fully enabled. This triggers the following\nusing blktests/blktrace/002:\n\nblktrace/002 (blktrace ftrace corruption with sysfs trace)   [failed]\n    runtime  0.367s  ...  0.437s\n    something found in dmesg:\n    [   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n    [   81.239580] null_blk: disk nullb1 created\n    [   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n    [   81.362842] caller is tracing_record_cmdline+0x10/0x40\n    [   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n    [   81.362877] Tainted: [N]=TEST\n    [   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n    [   81.362881] Call Trace:\n    [   81.362884]  \u0026lt;TASK\u0026gt;\n    [   81.362886]  dump_stack_lvl+0x8d/0xb0\n    ...\n    (See \u0026apos;/mnt/sda/blktests/results/nodev/blktrace/002.dmesg\u0026apos; for the entire message)\n\n[   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n[   81.239580] null_blk: disk nullb1 created\n[   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n[   81.362842] caller is tracing_record_cmdline+0x10/0x40\n[   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n[   81.362877] Tainted: [N]=TEST\n[   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[   81.362881] Call Trace:\n[   81.362884]  \u0026lt;TASK\u0026gt;\n[   81.362886]  dump_stack_lvl+0x8d/0xb0\n[   81.362895]  check_preemption_disabled+0xce/0xe0\n[   81.362902]  tracing_record_cmdline+0x10/0x40\n[   81.362923]  __blk_add_trace+0x307/0x5d0\n[   81.362934]  ? lock_acquire+0xe0/0x300\n[   81.362940]  ? iov_iter_extract_pages+0x101/0xa30\n[   81.362959]  blk_add_trace_bio+0x106/0x1e0\n[   81.362968]  submit_bio_noacct_nocheck+0x24b/0x3a0\n[   81.362979]  ? lockdep_init_map_type+0x58/0x260\n[   81.362988]  submit_bio_wait+0x56/0x90\n[   81.363009]  __blkdev_direct_IO_simple+0x16c/0x250\n[   81.363026]  ? __pfx_submit_bio_wait_endio+0x10/0x10\n[   81.363038]  ? rcu_read_lock_any_held+0x73/0xa0\n[   81.363051]  blkdev_read_iter+0xc1/0x140\n[   81.363059]  vfs_read+0x20b/0x330\n[   81.363083]  ksys_read+0x67/0xe0\n[   81.363090]  do_syscall_64+0xbf/0xf00\n[   81.363102]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   81.363106] RIP: 0033:0x7f281906029d\n[   81.363111] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d 66 63 0a 00 e8 59 ff 01 00 66 0f 1f 84 00 00 00 00 00 80 3d 41 33 0e 00 00 74 17 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec\n[   81.363113] RSP: 002b:00007ffca127dd48 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\n[   81.363120] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f281906029d\n[   81.363122] RDX: 0000000000001000 RSI: 0000559f8bfae000 RDI: 0000000000000000\n[   81.363123] RBP: 0000000000001000 R08: 0000002863a10a81 R09: 00007f281915f000\n[   81.363124] R10: 00007f2818f77b60 R11: 0000000000000246 R12: 0000559f8bfae000\n[   81.363126] R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000a\n[   81.363142]  \u0026lt;/TASK\u0026gt;\n\nThe same BUG fires from blk_add_trace_plug(), blk_add_trace_unplug(),\nand blk_add_trace_rq() paths as well.\n\nThe purpose of tracin\n---truncated---(CVE-2026-23374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing\n\nstruct bpf_plt contains a u64 target field. Currently, the BPF JIT\nallocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT\nbuffer.\n\nBecause the base address of the JIT buffer can be 4-byte aligned (e.g.,\nending in 0x4 or 0xc), the relative padding logic in build_plt() fails\nto ensure that target lands on an 8-byte boundary.\n\nThis leads to two issues:\n1. UBSAN reports misaligned-access warnings when dereferencing the\n   structure.\n2. More critically, target is updated concurrently via WRITE_ONCE() in\n   bpf_arch_text_poke() while the JIT\u0026apos;d code executes ldr. On arm64,\n   64-bit loads/stores are only guaranteed to be single-copy atomic if\n   they are 64-bit aligned. A misaligned target risks a torn read,\n   causing the JIT to jump to a corrupted address.\n\nFix this by increasing the allocation alignment requirement to 8 bytes\n(sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of\nthe JIT buffer to an 8-byte boundary, allowing the relative padding math\nin build_plt() to correctly align the target field.(CVE-2026-23383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: check metadata block offset is within range\n\nSyzkaller reports a \u0026quot;general protection fault in squashfs_copy_data\u0026quot;\n\nThis is ultimately caused by a corrupted index look-up table, which\nproduces a negative metadata block offset.\n\nThis is subsequently passed to squashfs_copy_data (via\nsquashfs_read_metadata) where the negative offset causes an out of bounds\naccess.\n\nThe fix is to check that the offset is within range in\nsquashfs_read_metadata.  This will trap this and other cases.(CVE-2026-23388)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: reject mount if bigalloc with s_first_data_block != 0\n\nbigalloc with s_first_data_block != 0 is not supported, reject mounting\nit.(CVE-2026-31447)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: Check to ensure report responses match the request\n\nIt is possible for a malicious (or clumsy) device to respond to a\nspecific report\u0026apos;s feature request using a completely different report\nID.  This can cause confusion in the HID core resulting in nasty\nside-effects such as OOB writes.\n\nAdd a check to ensure that the report ID in the response, matches the\none that was requested.  If it doesn\u0026apos;t, omit reporting the raw event and\nreturn early.(CVE-2026-43047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Mitigate potential OOB by removing bogus memset()\n\nThe memset() in hid_report_raw_event() has the good intention of\nclearing out bogus data by zeroing the area from the end of the incoming\ndata string to the assumed end of the buffer.  However, as we have\npreviously seen, doing so can easily result in OOB reads and writes in\nthe subsequent thread of execution.\n\nThe current suggestion from one of the HID maintainers is to remove the\nmemset() and simply return if the incoming event buffer size is not\nlarge enough to fill the associated report.\n\nSuggested-by Benjamin Tissoires \u0026lt;(CVE-2026-43048)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: close crash window in attr dabtree inactivation\n\nWhen inactivating an inode with node-format extended attributes,\nxfs_attr3_node_inactive() invalidates all child leaf/node blocks via\nxfs_trans_binval(), but intentionally does not remove the corresponding\nentries from their parent node blocks.  The implicit assumption is that\nxfs_attr_inactive() will truncate the entire attr fork to zero extents\nafterwards, so log recovery will never reach the root node and follow\nthose stale pointers.\n\nHowever, if a log shutdown occurs after the leaf/node block cancellations\ncommit but before the attr bmap truncation commits, this assumption\nbreaks.  Recovery replays the attr bmap intact (the inode still has\nattr fork extents), but suppresses replay of all cancelled leaf/node\nblocks, maybe leaving them as stale data on disk.  On the next mount,\nxlog_recover_process_iunlinks() retries inactivation and attempts to\nread the root node via the attr bmap. If the root node was not replayed,\nreading the unreplayed root block triggers a metadata verification\nfailure immediately; if it was replayed, following its child pointers\nto unreplayed child blocks triggers the same failure:\n\n XFS (pmem0): Metadata corruption detected at\n xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78\n XFS (pmem0): Unmount and run xfs_repair\n XFS (pmem0): First 128 bytes of corrupted metadata buffer:\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n XFS (pmem0): metadata I/O error in \u0026quot;xfs_da_read_buf+0x104/0x190\u0026quot; at daddr 0x78 len 8 error 117\n\nFix this in two places:\n\nIn xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a\nchild block, immediately remove the entry that references it from the\nparent node in the same transaction.  This eliminates the window where\nthe parent holds a pointer to a cancelled block.  Once all children are\nremoved, the now-empty root node is converted to a leaf block within the\nsame transaction. This node-to-leaf conversion is necessary for crash\nsafety. If the system shutdown after the empty node is written to the\nlog but before the second-phase bmap truncation commits, log recovery\nwill attempt to verify the root block on disk. xfs_da3_node_verify()\ndoes not permit a node block with count == 0; such a block will fail\nverification and trigger a metadata corruption shutdown. on the other\nhand, leaf blocks are allowed to have this transient state.\n\nIn xfs_attr_inactive(), split the attr fork truncation into two explicit\nphases.  First, truncate all extents beyond the root block (the child\nextents whose parent references have already been removed above).\nSecond, invalidate the root block and truncate the attr bmap to zero in\na single transaction.  The two operations in the second phase must be\natomic: as long as the attr bmap has any non-zero length, recovery can\nfollow it to the root block, so the root block invalidation must commit\ntogether with the bmap-to-zero truncation.(CVE-2026-43053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\u0026quot;\n\nThis reverts commit 05703271c3cd (\u0026quot;PCI/IOV: Add PCI rescan-remove locking\nwhen enabling/disabling SR-IOV\u0026quot;), which causes a deadlock by recursively\ntaking pci_rescan_remove_lock when sriov_del_vfs() is called as part of\npci_stop_and_remove_bus_device(). For example with the following sequence\nof commands:\n\n  $ echo \u0026lt;NUM\u0026gt; \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/sriov_numvfs\n  $ echo 1 \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/remove\n\nA trimmed trace of the deadlock on a mlx5 device is as below:\n\n  zsh/5715 is trying to acquire lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140\n\n  but task is already holding lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80\n  ...\n  Call Trace:\n   [\u0026lt;00000259778c4f90\u0026gt;] dump_stack_lvl+0xc0/0x110\n   [\u0026lt;00000259779c844e\u0026gt;] print_deadlock_bug+0x31e/0x330\n   [\u0026lt;00000259779c1908\u0026gt;] __lock_acquire+0x16c8/0x32f0\n   [\u0026lt;00000259779bffac\u0026gt;] lock_acquire+0x14c/0x350\n   [\u0026lt;00000259789643a6\u0026gt;] __mutex_lock_common+0xe6/0x1520\n   [\u0026lt;000002597896413c\u0026gt;] mutex_lock_nested+0x3c/0x50\n   [\u0026lt;00000259784a07e4\u0026gt;] sriov_disable+0x34/0x140\n   [\u0026lt;00000258f7d6dd80\u0026gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]\n   [\u0026lt;00000258f7d5745e\u0026gt;] remove_one+0x5e/0xf0 [mlx5_core]\n   [\u0026lt;00000259784857fc\u0026gt;] pci_device_remove+0x3c/0xa0\n   [\u0026lt;000002597851012e\u0026gt;] device_release_driver_internal+0x18e/0x280\n   [\u0026lt;000002597847ae22\u0026gt;] pci_stop_bus_device+0x82/0xa0\n   [\u0026lt;000002597847afce\u0026gt;] pci_stop_and_remove_bus_device_locked+0x5e/0x80\n   [\u0026lt;00000259784972c2\u0026gt;] remove_store+0x72/0x90\n   [\u0026lt;0000025977e6661a\u0026gt;] kernfs_fop_write_iter+0x15a/0x200\n   [\u0026lt;0000025977d7241c\u0026gt;] vfs_write+0x24c/0x300\n   [\u0026lt;0000025977d72696\u0026gt;] ksys_write+0x86/0x110\n   [\u0026lt;000002597895b61c\u0026gt;] __do_syscall+0x14c/0x400\n   [\u0026lt;000002597896e0ee\u0026gt;] system_call+0x6e/0x90\n\nThis alone is not a complete fix as it restores the issue the cited commit\ntried to solve. A new fix will be provided as a follow on.(CVE-2026-43147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: Add support for TSV110 Spectre-BHB mitigation\n\nThe TSV110 processor is vulnerable to the Spectre-BHB (Branch History\nBuffer) attack, which can be exploited to leak information through\nbranch prediction side channels. This commit adds the MIDR of TSV110\nto the list for software mitigation.(CVE-2026-43261)\n\nIn the Linux kernel, the kexec_load_purgatory() function derives image-\u0026gt;start by locating e_entry inside an SHF_EXECINSTR section. If the purgatory object contains multiple executable sections with overlapping sh_addr, the entrypoint check can match more than once and trigger a WARN. Derive the entry section from the purgatory_start symbol when present and compute image-\u0026gt;start from its final placement. Keep the existing e_entry fallback for purgatories that do not expose the symbol.(CVE-2026-43289)\n\nIn the Linux kernel, there is a potential out-of-bounds access vulnerability in the ceph_handle_auth_reply() function of the libceph component. When processing messages of type CEPH_MSG_AUTH_REPLY, the value of the payload_len field is stored in a variable of type int. A value greater than INT_MAX leads to integer overflow and is interpreted as a negative value, which causes the pointer address to be decremented and subsequently accessed because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation. The vulnerability is fixed by changing the data type of payload_len to u32 and introducing additional sanity checks.(CVE-2026-43407)\n\nIn the Linux kernel, when an alias is found through d_splice_alias in the nfs3_proc_create function, if the alias happens to be a directory dentry, the system does not return any error but simply forgets about this alias, leaving the original dentry to be added as negative. This later causes a system crash in nfs_atomic_open_v23/finish_open since a negative dentry is supplied to do_dentry_open. This issue was observed running lustre-racer, where directories and files are created/removed concurrently with the same name and O_EXCL is not used to open files.(CVE-2026-43470)","status":"published","published":"2026-05-22T11:11:22Z","modified":"2026-08-18T01:20:02.121651445Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"OESA-2026-2493","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\nscsi: target: Fix recursive locking in __configfs_open_file()\n\nIn flush_write_buffer, \u0026amp;p-\u0026gt;frag_sem is acquired and then the loaded store\nfunction is called, which, here, is target_core_item_dbroot_store().  This\nfunction called filp_open(), following which these functions were called\n(in reverse order), according to the call trace:\n\n  down_read\n  __configfs_open_file\n  do_dentry_open\n  vfs_open\n  do_open\n  path_openat\n  do_filp_open\n  file_open_name\n  filp_open\n  target_core_item_dbroot_store\n  flush_write_buffer\n  configfs_write_iter\n\ntarget_core_item_dbroot_store() tries to validate the new file path by\ntrying to open the file path provided to it; however, in this case, the bug\nreport shows:\n\ndb_root: not a directory: /sys/kernel/config/target/dbroot\n\nindicating that the same configfs file was tried to be opened, on which it\nis currently working on. Thus, it is trying to acquire frag_sem semaphore\nof the same file of which it already holds the semaphore obtained in\nflush_write_buffer(), leading to acquiring the semaphore in a nested manner\nand a possibility of recursive locking.\n\nFix this by modifying target_core_item_dbroot_store() to use kern_path()\ninstead of filp_open() to avoid opening the file using filesystem-specific\nfunction __configfs_open_file(), and further modifying it to make this fix\ncompatible.(CVE-2026-23292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix refcount leak for tagset_refcnt\n\nThis leak will cause a hang when tearing down the SCSI host. For example,\niscsid hangs with the following call trace:\n\n[130120.652718] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured\n\nPID: 2528     TASK: ffff9d0408974e00  CPU: 3    COMMAND: \u0026quot;iscsid\u0026quot;\n #0 [ffffb5b9c134b9e0] __schedule at ffffffff860657d4\n #1 [ffffb5b9c134ba28] schedule at ffffffff86065c6f\n #2 [ffffb5b9c134ba40] schedule_timeout at ffffffff86069fb0\n #3 [ffffb5b9c134bab0] __wait_for_common at ffffffff8606674f\n #4 [ffffb5b9c134bb10] scsi_remove_host at ffffffff85bfe84b\n #5 [ffffb5b9c134bb30] iscsi_sw_tcp_session_destroy at ffffffffc03031c4 [iscsi_tcp]\n #6 [ffffb5b9c134bb48] iscsi_if_recv_msg at ffffffffc0292692 [scsi_transport_iscsi]\n #7 [ffffb5b9c134bb98] iscsi_if_rx at ffffffffc02929c2 [scsi_transport_iscsi]\n #8 [ffffb5b9c134bbf0] netlink_unicast at ffffffff85e551d6\n #9 [ffffb5b9c134bc38] netlink_sendmsg at ffffffff85e554ef(CVE-2026-23296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix preempt count leak in napi poll tracepoint\n\nUsing get_cpu() in the tracepoint assignment causes an obvious preempt\ncount leak because nothing invokes put_cpu() to undo it:\n\n  softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101?\n\nThis clearly has seen a lot of testing in the last 3+ years...\n\nUse smp_processor_id() instead.(CVE-2026-23313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: defer freeing of boot services memory\n\nefi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE\nand EFI_BOOT_SERVICES_DATA using memblock_free_late().\n\nThere are two issue with that: memblock_free_late() should be used for\nmemory allocated with memblock_alloc() while the memory reserved with\nmemblock_reserve() should be freed with free_reserved_area().\n\nMore acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y\nefi_free_boot_services() is called before deferred initialization of the\nmemory map is complete.\n\nBenjamin Herrenschmidt reports that this causes a leak of ~140MB of\nRAM on EC2 t3a.nano instances which only have 512MB or RAM.\n\nIf the freed memory resides in the areas that memory map for them is\nstill uninitialized, they won\u0026apos;t be actually freed because\nmemblock_free_late() calls memblock_free_pages() and the latter skips\nuninitialized pages.\n\nUsing free_reserved_area() at this point is also problematic because\n__free_page() accesses the buddy of the freed page and that again might\nend up in uninitialized part of the memory map.\n\nDelaying the entire efi_free_boot_services() could be problematic\nbecause in addition to freeing boot services memory it updates\nefi.memmap without any synchronization and that\u0026apos;s undesirable late in\nboot when there is concurrency.\n\nMore robust approach is to only defer freeing of the EFI boot services\nmemory.\n\nSplit efi_free_boot_services() in two. First efi_unmap_boot_services()\ncollects ranges that should be freed into an array then\nefi_free_boot_services() later frees them after deferred init is complete.(CVE-2026-23352)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin queue leak on controller reset\n\nWhen nvme_alloc_admin_tag_set() is called during a controller reset,\na previous admin queue may still exist. Release it properly before\nallocating a new one to avoid orphaning the old queue.\n\nThis fixes a regression introduced by commit 03b3bcd319b3 (\u0026quot;nvme: fix\nadmin request_queue lifetime\u0026quot;).(CVE-2026-23360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblktrace: fix __this_cpu_read/write in preemptible context\n\ntracing_record_cmdline() internally uses __this_cpu_read() and\n__this_cpu_write() on the per-CPU variable trace_cmdline_save, and\ntrace_save_cmdline() explicitly asserts preemption is disabled via\nlockdep_assert_preemption_disabled(). These operations are only safe\nwhen preemption is off, as they were designed to be called from the\nscheduler context (probe_wakeup_sched_switch() / probe_wakeup()).\n\n__blk_add_trace() was calling tracing_record_cmdline(current) early in\nthe blk_tracer path, before ring buffer reservation, from process\ncontext where preemption is fully enabled. This triggers the following\nusing blktests/blktrace/002:\n\nblktrace/002 (blktrace ftrace corruption with sysfs trace)   [failed]\n    runtime  0.367s  ...  0.437s\n    something found in dmesg:\n    [   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n    [   81.239580] null_blk: disk nullb1 created\n    [   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n    [   81.362842] caller is tracing_record_cmdline+0x10/0x40\n    [   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n    [   81.362877] Tainted: [N]=TEST\n    [   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n    [   81.362881] Call Trace:\n    [   81.362884]  \u0026lt;TASK\u0026gt;\n    [   81.362886]  dump_stack_lvl+0x8d/0xb0\n    ...\n    (See \u0026apos;/mnt/sda/blktests/results/nodev/blktrace/002.dmesg\u0026apos; for the entire message)\n\n[   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n[   81.239580] null_blk: disk nullb1 created\n[   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n[   81.362842] caller is tracing_record_cmdline+0x10/0x40\n[   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n[   81.362877] Tainted: [N]=TEST\n[   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[   81.362881] Call Trace:\n[   81.362884]  \u0026lt;TASK\u0026gt;\n[   81.362886]  dump_stack_lvl+0x8d/0xb0\n[   81.362895]  check_preemption_disabled+0xce/0xe0\n[   81.362902]  tracing_record_cmdline+0x10/0x40\n[   81.362923]  __blk_add_trace+0x307/0x5d0\n[   81.362934]  ? lock_acquire+0xe0/0x300\n[   81.362940]  ? iov_iter_extract_pages+0x101/0xa30\n[   81.362959]  blk_add_trace_bio+0x106/0x1e0\n[   81.362968]  submit_bio_noacct_nocheck+0x24b/0x3a0\n[   81.362979]  ? lockdep_init_map_type+0x58/0x260\n[   81.362988]  submit_bio_wait+0x56/0x90\n[   81.363009]  __blkdev_direct_IO_simple+0x16c/0x250\n[   81.363026]  ? __pfx_submit_bio_wait_endio+0x10/0x10\n[   81.363038]  ? rcu_read_lock_any_held+0x73/0xa0\n[   81.363051]  blkdev_read_iter+0xc1/0x140\n[   81.363059]  vfs_read+0x20b/0x330\n[   81.363083]  ksys_read+0x67/0xe0\n[   81.363090]  do_syscall_64+0xbf/0xf00\n[   81.363102]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   81.363106] RIP: 0033:0x7f281906029d\n[   81.363111] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d 66 63 0a 00 e8 59 ff 01 00 66 0f 1f 84 00 00 00 00 00 80 3d 41 33 0e 00 00 74 17 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec\n[   81.363113] RSP: 002b:00007ffca127dd48 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\n[   81.363120] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f281906029d\n[   81.363122] RDX: 0000000000001000 RSI: 0000559f8bfae000 RDI: 0000000000000000\n[   81.363123] RBP: 0000000000001000 R08: 0000002863a10a81 R09: 00007f281915f000\n[   81.363124] R10: 00007f2818f77b60 R11: 0000000000000246 R12: 0000559f8bfae000\n[   81.363126] R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000a\n[   81.363142]  \u0026lt;/TASK\u0026gt;\n\nThe same BUG fires from blk_add_trace_plug(), blk_add_trace_unplug(),\nand blk_add_trace_rq() paths as well.\n\nThe purpose of tracin\n---truncated---(CVE-2026-23374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing\n\nstruct bpf_plt contains a u64 target field. Currently, the BPF JIT\nallocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT\nbuffer.\n\nBecause the base address of the JIT buffer can be 4-byte aligned (e.g.,\nending in 0x4 or 0xc), the relative padding logic in build_plt() fails\nto ensure that target lands on an 8-byte boundary.\n\nThis leads to two issues:\n1. UBSAN reports misaligned-access warnings when dereferencing the\n   structure.\n2. More critically, target is updated concurrently via WRITE_ONCE() in\n   bpf_arch_text_poke() while the JIT\u0026apos;d code executes ldr. On arm64,\n   64-bit loads/stores are only guaranteed to be single-copy atomic if\n   they are 64-bit aligned. A misaligned target risks a torn read,\n   causing the JIT to jump to a corrupted address.\n\nFix this by increasing the allocation alignment requirement to 8 bytes\n(sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of\nthe JIT buffer to an 8-byte boundary, allowing the relative padding math\nin build_plt() to correctly align the target field.(CVE-2026-23383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp: Fix wildcard bind conflict check when using hash2\n\nWhen binding a udp_sock to a local address and port, UDP uses\ntwo hashes (udptable-\u0026gt;hash and udptable-\u0026gt;hash2) for collision\ndetection. The current code switches to \u0026quot;hash2\u0026quot; when\nhslot-\u0026gt;count \u0026gt; 10.\n\n\u0026quot;hash2\u0026quot; is keyed by local address and local port.\n\u0026quot;hash\u0026quot; is keyed by local port only.\n\nThe issue can be shown in the following bind sequence (pseudo code):\n\nbind(fd1,  \u0026quot;[fd00::1]:8888\u0026quot;)\nbind(fd2,  \u0026quot;[fd00::2]:8888\u0026quot;)\nbind(fd3,  \u0026quot;[fd00::3]:8888\u0026quot;)\nbind(fd4,  \u0026quot;[fd00::4]:8888\u0026quot;)\nbind(fd5,  \u0026quot;[fd00::5]:8888\u0026quot;)\nbind(fd6,  \u0026quot;[fd00::6]:8888\u0026quot;)\nbind(fd7,  \u0026quot;[fd00::7]:8888\u0026quot;)\nbind(fd8,  \u0026quot;[fd00::8]:8888\u0026quot;)\nbind(fd9,  \u0026quot;[fd00::9]:8888\u0026quot;)\nbind(fd10, \u0026quot;[fd00::10]:8888\u0026quot;)\n\n/* Correctly return -EADDRINUSE because \u0026quot;hash\u0026quot; is used\n * instead of \u0026quot;hash2\u0026quot;. udp_lib_lport_inuse() detects the\n * conflict.\n */\nbind(fail_fd, \u0026quot;[::]:8888\u0026quot;)\n\n/* After one more socket is bound to \u0026quot;[fd00::11]:8888\u0026quot;,\n * hslot-\u0026gt;count exceeds 10 and \u0026quot;hash2\u0026quot; is used instead.\n */\nbind(fd11, \u0026quot;[fd00::11]:8888\u0026quot;)\nbind(fail_fd, \u0026quot;[::]:8888\u0026quot;)      /* succeeds unexpectedly */\n\nThe same issue applies to the IPv4 wildcard address \u0026quot;0.0.0.0\u0026quot;\nand the IPv4-mapped wildcard address \u0026quot;::ffff:0.0.0.0\u0026quot;. For\nexample, if there are existing sockets bound to\n\u0026quot;192.168.1.[1-11]:8888\u0026quot;, then binding \u0026quot;0.0.0.0:8888\u0026quot; or\n\u0026quot;[::ffff:0.0.0.0]:8888\u0026quot; can also miss the conflict when\nhslot-\u0026gt;count \u0026gt; 10.\n\nTCP inet_csk_get_port() already has the correct check in\ninet_use_bhash2_on_bind(). Rename it to\ninet_use_hash2_on_bind() and move it to inet_hashtables.h\nso udp.c can reuse it in this fix.(CVE-2026-31503)\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\nxfs: close crash window in attr dabtree inactivation\n\nWhen inactivating an inode with node-format extended attributes,\nxfs_attr3_node_inactive() invalidates all child leaf/node blocks via\nxfs_trans_binval(), but intentionally does not remove the corresponding\nentries from their parent node blocks.  The implicit assumption is that\nxfs_attr_inactive() will truncate the entire attr fork to zero extents\nafterwards, so log recovery will never reach the root node and follow\nthose stale pointers.\n\nHowever, if a log shutdown occurs after the leaf/node block cancellations\ncommit but before the attr bmap truncation commits, this assumption\nbreaks.  Recovery replays the attr bmap intact (the inode still has\nattr fork extents), but suppresses replay of all cancelled leaf/node\nblocks, maybe leaving them as stale data on disk.  On the next mount,\nxlog_recover_process_iunlinks() retries inactivation and attempts to\nread the root node via the attr bmap. If the root node was not replayed,\nreading the unreplayed root block triggers a metadata verification\nfailure immediately; if it was replayed, following its child pointers\nto unreplayed child blocks triggers the same failure:\n\n XFS (pmem0): Metadata corruption detected at\n xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78\n XFS (pmem0): Unmount and run xfs_repair\n XFS (pmem0): First 128 bytes of corrupted metadata buffer:\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n XFS (pmem0): metadata I/O error in \u0026quot;xfs_da_read_buf+0x104/0x190\u0026quot; at daddr 0x78 len 8 error 117\n\nFix this in two places:\n\nIn xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a\nchild block, immediately remove the entry that references it from the\nparent node in the same transaction.  This eliminates the window where\nthe parent holds a pointer to a cancelled block.  Once all children are\nremoved, the now-empty root node is converted to a leaf block within the\nsame transaction. This node-to-leaf conversion is necessary for crash\nsafety. If the system shutdown after the empty node is written to the\nlog but before the second-phase bmap truncation commits, log recovery\nwill attempt to verify the root block on disk. xfs_da3_node_verify()\ndoes not permit a node block with count == 0; such a block will fail\nverification and trigger a metadata corruption shutdown. on the other\nhand, leaf blocks are allowed to have this transient state.\n\nIn xfs_attr_inactive(), split the attr fork truncation into two explicit\nphases.  First, truncate all extents beyond the root block (the child\nextents whose parent references have already been removed above).\nSecond, invalidate the root block and truncate the attr bmap to zero in\na single transaction.  The two operations in the second phase must be\natomic: as long as the attr bmap has any non-zero length, recovery can\nfollow it to the root block, so the root block invalidation must commit\ntogether with the bmap-to-zero truncation.(CVE-2026-43053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Drain commands in target_reset handler\n\ntcm_loop_target_reset() violates the SCSI EH contract: it returns SUCCESS\nwithout draining any in-flight commands.  The SCSI EH documentation\n(scsi_eh.rst) requires that when a reset handler returns SUCCESS the driver\nhas made lower layers \u0026quot;forget about timed out scmds\u0026quot; and is ready for new\ncommands.  Every other SCSI LLD (virtio_scsi, mpt3sas, ipr, scsi_debug,\nmpi3mr) enforces this by draining or completing outstanding commands before\nreturning SUCCESS.\n\nBecause tcm_loop_target_reset() doesn\u0026apos;t drain, the SCSI EH reuses in-flight\nscsi_cmnd structures for recovery commands (e.g. TUR) while the target core\nstill has async completion work queued for the old se_cmd.  The memset in\nqueuecommand zeroes se_lun and lun_ref_active, causing\ntransport_lun_remove_cmd() to skip its percpu_ref_put().  The leaked LUN\nreference prevents transport_clear_lun_ref() from completing, hanging\nconfigfs LUN unlink forever in D-state:\n\n  INFO: task rm:264 blocked for more than 122 seconds.\n  rm              D    0   264    258 0x00004000\n  Call Trace:\n   __schedule+0x3d0/0x8e0\n   schedule+0x36/0xf0\n   transport_clear_lun_ref+0x78/0x90 [target_core_mod]\n   core_tpg_remove_lun+0x28/0xb0 [target_core_mod]\n   target_fabric_port_unlink+0x50/0x60 [target_core_mod]\n   configfs_unlink+0x156/0x1f0 [configfs]\n   vfs_unlink+0x109/0x290\n   do_unlinkat+0x1d5/0x2d0\n\nFix this by making tcm_loop_target_reset() actually drain commands:\n\n 1. Issue TMR_LUN_RESET via tcm_loop_issue_tmr() to drain all commands that\n    the target core knows about (those not yet CMD_T_COMPLETE).\n\n 2. Use blk_mq_tagset_busy_iter() to iterate all started requests and\n    flush_work() on each se_cmd — this drains any deferred completion work\n    for commands that already had CMD_T_COMPLETE set before the TMR (which\n    the TMR skips via __target_check_io_state()).  This is the same pattern\n    used by mpi3mr, scsi_debug, and libsas to drain outstanding commands\n    during reset.(CVE-2026-43054)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: correctly handle tunneled traffic on IPV6_CSUM GSO fallback\n\nNETIF_F_IPV6_CSUM only advertises support for checksum offload of\npackets without IPv6 extension headers. Packets with extension\nheaders must fall back onto software checksumming. Since TSO\ndepends on checksum offload, those must revert to GSO.\n\nThe below commit introduces that fallback. It always checks\nnetwork header length. For tunneled packets, the inner header length\nmust be checked instead. Extend the check accordingly.\n\nA special case is tunneled packets without inner IP protocol. Such as\nRFC 6951 SCTP in UDP. Those are not standard IPv6 followed by\ntransport header either, so also must revert to the software GSO path.(CVE-2026-43057)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: annotate data-races around hdev-\u0026gt;req_status\n\n__hci_cmd_sync_sk() sets hdev-\u0026gt;req_status under hdev-\u0026gt;req_lock:\n\n    hdev-\u0026gt;req_status = HCI_REQ_PEND;\n\nHowever, several other functions read or write hdev-\u0026gt;req_status without\nholding any lock:\n\n  - hci_send_cmd_sync() reads req_status in hci_cmd_work (workqueue)\n  - hci_cmd_sync_complete() reads/writes from HCI event completion\n  - hci_cmd_sync_cancel() / hci_cmd_sync_cancel_sync() read/write\n  - hci_abort_conn() reads in connection abort path\n\nSince __hci_cmd_sync_sk() runs on hdev-\u0026gt;req_workqueue while\nhci_send_cmd_sync() runs on hdev-\u0026gt;workqueue, these are different\nworkqueues that can execute concurrently on different CPUs. The plain\nC accesses constitute a data race.\n\nAdd READ_ONCE()/WRITE_ONCE() annotations on all concurrent accesses\nto hdev-\u0026gt;req_status to prevent potential compiler optimizations that\ncould affect correctness (e.g., load fusing in the wait_event\ncondition or store reordering).(CVE-2026-43119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: check return value of con2fb_acquire_newinfo()\n\nIf fbcon_open() fails when called from con2fb_acquire_newinfo() then\ninfo-\u0026gt;fbcon_par pointer remains NULL which is later dereferenced.\n\nAdd check for return value of the function con2fb_acquire_newinfo() to\navoid it.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2026-43123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ\n\nThis adds a check for encryption key size upon receiving\nL2CAP_LE_CONN_REQ which is required by L2CAP/LE/CFC/BV-15-C which\nexpects L2CAP_CR_LE_BAD_KEY_SIZE.(CVE-2026-43134)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\u0026quot;\n\nThis reverts commit 05703271c3cd (\u0026quot;PCI/IOV: Add PCI rescan-remove locking\nwhen enabling/disabling SR-IOV\u0026quot;), which causes a deadlock by recursively\ntaking pci_rescan_remove_lock when sriov_del_vfs() is called as part of\npci_stop_and_remove_bus_device(). For example with the following sequence\nof commands:\n\n  $ echo \u0026lt;NUM\u0026gt; \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/sriov_numvfs\n  $ echo 1 \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/remove\n\nA trimmed trace of the deadlock on a mlx5 device is as below:\n\n  zsh/5715 is trying to acquire lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140\n\n  but task is already holding lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80\n  ...\n  Call Trace:\n   [\u0026lt;00000259778c4f90\u0026gt;] dump_stack_lvl+0xc0/0x110\n   [\u0026lt;00000259779c844e\u0026gt;] print_deadlock_bug+0x31e/0x330\n   [\u0026lt;00000259779c1908\u0026gt;] __lock_acquire+0x16c8/0x32f0\n   [\u0026lt;00000259779bffac\u0026gt;] lock_acquire+0x14c/0x350\n   [\u0026lt;00000259789643a6\u0026gt;] __mutex_lock_common+0xe6/0x1520\n   [\u0026lt;000002597896413c\u0026gt;] mutex_lock_nested+0x3c/0x50\n   [\u0026lt;00000259784a07e4\u0026gt;] sriov_disable+0x34/0x140\n   [\u0026lt;00000258f7d6dd80\u0026gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]\n   [\u0026lt;00000258f7d5745e\u0026gt;] remove_one+0x5e/0xf0 [mlx5_core]\n   [\u0026lt;00000259784857fc\u0026gt;] pci_device_remove+0x3c/0xa0\n   [\u0026lt;000002597851012e\u0026gt;] device_release_driver_internal+0x18e/0x280\n   [\u0026lt;000002597847ae22\u0026gt;] pci_stop_bus_device+0x82/0xa0\n   [\u0026lt;000002597847afce\u0026gt;] pci_stop_and_remove_bus_device_locked+0x5e/0x80\n   [\u0026lt;00000259784972c2\u0026gt;] remove_store+0x72/0x90\n   [\u0026lt;0000025977e6661a\u0026gt;] kernfs_fop_write_iter+0x15a/0x200\n   [\u0026lt;0000025977d7241c\u0026gt;] vfs_write+0x24c/0x300\n   [\u0026lt;0000025977d72696\u0026gt;] ksys_write+0x86/0x110\n   [\u0026lt;000002597895b61c\u0026gt;] __do_syscall+0x14c/0x400\n   [\u0026lt;000002597896e0ee\u0026gt;] system_call+0x6e/0x90\n\nThis alone is not a complete fix as it restores the issue the cited commit\ntried to solve. A new fix will be provided as a follow on.(CVE-2026-43147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: gadget: Move vbus draw to workqueue context\n\nCurrently dwc3_gadget_vbus_draw() can be called from atomic\ncontext, which in turn invokes power-supply-core APIs. And\nsome these PMIC APIs have operations that may sleep, leading\nto kernel panic.\n\nFix this by moving the vbus_draw into a workqueue context.(CVE-2026-43170)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: pvrusb2: fix URB leak in pvr2_send_request_ex\n\nWhen pvr2_send_request_ex() submits a write URB successfully but fails to\nsubmit the read URB (e.g. returns -ENOMEM), it returns immediately without\nwaiting for the write URB to complete. Since the driver reuses the same\nURB structure, a subsequent call to pvr2_send_request_ex() attempts to\nsubmit the still-active write URB, triggering a \u0026apos;URB submitted while\nactive\u0026apos; warning in usb_submit_urb().\n\nFix this by ensuring the write URB is unlinked and waited upon if the read\nURB submission fails.(CVE-2026-43223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: Add support for TSV110 Spectre-BHB mitigation\n\nThe TSV110 processor is vulnerable to the Spectre-BHB (Branch History\nBuffer) attack, which can be exploited to leak information through\nbranch prediction side channels. This commit adds the MIDR of TSV110\nto the list for software mitigation.(CVE-2026-43261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkexec: derive purgatory entry from symbol\n\nkexec_load_purgatory() derives image-\u0026gt;start by locating e_entry inside an\nSHF_EXECINSTR section.  If the purgatory object contains multiple\nexecutable sections with overlapping sh_addr, the entrypoint check can\nmatch more than once and trigger a WARN.\n\nDerive the entry section from the purgatory_start symbol when present and\ncompute image-\u0026gt;start from its final placement.  Keep the existing e_entry\nfallback for purgatories that do not expose the symbol.\n\nWARNING: kernel/kexec_file.c:1009 at kexec_load_purgatory+0x395/0x3c0, CPU#10: kexec/1784\nCall Trace:\n \u0026lt;TASK\u0026gt;\n bzImage64_load+0x133/0xa00\n __do_sys_kexec_file_load+0x2b3/0x5c0\n do_syscall_64+0x81/0x610\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n[(CVE-2026-43289)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Fix die ID init and look up bugs\n\nIn snbep_pci2phy_map_init(), in the nr_node_ids \u0026gt; 8 path,\nuncore_device_to_die() may return -1 when all CPUs associated\nwith the UBOX device are offline.\n\nRemove the WARN_ON_ONCE(die_id == -1) check for two reasons:\n\n- The current code breaks out of the loop. This is incorrect because\n  pci_get_device() does not guarantee iteration in domain or bus order,\n  so additional UBOX devices may be skipped during the scan.\n\n- Returning -EINVAL is incorrect, since marking offline buses with\n  die_id == -1 is expected and should not be treated as an error.\n\nSeparately, when NUMA is disabled on a NUMA-capable platform,\npcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die()\nto return -1 for all PCI devices.  As a result,\nspr_update_device_location(), used on Intel SPR and EMR, ignores the\ncorresponding PMON units and does not add them to the RB tree.\n\nFix this by using uncore_pcibus_to_dieid(), which retrieves topology\nfrom the UBOX GIDNIDMAP register and works regardless of whether NUMA\nis enabled in Linux.  This requires snbep_pci2phy_map_init() to be\nadded in spr_uncore_pci_init().\n\nKeep uncore_device_to_die() only for the nr_node_ids \u0026gt; 8 case, where\nNUMA is expected to be enabled.(CVE-2026-43344)\n\nThe Linux kernel Nouveau graphics driver has a race condition/null pointer dereference issue in DPCD (DisplayPort Configuration Data) AUX channel transmission processing. When the GPU device enters the suspend state due to runtime power management (runtime PM), if the user space program (such as through the /dev/drm_dp_ interface) attempts to initiate an AUX transfer request, the driver will try to access the GSP (Graphics System Processor) firmware code of the suspended device, causing the kernel to crash.(CVE-2026-43381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: add a bunch of missing ceph_path_info initializers\n\nceph_mdsc_build_path() must be called with a zero-initialized\nceph_path_info parameter, or else the following\nceph_mdsc_free_path_info() may crash.\n\nExample crash (on Linux 6.18.12):\n\n  virt_to_cache: Object is not a Slab page!\n  WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6732 kmem_cache_free+0x316/0x400\n  [...]\n  Call Trace:\n   [...]\n   ceph_open+0x13d/0x3e0\n   do_dentry_open+0x134/0x480\n   vfs_open+0x2a/0xe0\n   path_openat+0x9a3/0x1160\n  [...]\n  cache_from_obj: Wrong slab cache. names_cache but object is from ceph_inode_info\n  WARNING: CPU: 184 PID: 2871736 at mm/slub.c:6746 kmem_cache_free+0x2dd/0x400\n  [...]\n  kernel BUG at mm/slub.c:634!\n  Oops: invalid opcode: 0000 [#1] SMP NOPTI\n  RIP: 0010:__slab_free+0x1a4/0x350\n\nSome of the ceph_mdsc_build_path() callers had initializers, but\nothers had not, even though they were all added by commit 15f519e9f883\n(\u0026quot;ceph: fix race condition validating r_parent before applying state\u0026quot;).\nThe ones without initializer are suspectible to random crashes.  (I can\nimagine it could even be possible to exploit this bug to elevate\nprivileges.)\n\nUnfortunately, these Ceph functions are undocumented and its semantics\ncan only be derived from the code.  I see that ceph_mdsc_build_path()\ninitializes the structure only on success, but not on error.\n\nCalling ceph_mdsc_free_path_info() after a failed\nceph_mdsc_build_path() call does not even make sense, but that\u0026apos;s what\nall callers do, and for it to be safe, the structure must be\nzero-initialized.  The least intrusive approach to fix this is\ntherefore to add initializers everywhere.(CVE-2026-43408)\n\nIn the Linux kernel, the following vulnerability has been resolved: powerpc, perf: Check that current-\u0026gt;mm is alive before getting user callchain. It may happen that mm is already released, which leads to kernel panic. This adds the NULL check for current-\u0026gt;mm, similarly to commit 20afc60f892d (\u0026quot;x86, perf: Check that current-\u0026gt;mm is alive before getting user callchain\u0026quot;). I was getting this panic when running a profiling BPF program (profile.py from bcc-tools). In addition, move storing the top-level stack entry to generic perf_callchain_user to make sure the top-level entry is always captured, even if current-\u0026gt;mm is NULL.(CVE-2026-43416)\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\nnfs: return EISDIR on nfs3_proc_create if d_alias is a dir\n\nIf we found an alias through nfs3_do_create/nfs_add_or_obtain\n/d_splice_alias which happens to be a dir dentry, we don\u0026apos;t return\nany error, and simply forget about this alias, but the original\ndentry we were adding and passed as parameter remains negative.\n\nThis later causes an oops on nfs_atomic_open_v23/finish_open since we\nsupply a negative dentry to do_dentry_open.\n\nThis has been observed running lustre-racer, where dirs and files are\ncreated/removed concurrently with the same name and O_EXCL is not\nused to open files (frequent file redirection).\n\nWhile d_splice_alias typically returns a directory alias or NULL, we\nexplicitly check d_is_dir() to ensure that we don\u0026apos;t attempt to perform\nfile operations (like finish_open) on a directory inode, which triggers\nthe observed oops.(CVE-2026-43470)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nunshare: fix unshare_fs() handling\n\nThere\u0026apos;s an unpleasant corner case in unshare(2), when we have a\nCLONE_NEWNS in flags and current-\u0026gt;fs hadn\u0026apos;t been shared at all; in that\ncase copy_mnt_ns() gets passed current-\u0026gt;fs instead of a private copy,\nwhich causes interesting warts in proof of correctness]\n\n\u0026gt; I guess if private means fs-\u0026gt;users == 1, the condition could still be true.\n\nUnfortunately, it\u0026apos;s worse than just a convoluted proof of correctness.\nConsider the case when we have CLONE_NEWCGROUP in addition to CLONE_NEWNS\n(and current-\u0026gt;fs-\u0026gt;users == 1).\n\nWe pass current-\u0026gt;fs to copy_mnt_ns(), all right.  Suppose it succeeds and\nflips current-\u0026gt;fs-\u0026gt;{pwd,root} to corresponding locations in the new namespace.\nNow we proceed to copy_cgroup_ns(), which fails (e.g. with -ENOMEM).\nWe call put_mnt_ns() on the namespace created by copy_mnt_ns(), it\u0026apos;s\ndestroyed and its mount tree is dissolved, but...  current-\u0026gt;fs-\u0026gt;root and\ncurrent-\u0026gt;fs-\u0026gt;pwd are both left pointing to now detached mounts.\n\nThey are pinning those, so it\u0026apos;s not a UAF, but it leaves the calling\nprocess with unshare(2) failing with -ENOMEM _and_ leaving it with\npwd and root on detached isolated mounts.  The last part is clearly a bug.\n\nThere is other fun related to that mess (races with pivot_root(), including\nthe one between pivot_root() and fork(), of all things), but this one\nis easy to isolate and fix - treat CLONE_NEWNS as \u0026quot;allocate a new\nfs_struct even if it hadn\u0026apos;t been shared in the first place\u0026quot;.  Sure, we could\ngo for something like \u0026quot;if both CLONE_NEWNS *and* one of the things that might\nend up failing after copy_mnt_ns() call in create_new_namespaces() are set,\nforce allocation of new fs_struct\u0026quot;, but let\u0026apos;s keep it simple - the cost\nof copy_fs_struct() is trivial.\n\nAnother benefit is that copy_mnt_ns() with CLONE_NEWNS *always* gets\na freshly allocated fs_struct, yet to be attached to anything.  That\nseriously simplifies the analysis...\n\nFWIW, that bug had been there since the introduction of unshare(2) ;-/(CVE-2026-43472)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated\n\nExplicitly set/clear CR8 write interception when AVIC is (de)activated to\nfix a bug where KVM leaves the interception enabled after AVIC is\nactivated.  E.g. if KVM emulates INIT=\u0026gt;WFS while AVIC is deactivated, CR8\nwill remain intercepted in perpetuity.\n\nOn its own, the dangling CR8 intercept is \u0026quot;just\u0026quot; a performance issue, but\ncombined with the TPR sync bug fixed by commit d02e48830e3f (\u0026quot;KVM: SVM:\nSync TPR from LAPIC into VMCB::V_TPR even if AVIC is active\u0026quot;), the danging\nintercept is fatal to Windows guests as the TPR seen by hardware gets\nwildly out of sync with reality.\n\nNote, VMX isn\u0026apos;t affected by the bug as TPR_THRESHOLD is explicitly ignored\nwhen Virtual Interrupt Delivery is enabled, i.e. when APICv is active in\nKVM\u0026apos;s world.  I.e. there\u0026apos;s no need to trigger update_cr8_intercept(), this\nis firmly an SVM implementation flaw/detail.\n\nWARN if KVM gets a CR8 write #VMEXIT while AVIC is active, as KVM should\nnever enter the guest with AVIC enabled and CR8 writes intercepted.\n\n[Squash fix to avic_deactivate_vmcb. - Paolo](CVE-2026-43483)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl()\n\nYiming reports an integer underflow in mpi_read_raw_from_sgl() when\nsubtracting \u0026quot;lzeros\u0026quot; from the unsigned \u0026quot;nbytes\u0026quot;.\n\nFor this to happen, the scatterlist \u0026quot;sgl\u0026quot; needs to occupy more bytes\nthan the \u0026quot;nbytes\u0026quot; parameter and the first \u0026quot;nbytes + 1\u0026quot; bytes of the\nscatterlist must be zero.  Under these conditions, the while loop\niterating over the scatterlist will count more zeroes than \u0026quot;nbytes\u0026quot;,\nsubtract the number of zeroes from \u0026quot;nbytes\u0026quot; and cause the underflow.\n\nWhen commit 2d4d1eea540b (\u0026quot;lib/mpi: Add mpi sgl helpers\u0026quot;) originally\nintroduced the bug, it couldn\u0026apos;t be triggered because all callers of\nmpi_read_raw_from_sgl() passed a scatterlist whose length was equal to\n\u0026quot;nbytes\u0026quot;.\n\nHowever since commit 63ba4d67594a (\u0026quot;KEYS: asymmetric: Use new crypto\ninterface without scatterlists\u0026quot;), the underflow can now actually be\ntriggered.  When invoking a KEYCTL_PKEY_ENCRYPT system call with a\nlarger \u0026quot;out_len\u0026quot; than \u0026quot;in_len\u0026quot; and filling the \u0026quot;in\u0026quot; buffer with zeroes,\ncrypto_akcipher_sync_prep() will create an all-zero scatterlist used for\nboth the \u0026quot;src\u0026quot; and \u0026quot;dst\u0026quot; member of struct akcipher_request and thereby\nfulfil the conditions to trigger the bug:\n\n  sys_keyctl()\n    keyctl_pkey_e_d_s()\n      asymmetric_key_eds_op()\n        software_key_eds_op()\n          crypto_akcipher_sync_encrypt()\n            crypto_akcipher_sync_prep()\n              crypto_akcipher_encrypt()\n                rsa_enc()\n                  mpi_read_raw_from_sgl()\n\nTo the user this will be visible as a DoS as the kernel spins forever,\ncausing soft lockup splats as a side effect.\n\nFix it.(CVE-2026-43492)","status":"published","published":"2026-05-29T11:11:26Z","modified":"2026-08-18T01:20:01.365144884Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"OESA-2026-3704","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: 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\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\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim\n\nThe root cause of this bug is that when \u0026apos;bpf_link_put\u0026apos; reduces the\nrefcount of \u0026apos;shim_link-\u0026gt;link.link\u0026apos; to zero, the resource is considered\nreleased but may still be referenced via \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;cgroup_shim_find\u0026apos;. The actual cleanup of \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;bpf_shim_tramp_link_release\u0026apos; is deferred. During this window, another\nprocess can cause a use-after-free via \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n\nBased on Martin KaFai Lau\u0026apos;s suggestions, I have created a simple patch.\n\nTo fix this:\n   Add an atomic non-zero check in \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n   Only increment the refcount if it is not already zero.\n\nTesting:\n   I verified the fix by adding a delay in\n   \u0026apos;bpf_shim_tramp_link_release\u0026apos; to make the bug easier to trigger:\n\nstatic void bpf_shim_tramp_link_release(struct bpf_link *link)\n{\n\t/* ... */\n\tif (!shim_link-\u0026gt;trampoline)\n\t\treturn;\n\n+\tmsleep(100);\n\tWARN_ON_ONCE(bpf_trampoline_unlink_prog(\u0026amp;shim_link-\u0026gt;link,\n\t\tshim_link-\u0026gt;trampoline, NULL));\n\tbpf_trampoline_put(shim_link-\u0026gt;trampoline);\n}\n\nBefore the patch, running a PoC easily reproduced the crash(almost 100%)\nwith a call trace similar to KaiyanM\u0026apos;s report.\nAfter the patch, the bug no longer occurs even after millions of\niterations.(CVE-2026-23319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stack-out-of-bounds write in devmap\n\nget_upper_ifindexes() iterates over all upper devices and writes their\nindices into an array without checking bounds.\n\nAlso the callers assume that the max number of upper devices is\nMAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack,\nbut that assumption is not correct and the number of upper devices could\nbe larger than MAX_NEST_DEV (e.g., many macvlans), causing a\nstack-out-of-bounds write.\n\nAdd a max parameter to get_upper_ifindexes() to avoid the issue.\nWhen there are too many upper devices, return -EOVERFLOW and abort the\nredirect.\n\nTo reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with\nan XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS.\nThen send a packet to the device to trigger the XDP redirect path.(CVE-2026-23359)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing\n\nstruct bpf_plt contains a u64 target field. Currently, the BPF JIT\nallocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT\nbuffer.\n\nBecause the base address of the JIT buffer can be 4-byte aligned (e.g.,\nending in 0x4 or 0xc), the relative padding logic in build_plt() fails\nto ensure that target lands on an 8-byte boundary.\n\nThis leads to two issues:\n1. UBSAN reports misaligned-access warnings when dereferencing the\n   structure.\n2. More critically, target is updated concurrently via WRITE_ONCE() in\n   bpf_arch_text_poke() while the JIT\u0026apos;d code executes ldr. On arm64,\n   64-bit loads/stores are only guaranteed to be single-copy atomic if\n   they are 64-bit aligned. A misaligned target risks a torn read,\n   causing the JIT to jump to a corrupted address.\n\nFix this by increasing the allocation alignment requirement to 8 bytes\n(sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of\nthe JIT buffer to an 8-byte boundary, allowing the relative padding math\nin build_plt() to correctly align the target field.(CVE-2026-23383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: check metadata block offset is within range\n\nSyzkaller reports a \u0026quot;general protection fault in squashfs_copy_data\u0026quot;\n\nThis is ultimately caused by a corrupted index look-up table, which\nproduces a negative metadata block offset.\n\nThis is subsequently passed to squashfs_copy_data (via\nsquashfs_read_metadata) where the negative offset causes an out of bounds\naccess.\n\nThe fix is to check that the offset is within range in\nsquashfs_read_metadata.  This will trap this and other cases.(CVE-2026-23388)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl\n\nWhen page reassignment was added to af_alg_pull_tsgl the original\nloop wasn\u0026apos;t updated so it may try to reassign one more page than\nnecessary.\n\nAdd the check to the reassignment so that this does not happen.\n\nAlso update the comment which still refers to the obsolete offset\nargument.(CVE-2026-43078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: algif_aead - snapshot IV for async AEAD requests\n\nAF_ALG AEAD AIO requests currently use the socket-wide IV buffer during\nrequest processing.  For async requests, later socket activity can\nupdate that shared state before the original request has fully\ncompleted, which can lead to inconsistent IV handling.\n\nSnapshot the IV into per-request storage when preparing the AEAD\nrequest, so in-flight operations no longer depend on mutable socket\nstate.(CVE-2026-46028)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/fair: Clear rel_deadline when initializing forked entities\n\nA yield-triggered crash can happen when a newly forked sched_entity\nenters the fair class with se-\u0026gt;rel_deadline unexpectedly set.\n\nThe failing sequence is:\n\n  1. A task is forked while se-\u0026gt;rel_deadline is still set.\n  2. __sched_fork() initializes vruntime, vlag and other sched_entity\n     state, but does not clear rel_deadline.\n  3. On the first enqueue, enqueue_entity() calls place_entity().\n  4. Because se-\u0026gt;rel_deadline is set, place_entity() treats se-\u0026gt;deadline\n     as a relative deadline and converts it to an absolute deadline by\n     adding the current vruntime.\n  5. However, the forked entity\u0026apos;s deadline is not a valid inherited\n     relative deadline for this new scheduling instance, so the conversion\n     produces an abnormally large deadline.\n  6. If the task later calls sched_yield(), yield_task_fair() advances\n     se-\u0026gt;vruntime to se-\u0026gt;deadline.\n  7. The inflated vruntime is then used by the following enqueue path,\n     where the vruntime-derived key can overflow when multiplied by the\n     entity weight.\n  8. This corrupts cfs_rq-\u0026gt;sum_w_vruntime, breaks EEVDF eligibility\n     calculation, and can eventually make all entities appear ineligible.\n     pick_next_entity() may then return NULL unexpectedly, leading to a\n     later NULL dereference.\n\nA captured trace shows the effect clearly. Before yield, the entity\u0026apos;s\nvruntime was around:\n\n  9834017729983308\n\nAfter yield_task_fair() executed:\n\n  se-\u0026gt;vruntime = se-\u0026gt;deadline\n\nthe vruntime jumped to:\n\n  19668035460670230\n\nand the deadline was later advanced further to:\n\n  19668035463470230\n\nThis shows that the deadline had already become abnormally large before\nyield_task_fair() copied it into vruntime.\n\nrel_deadline is only meaningful when se-\u0026gt;deadline really carries a\nrelative deadline that still needs to be placed against vruntime. A\nfreshly forked sched_entity should not inherit or retain this state.\nClear se-\u0026gt;rel_deadline in __sched_fork(), together with the other\nsched_entity runtime state, so that the first enqueue does not interpret\nthe new entity\u0026apos;s deadline as a stale relative deadline.(CVE-2026-52980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/sec2 - prevent req used-after-free for sec\n\nDuring packet transmission, if the system is under heavy load,\nthe hardware might complete processing the packet and free the\nrequest memory (req) before the transmission function finishes.\nIf the software subsequently accesses this req, a use-after-free\nerror will occur. The qp_ctx memory exists throughout the packet\nsending process, so replace the req with the qp_ctx.(CVE-2026-53055)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: validate cached peer INIT chunk length in COOKIE_ECHO processing\n\nWhen a listening SCTP server processes a COOKIE_ECHO chunk, the cached\npeer INIT chunk embedded after the cookie is parsed and its parameters\nare later walked by sctp_process_init() using sctp_walk_params().\n\nHowever, the chunk header length of this cached INIT chunk was not\nvalidated against the remaining buffer in the COOKIE_ECHO payload. If\nthe length field is inflated, the parameter walk can run beyond the\nactual received data, leading to out-of-bounds reads and potential\nmemory corruption during later parameter handling (e.g. STATE_COOKIE\nprocessing and kmemdup() copies).\n\nAdd a bounds check in sctp_unpack_cookie() to ensure the cached INIT\nchunk length does not exceed the available data in the COOKIE_ECHO\nbuffer before it is used.(CVE-2026-53246)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250_dw: unregister 8250 port if clk_notifier_register() fails\n\ndw8250_probe() registers the 8250 port via serial8250_register_8250_port()\nand then, if the device has a clock, registers a clock notifier. If\nclk_notifier_register() fails, probe returns the error but leaves the\n8250 port registered. The matching serial8250_unregister_port() lives\nin dw8250_remove(), which is not called when probe fails, so the port\nslot stays occupied until the device is rebound or the system is\nrebooted. The devm-allocated driver data is freed while the port still\nreferences it (via the saved private_data and serial_in/serial_out\ncallbacks), so any access to that port slot before a rebind is a\nuse-after-free hazard.\n\nUnregister the port on the clk_notifier_register() error path.(CVE-2026-53384)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix use-after-free in pnfs_update_layout()\n\nWhen hitting the NFS_LAYOUT_RETURN branch in pnfs_update_layout(),\nthe code calls pnfs_prepare_to_retry_layoutget(lo). If it succeeds,\npnfs_put_layout_hdr(lo) is called before trace_pnfs_update_layout(),\nwhich still references \u0026apos;lo\u0026apos;. This results in a use-after-free when the\ntracepoint accesses lo\u0026apos;s fields.\n\nFix this by moving the tracepoint call before pnfs_put_layout_hdr(lo).(CVE-2026-63800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skmsg: preserve sg.copy across SG transforms\n\nThe sk_msg sg.copy bitmap is part of the scatterlist entry ownership\nstate. A set bit tells sk_msg_compute_data_pointers() not to expose the\nentry through writable BPF ctx-\u0026gt;data. This protects entries backed by\npages that are not private to the sk_msg, such as splice-backed file\npage-cache pages.\n\nSeveral sk_msg transform paths move, copy, split, or compact\nmsg-\u0026gt;sg.data[] entries without moving the matching sg.copy bit. This can\nmake an externally backed entry arrive at a new slot with a clear copy\nbit. A later SK_MSG verdict can then expose sg_virt(sge) as writable\nctx-\u0026gt;data and BPF stores can modify the original page cache.\n\nKeep sg.copy synchronized with sg.data[] whenever entries are\ntransferred, shifted, split, or copied into a new sk_msg. Clear the bit\nwhen an entry is replaced by a newly allocated private page or freed.\nThis covers the BPF pull/push/pop helpers, sk_msg_shift_left/right(),\nsk_msg_xfer(), and tls_split_open_record(), including the partial tail\nentry created during TLS open-record splitting.(CVE-2026-63830)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Validate CHAP_R length before base64 decode\n\nchap_server_compute_hash() allocates client_digest as\nkzalloc(chap-\u0026gt;digest_size) and then, for BASE64-encoded responses,\npasses chap_r directly to chap_base64_decode() without checking whether\nthe input length could produce more than digest_size bytes of output.\n\nchap_base64_decode() writes to the destination unconditionally as long\nas there is input to consume. With MAX_RESPONSE_LENGTH set to 128 and\nthe \u0026quot;0b\u0026quot; prefix stripped by extract_param(), up to 127 base64 characters\ncan reach the decoder. 127 characters decode to 95 bytes. For SHA-256\n(digest_size=32) this overflows client_digest by 63 bytes; for MD5\n(digest_size=16) the overflow is 79 bytes.\n\nThe length check at line 344 fires after the write has already happened.\n\nThe HEX branch in the same switch statement already validates the length\nup front. Apply the same approach to the BASE64 branch: strip trailing\nbase64 padding characters, then reject any input whose data length\nexceeds DIV_ROUND_UP(digest_size * 4, 3) before calling the decoder.\n\nStripping trailing \u0026apos;=\u0026apos; before the comparison handles both padded and\nunpadded encodings. chap_base64_decode() already returns early on \u0026apos;=\u0026apos;,\nso the full original string is still passed to the decoder unchanged.\n\nThe mutual CHAP path decodes CHAP_C into initiatorchg_binhex, which is\nkzalloc(CHAP_CHALLENGE_STR_LEN). extract_param() caps initiatorchg at\nCHAP_CHALLENGE_STR_LEN characters, so at most CHAP_CHALLENGE_STR_LEN-1\nbase64 characters reach the decoder. The maximum decoded size,\nDIV_ROUND_UP((CHAP_CHALLENGE_STR_LEN-1) * 3, 4), is less than\nCHAP_CHALLENGE_STR_LEN, so no overflow is possible there. A comment is\nadded at the call site to document this.(CVE-2026-63886)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf\n\niscsi_encode_text_output() concatenates \u0026quot;key=value\\0\u0026quot; records into\nlogin-\u0026gt;rsp_buf, an 8192-byte kzalloc(MAX_KEY_VALUE_PAIRS) buffer\nallocated in iscsit_alloc_login_setup_buffer(). The three sprintf() call\nsites in this function (lines 1398, 1411, 1424 in v7.1-rc2) never check\nthe remaining buffer capacity:\n\n\t*length += sprintf(output_buf, \u0026quot;%s=%s\u0026quot;, er-\u0026gt;key, er-\u0026gt;value);\n\t*length += 1;\n\toutput_buf = textbuf + *length;\n\nThe 8192-byte ceiling at iscsi_target_check_login_request() bounds the\n*input* Login PDU payload, but a single PDU can carry up to 2048 minimal\nfour-byte \u0026quot;a=b\\0\u0026quot; pairs, each unknown key expanding to a 16-byte\n\u0026quot;a=NotUnderstood\\0\u0026quot; output record via iscsi_add_notunderstood_response().\n2048 * 16 = 32 KiB of output into an 8 KiB buffer, producing a ~24 KiB\nheap overrun in the kmalloc-8k slab.\n\nThe fix introduces a static iscsi_encode_text_record() helper that uses\nsnprintf() with a per-call bounds check against the remaining buffer,\nand threads a u32 textbuf_size parameter through\niscsi_encode_text_output(). Both call sites in\niscsi_target_handle_csg_zero() (PHASE_SECURITY) and\niscsi_target_handle_csg_one() (PHASE_OPERATIONAL) pass\nMAX_KEY_VALUE_PAIRS. On overflow the encoder logs the condition, calls\niscsi_release_extra_responses() to drop queued records, and returns -1;\nboth caller sites now emit ISCSI_STATUS_CLS_INITIATOR_ERR /\nISCSI_LOGIN_STATUS_INIT_ERR via iscsit_tx_login_rsp() before returning,\nso the initiator sees an explicit failed-login response rather than a\nsilent connection drop. (Prior to this patch only the PHASE_OPERATIONAL\ncaller did that; the PHASE_SECURITY caller is converted to the same\nshape.)(CVE-2026-63887)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()\n\nTwo latent bugs in the Text-phase handler, both present since the\noriginal LIO integration in commit e48354ce078c (\u0026quot;iscsi-target: Add\niSCSI fabric support for target v4.1\u0026quot;):\n\n1) DataDigest CRC buffer overread (4 bytes past text_in).\n\n   text_in is kzalloc()\u0026apos;d at ALIGN(payload_length, 4).  rx_size is then\n   incremented by ISCSI_CRC_LEN to make room for the received DataDigest\n   in the iovec, but the same (now-bumped) rx_size is passed as the\n   buffer length to iscsit_crc_buf():\n\n       if (conn-\u0026gt;conn_ops-\u0026gt;DataDigest) {\n               ...\n               rx_size += ISCSI_CRC_LEN;\n       }\n       ...\n       if (conn-\u0026gt;conn_ops-\u0026gt;DataDigest) {\n               data_crc = iscsit_crc_buf(text_in, rx_size, 0, NULL);\n\n   iscsit_crc_buf() walks rx_size bytes of text_in with crc32c(), so\n   when DataDigest is negotiated it reads 4 bytes past the end of the\n   text_in allocation.  KASAN reproduces this directly on the unpatched\n   mainline tree as slab-out-of-bounds in crc32c() called from the Text\n   PDU path.  The OOB bytes feed crc32c() and are then compared against\n   the initiator-supplied checksum, so the value does not flow back to\n   the attacker, but the kernel does read past the buffer on every Text\n   PDU with DataDigest=CRC32C.\n\n   Fix by passing the actual padded payload length\n   (ALIGN(payload_length, 4)) that was used for the kzalloc().\n\n2) Stale cmd-\u0026gt;text_in_ptr re-free (double-free) on ERL\u0026gt;0 bad DataDigest\n   drop.\n\n   On DataDigest mismatch with ErrorRecoveryLevel \u0026gt; 0 the handler\n   silently drops the PDU and lets the initiator plug the CmdSN gap:\n\n               kfree(text_in);\n               return 0;\n\n   cmd-\u0026gt;text_in_ptr still points at the freed buffer.  The next Text\n   Request on the same ITT re-enters iscsit_setup_text_cmd(), which\n   unconditionally does\n\n       kfree(cmd-\u0026gt;text_in_ptr);\n       cmd-\u0026gt;text_in_ptr = NULL;\n\n   freeing the same pointer a second time.  Session teardown via\n   iscsit_release_cmd() has the same shape and hits the same double-free\n   if the connection is dropped before a second Text Request arrives.\n\n   On an unmodified mainline tree the bug-1 CRC overread fires first on\n   the initial valid Text Request and perturbs the subsequent state, so\n   #4 was isolated by building a kernel with only the bug-1 hunk of this\n   patch applied plus temporary printk() observability around the three\n   relevant kfree() sites.  The observability prints are not part of\n   this patch.  On that build, a three-PDU Text Request sequence after\n   login produces two back-to-back splats:\n\n       BUG: KASAN: double-free in iscsit_setup_text_cmd+0x??\n       BUG: KASAN: double-free in iscsit_release_cmd+0x??\n\n   showing the same pointer freed in the ERL\u0026gt;0 drop path and again in\n   iscsit_setup_text_cmd() (next Text Request on the same ITT) and once\n   more in iscsit_release_cmd() (session teardown).  On distro kernels\n   with CONFIG_SLAB_FREELIST_HARDENED=y (default) the double-free\n   becomes a remote kernel BUG(); on non-hardened kernels it corrupts\n   the slab freelist.\n\n   Fix by clearing cmd-\u0026gt;text_in_ptr after the kfree() in the ERL\u0026gt;0 drop\n   path.  With both hunks applied #4 is directly observable on the stock\n   tree without observability printks; fixing bug-1 alone would mask #4\n   less, not more, so the hunks are submitted together.\n\nBoth fixes are one-liners.  The Text PDU state machine is unchanged and\nthe wire protocol is unaffected.(CVE-2026-63888)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: scsi_transport_fc: Widen FPIN pname walker counter to u32\n\nAn adjacent Fibre Channel fabric actor that can deliver an FPIN ELS\nframe to an lpfc or qla2xxx Linux initiator can trigger a non-return in\nthe generic FC transport. This is not a local userspace or IP network\npath; the attacker must be able to inject fabric traffic, for example as\na compromised switch or fabric controller, or as a same-zone N_Port on a\nfabric that permits source spoofing.\n\nThe Link-Integrity and Peer-Congestion FPIN walkers used a u8 loop\ncounter against the 32-bit on-wire pname_count field, and did not bound\npname_count by the descriptor body already validated by the TLV walker.\nA pname_count of 256 therefore wraps the counter and keeps the loop\ncondition true indefinitely.\n\nFactor the shared pname_list[] walk into one helper, widen the counter\nto u32, and clamp pname_count against the entries that fit in the\ndescriptor body before iterating.(CVE-2026-63889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nthunderbolt: property: Cap recursion depth in __tb_property_parse_dir()\n\nA DIRECTORY entry\u0026apos;s value field is used as the dir_offset for a\nrecursive call into __tb_property_parse_dir() with no depth counter.\nA crafted peer that chains DIRECTORY entries into a back-reference\nloop drives the parser until the kernel stack is exhausted and the\nguard page fires.  Any untrusted XDomain peer (cable, dock, in-line\ninspector, adjacent host) that reaches the PROPERTIES_REQUEST\ncontrol-plane exchange can trigger this without authentication.\n\nThread a depth counter through tb_property_parse() and\n__tb_property_parse_dir(), and reject blocks that exceed\nTB_PROPERTY_MAX_DEPTH = 8.  That is comfortably larger than any\nobserved legitimate XDomain layout.\n\nOperators who do not need XDomain host-to-host discovery can disable\nthe path entirely with thunderbolt.xdomain=0 on the kernel command\nline.(CVE-2026-63891)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: mct_u232: fix memory corruption with small endpoint\n\nThe driver overrides the maximum transfer size for a specific device\nwhich only accepts 16 byte packets for its 32 byte bulk-out endpoint.\n\nMake sure to never increase the maximum transfer size to prevent slab\ncorruption should a malicious device report a smaller endpoint max\npacket size than expected.(CVE-2026-63898)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: mxuport: fix memory corruption with small endpoint\n\nMake sure that the bulk-out endpoint max packet size is at least eight\nbytes to avoid user-controlled slab corruption should a malicious device\nreport a smaller size.(CVE-2026-63899)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: digi_acceleport: fix memory corruption with small endpoints\n\nAdd the missing bulk-out buffer size sanity checks to avoid\nout-of-bounds memory accesses or slab corruption should a malicious\ndevice report smaller buffers than expected.(CVE-2026-63901)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: esp: restore combined single-frag length gate\n\nThe ESP out-of-place fast path appends the trailer in esp_output_head()\nbefore esp_output_tail() allocates the destination page frag. The\nhead-side gate currently checks skb-\u0026gt;data_len and tailen separately, but\nthe tail code allocates a single destination frag from the combined\npost-trailer skb-\u0026gt;data_len.\n\nReject the page-frag fast path when the combined aligned length exceeds a\npage. Otherwise skb_page_frag_refill() may fall back to a single page while\nthe destination sg still spans the combined skb-\u0026gt;data_len.\n\nRestore this combined-length page gate for both IPv4 and IPv6.(CVE-2026-63912)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6: vti: Use ip6_tnl.net in vti6_changelink().\n\nip netns add ns1\nip netns add ns2\nip -n ns1 link add vti6_test type vti6 remote ::1 local ::2 key 7\nip -n ns1 link set vti6_test netns ns2\nip -n ns2 link set vti6_test type vti6 remote ::3 local ::4 key 9\nip netns del ns2\nip netns del ns1\n[  132.495484] ------------[ cut here ]------------\n[  132.497609] kernel BUG at net/core/dev.c:12376!\n\nCommit 61220ab34948 (\u0026quot;vti6: Enable namespace changing\u0026quot;) dropped\nNETIF_F_NETNS_LOCAL from vti6 devices. A vti6 tunnel can then\nmove through IFLA_NET_NS_FD. After the move dev_net(dev) points\nat the new netns while t-\u0026gt;net stays at the creation netns.\n\nvti6_changelink() and vti6_update() still use dev_net(dev) and\ndev_net(t-\u0026gt;dev). They unlink from one per netns hash and relink\ninto another. The creation netns is left with a stale entry.\ncleanup_net() of that netns later walks freed memory.\n\nReachable from an unprivileged user namespace (unshare --user\n--map-root-user --net). Cross tenant scope on container hosts.(CVE-2026-63917)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: input: hold netns during deferred transport reinjection\n\nTransport-mode reinjection stores a struct net pointer in skb-\u0026gt;cb and\nuses it later from xfrm_trans_reinject(). That pointer must stay valid\nuntil the deferred callback runs.\n\nTake a netns reference when queueing deferred reinjection work and drop\nit after the callback completes. Use maybe_get_net() so the queueing\npath does not revive a namespace that is already being torn down.\n\nThis keeps the existing workqueue design and fixes the netns lifetime\nhandling in one place for all users of xfrm_trans_queue_net().(CVE-2026-63919)\n\nIn the Linux kernel, ip6_datagram_recv_specific_ctl() builds IPV6_{HOPOPTS,DSTOPTS,RTHDR} cmsgs (and their IPV6_2292* legacy counterparts) by trusting the on-wire hdrlen byte (ptr[1]) when computing the put_cmsg() length. The length was validated only at parse time (ipv6_parse_hopopts(), etc.). An nftables payload-write expression can rewrite hdrlen after parsing and before the skb reaches recvmsg; the write itself is in-bounds but put_cmsg() then reads up to ((hdrlen+1) \u0026amp;lt;\u0026amp;lt; 3) = 2040 bytes from an 8-byte header. nftables is reachable from an unprivileged user namespace, so this is an unprivileged slab-out-of-bounds read.(CVE-2026-63920)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().\n\nAfter patch 1/2 in this series, vti6_update() unlinks and relinks\nthe tunnel through t-\u0026gt;net. vti6_siocdevprivate() still uses\ndev_net(dev) for the collision lookup. For a tunnel moved through\nIFLA_NET_NS_FD, dev_net(dev) is the new netns, not t-\u0026gt;net.\n\nSIOCCHGTUNNEL on a migrated tunnel then runs:\n\n  net = dev_net(dev)                    /* migrated netns */\n  t   = vti6_locate(net, \u0026amp;p1, false)    /* misses target in t-\u0026gt;net */\n  ...\n  t   = netdev_priv(dev)\n  vti6_update(t, \u0026amp;p1, false)            /* mutates t-\u0026gt;net\u0026apos;s hash */\n\nA caller in the migrated netns picks params that match a tunnel\nin the creation netns. The lookup in dev_net(dev) finds nothing.\nvti6_update() prepends the migrated tunnel at the head of the\ncreation netns hash bucket for those params. Later lookups in\nthe creation netns resolve to the migrated device. xfrm receive\ndelivers the matched packets through a device the caller controls.\n\nReachable from an unprivileged user namespace (unshare --user\n--map-root-user --net). Cross tenant scope on container hosts.\n\nSwitch the SIOCCHGTUNNEL path on a non fallback device to use\nt-\u0026gt;net for the lookup. The lookup now matches the netns\nvti6_update() operates on.\n\nAlso add ns_capable(self-\u0026gt;net-\u0026gt;user_ns, CAP_NET_ADMIN) before\nthe lookup. The check at the top of the case is against\ndev_net(dev)-\u0026gt;user_ns, which after migration is the attacker\u0026apos;s\nnetns. A caller there can pick params absent from self-\u0026gt;net,\nthe lookup returns NULL, t becomes self, and vti6_update()\ninserts the device into the creation netns hash. The new check\nrequires CAP_NET_ADMIN in the creation netns user_ns too.\n\nSIOCADDTUNNEL and SIOCCHGTUNNEL on the fallback device keep\ndev_net(dev), which equals init_net there.(CVE-2026-63921)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo()\n\nipv6_hop_jumbo() calls pskb_trim_rcsum(), which can change skb pointers.\nLet\u0026apos;s recompute nh pointer to make sure any change won\u0026apos;t mess things up.(CVE-2026-63924)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: sockmap: fix tail fragment offset in bpf_msg_push_data\n\nWhen bpf_msg_push_data() inserts data in the middle of a scatterlist\nentry, it splits the original entry into a left fragment and a right\nfragment.\n\nThe right fragment offset is page-local, but the code advances it with\n`start`, which is the message-global insertion point. For inserts into a\nnon-first SG entry, this over-advances the offset and leaves the split\nlayout inconsistent.\n\nAdvance the right fragment offset by the fragment-local delta,\n`start - offset`, which matches the length removed from the front of the\noriginal entry.(CVE-2026-63926)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: omninet: fix memory corruption with small endpoint\n\nMake sure that the bulk-out buffers are at least as large as the\nhardcoded transfer size to avoid user-controlled slab corruption should\na malicious device report a smaller endpoint max packet size than\nexpected.(CVE-2026-63928)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix UAF in hci_le_create_cis_sync\n\nhci_le_create_cis_sync() dereferences conn-\u0026gt;conn_timeout after releasing\nboth rcu_read_lock() and hci_dev_lock(hdev).  The conn pointer was\nobtained from an RCU-protected iteration over hdev-\u0026gt;conn_hash.list and\nis not valid once these locks are dropped.  A concurrent disconnect can\nfree the hci_conn between the unlock and the dereference, causing a\nuse-after-free read.\n\nThe cancellation mechanism in hci_conn_del() cannot prevent this because\nhci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL:\n\n    hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL);\n\nWhile hci_conn_del() dequeues with data=conn:\n\n    hci_cmd_sync_dequeue(hdev, NULL, conn, NULL);\n\nSince NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never\nmatches, and the pending work item is not cancelled.\n\nFix this by saving conn-\u0026gt;conn_timeout into a local variable while the\nlocks are still held, so the stale conn pointer is never dereferenced\nafter unlock.\n\nThis is the same class of bug as the one fixed by commit 035c25007c9e\n(\u0026quot;Bluetooth: hci_sync: Fix UAF on le_read_features_complete\u0026quot;) which\naddressed the identical pattern in a different function.\n\nThis vulnerability was identified using 0sec.ai, an open-source\nautomated security auditing platform (https://github.com/0sec-labs).(CVE-2026-63944)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: serialize iso_sock_clear_timer with socket lock\n\niso_sock_close() calls iso_sock_clear_timer() before acquiring\nlock_sock(sk).\n\niso_sock_clear_timer() reads iso_pi(sk)-\u0026gt;conn twice without the\nsocket lock held:\n\n    if (!iso_pi(sk)-\u0026gt;conn)\n        return;\n    cancel_delayed_work(\u0026amp;iso_pi(sk)-\u0026gt;conn-\u0026gt;timeout_work);\n\nConcurrently, iso_conn_del() executes under lock_sock(sk) and calls\niso_chan_del(), which sets iso_pi(sk)-\u0026gt;conn to NULL and may result in\nthe final reference to the connection being dropped:\n\n    CPU0                         CPU1\n    ----                         ----\n    iso_sock_clear_timer()\n      if (conn != NULL) ...      lock_sock(sk)\n                                   iso_chan_del()\n                                   iso_pi(sk)-\u0026gt;conn = NULL\n      cancel_delayed_work(conn)  /* NULL deref or UAF */\n\niso_pi(sk)-\u0026gt;conn is not stable across the unlock window, causing a\nNULL pointer dereference or use-after-free.\n\nSerialize iso_sock_clear_timer() with the socket lock by moving it\ninside lock_sock()/release_sock(), matching the pattern used in\niso_conn_del() and all other call sites.(CVE-2026-63945)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: fix UAF in iso_recv_frame\n\niso_recv_frame reads conn-\u0026gt;sk under iso_conn_lock but releases the lock\nbefore using sk, with no reference held. A concurrent iso_sock_kill()\ncan free sk in that window, causing use-after-free on sk-\u0026gt;sk_state and\nsock_queue_rcv_skb().\n\nFix by replacing the bare pointer read with iso_sock_hold(conn), which\ncalls sock_hold() while the spinlock is held, atomically elevating the\nrefcount before the lock drops. Add a drop_put label so sock_put() is\ncalled on all exit paths where the hold succeeded.(CVE-2026-63946)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmemfd: deny writeable mappings when implying SEAL_WRITE\n\nWhen SEAL_EXEC is added, SEAL_WRITE is implied to make W^X.  But the\nimplied seal is set after the check that makes sure the memfd can not have\nany writable mappings.  This means one can use SEAL_EXEC to apply\nSEAL_WRITE while having writeable mappings.\n\nThis breaks the contract that SEAL_WRITE provides and can be used by an\nattacker to pass a memfd that appears to be write sealed but can still be\nmodified arbitrarily.\n\nFix this by adding the implied seals before the call for\nmapping_deny_writable() is done.(CVE-2026-63952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: serial: cypress_m8: fix memory corruption with small endpoint\n\nMake sure that the interrupt-out endpoint max packet size is at least\neight bytes to avoid user-controlled slab corruption or NULL-pointer\ndereference should a malicious device report a smaller size.(CVE-2026-63956)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix possible infinite loop in fib6_select_path()\n\nFound while auditing the same pattern Sashiko reported in\nrt6_fill_node() [1]. Apply the same fix as\ncommit f8d8ce1b515a (\u0026quot;ipv6: fix possible infinite loop in fib6_info_uses_dev()\u0026quot;).\n\nWriters holding tb6_lock can list_del_rcu(\u0026amp;first-\u0026gt;fib6_siblings)\nwithout waiting for RCU readers; first-\u0026gt;fib6_siblings.next then\nstill points into the old ring and this softirq-side walker never\nreaches \u0026amp;first-\u0026gt;fib6_siblings as its terminator. fib6_purge_rt()\nalways WRITE_ONCE()s first-\u0026gt;fib6_nsiblings to 0 before\nlist_del_rcu(), so an inside-loop check is a reliable detach signal.\n\n[1] https://sashiko.dev/#/patchset/20260526020227.4857-1-jiayuan.chen%40linux.dev(CVE-2026-63968)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix race between sctp_wait_for_connect and peeloff\n\nsctp_wait_for_connect() drops and re-acquires the socket lock while\nwaiting for the association to reach ESTABLISHED state. During this\nwindow, another thread can peeloff the association to a new socket via\ngetsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc-\u0026gt;base.sk. After\nre-acquiring the old socket lock, sctp_wait_for_connect() returns\nsuccess without noticing the migration — the caller then accesses\nthe association under the wrong lock in sctp_datamsg_from_user().\n\nAdd the same sk != asoc-\u0026gt;base.sk check that sctp_wait_for_sndbuf()\nalready has, returning an error if the association was migrated while\nwe slept.(CVE-2026-63971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close\n\nSince hci_dev_close_sync() can now be called during the reset path, we\nshould also set HCI_CMD_DRAIN_WORKQUEUE. This avoids queuing timeouts\nwhile the hdev workqueue is being drained.(CVE-2026-63974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix possible crash on l2cap_ecred_conn_rsp\n\nIf dcid is received for an already-assigned destination CID the spec\nrequires that both channels to be discarded, but calling l2cap_chan_del\nmay invalidate the tmp cursor created by list_for_each_entry_safe and\nin fact it is the wrong procedure as the chan-\u0026gt;dcid may be assigned\npreviously it really needs to be disconnected.\n\nCalling l2cap_chan_clone directly may still lead to l2cap_chan_del so\ninstead schedule l2cap_chan_timeout with delay 0 to close the channel\nasynchronously.(CVE-2026-63975)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: l2cap: clear chan-\u0026gt;ident on ECRED reconfiguration success\n\nl2cap_ecred_reconf_rsp() returns early on success without clearing\nchan-\u0026gt;ident. Every other L2CAP response handler (l2cap_ecred_conn_rsp,\nl2cap_le_connect_rsp, l2cap_config_rsp) clears chan-\u0026gt;ident after a\nsuccessful transaction to prevent the channel from matching subsequent\nresponses with the recycled ident value.\n\nA remote attacker that completed a reconfiguration as the peer can\nreplay a failure response with the stale ident, causing the kernel to\nmatch and destroy the already-established channel via\nl2cap_chan_del(chan, ECONNRESET).\n\nClear chan-\u0026gt;ident for all matching channels on success, and harden the\nfailure path by using l2cap_chan_hold_unless_zero() consistent with\nother L2CAP handlers (l2cap_le_command_rej, __l2cap_get_chan_by_ident).(CVE-2026-63976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress()\n\nipv6_rpl_srh_decompress() computes:\n\n    outhdr-\u0026gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) \u0026gt;\u0026gt; 3);\n\nhdrlen is __u8. For n \u0026gt;= 127 the result exceeds 255 and silently\ntruncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):\n\n    (128 * 16) \u0026gt;\u0026gt; 3 = 256, truncated to 0 as __u8\n\nThe caller in ipv6_rpl_srh_rcv() then places the compressed header\nat buf + ((ohdr-\u0026gt;hdrlen + 1) \u0026lt;\u0026lt; 3). With hdrlen=0 this is buf + 8,\nbut the decompressed region occupies buf[0..2055] (8-byte header\nplus 128 full addresses). The compressed header overlaps the\ndecompressed data, and ipv6_rpl_srh_compress() writes into this\noverlap, corrupting the routing header of the forwarded packet.\n\nThe existing guard at exthdrs.c:546 checks (n + 1) \u0026gt; 255, which\nprevents n+1 from overflowing unsigned char (the segments_left\nfield), but does not prevent the computed hdrlen from overflowing\n__u8. n=127 passes because 128 \u0026lt;= 255, yet hdrlen=256 does not\nfit.\n\nTighten the bound to (n + 1) \u0026gt; 127. This caps n at 126, giving\nhdrlen = (127 * 16) \u0026gt;\u0026gt; 3 = 254, which fits in __u8. The compressed\nheader then lands at buf + ((254 + 1) \u0026lt;\u0026lt; 3) = buf + 2040, exactly\npast the decompressed region (buf[0..2039]). No overlap. 127\nsegments is well beyond any realistic RPL deployment.(CVE-2026-63984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: eeprom: add more safeties to EEPROM Netlink fallback\n\nThe Netlink fallback path for reading module EEPROM\n(fallback_set_params()) validates that offset \u0026lt; eeprom_len,\nbut does not check that offset + length stays within eeprom_len.\nThe ioctl equivalent (ethtool_get_any_eeprom() in ioctl.c) has\nalways enforced both bounds:\n\n  if (eeprom.offset + eeprom.len \u0026gt; total_len)\n      return -EINVAL;\n\nThis could lead to surprises in both drivers and device FW.\nAdd the missing offset + length validation to fallback_set_params(),\nmirroring the ioctl.\n\nSimilarly - ethtool core in general, and ethtool_get_any_eeprom()\nin particular tries to zero-init all buffers passed to the drivers\nto avoid any extra work of zeroing things out. eeprom_fallback()\nuses a plain kmalloc(), change it to zalloc.(CVE-2026-63985)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntunnels: do not assume transport header in iptunnel_pmtud_check_icmp()\n\nIn some cases, iptunnel_pmtud_check_icmp() can be called while\nskb transport header is not set.\n\nThis triggers an out-of-bound access, because\n(typeof(skb-\u0026gt;transport_header))~0U is 65535.\n\nAccess the icmp header based on IPv4 network header,\nafter making sure icmp-\u0026gt;type is present in skb linear part.\n\nNote that iptunnel_pmtud_check_icmpv6()) is fine.(CVE-2026-63992)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu()\n\nskb_tunnel_check_pmtu() can change skb-\u0026gt;head.\n\nReusing old_iph afer skb_tunnel_check_pmtu() can cause an UAF.\n\nUse instead ip_hdr(skb) as done in drivers/net/bareudp.c\nand drivers/net/geneve.c.\n\nFound by Sashiko.(CVE-2026-63993)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntunnels: load network headers after skb_cow() in iptunnel_pmtud_build_icmp[v6]()\n\nSashiko found that iptunnel_pmtud_build_icmp() and\niptunnel_pmtud_build_icmpv6() were caching ip_hdr() and ipv6_hdr()\nbefore an skb_cow() call which can reallocate skb-\u0026gt;head.\n\nFix this possible UAF by initializing the local variables\nafter the skb_cow() call.\n\nRemove skb_reset_network_header() calls which were not needed.(CVE-2026-63994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: free net-\u0026gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table()\n\nipv4_sysctl_exit_net() is currently freeing net-\u0026gt;ipv4.sysctl_local_reserved_ports\ntoo soon.\n\nOnly after unregister_net_sysctl_table() we can be sure no threads can possibly\nuse the sysctls, including /proc/sys/net/ipv4/ip_local_reserved_ports.(CVE-2026-64002)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues\n\nWhile a SCSI host is in a recovery state, scsi_mq_requeue_cmd() will not\nset the requeue list for a requeued command to be kicked in the future.\nThe expectation is a call to scsi_run_host_queues() will kick all SCSI\ndevices once the recovery state is cleared.\n\nHowever, scsi_run_host_queues() uses shost_for_each_device() which uses\nscsi_device_get() and so will ignore devices in a partially removed\nstate like SDEV_CANCEL. But these devices may also have requeued\nrequests, leaving their requests stuck from not being kicked and causing\nthe removal process of the device to hang.\n\nscsi_run_host_queues() needs to run against more devices than the macro\nshost_for_each_device() allows. Instead of using the too limiting\nscsi_device_get() state checks, only ignore devices in SDEV_DEL state or\nwhen unable to acquire a reference. Attempt to run the queues for all\nother devices when scsi_run_host_queues() is called.(CVE-2026-64003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsecurity/keys: fix missed RCU read section on lookup\n\nNicholas Carlini reports that the keyring code calls assoc_array_find()\nin find_key_to_update() without holding the RCU read lock, while the\nassoc_array_gc() code really is designed around removing the node from\nthe tree and then freeing it after an RCU grace-period.\n\nThe regular key handling doesn\u0026apos;t see this because holding the keyring\nsemaphore hides any lifetime issues, but the persistent key handling\nuses a different model.\n\nInstead of extending the keyring locking, just do the simple RCU locking\nthat the assoc_array was designed for.(CVE-2026-64015)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, skmsg: fix verdict sk_data_ready racing with ktls rx\n\nsk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() and\ndefers to psock-\u0026gt;saved_data_ready when a TLS RX context is present,\navoiding a conflict with the TLS strparser\u0026apos;s ownership of the receive\nqueue (commit e91de6afa81c, \u0026quot;bpf: Fix running sk_skb program types\nwith ktls\u0026quot;).\n\nsk_psock_verdict_data_ready() has no equivalent guard.  When a socket\nis inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX is\nconfigured, tls_sw_strparser_arm() saves sk_psock_verdict_data_ready\nas rx_ctx-\u0026gt;saved_data_ready.  On data arrival:\n\n  tls_data_ready -\u0026gt; tls_strp_data_ready -\u0026gt; tls_rx_msg_ready\n    -\u0026gt; saved_data_ready() = sk_psock_verdict_data_ready()\n      -\u0026gt; tcp_read_skb() drains sk_receive_queue via __skb_unlink()\n         without calling tcp_eat_skb(), so copied_seq is not advanced.\n\ntls_strp_msg_load() then finds tcp_inq() \u0026gt;= full_len (stale), calls\ntcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), and\nreturns with rx_ctx-\u0026gt;strp.anchor.frag_list pointing at a psock-owned\n(potentially freed) skb.  tls_decrypt_sg() subsequently walks that\nfrag_list: use-after-free.\n\nApply the same fix as sk_psock_strp_data_ready(): if a TLS RX context\nis present, call psock-\u0026gt;saved_data_ready (sock_def_readable) to wake\nrecv() waiters and return immediately, leaving the receive queue\nuntouched.  TLS retains sole ownership of the queue and decrypts the\nrecord normally through tls_sw_recvmsg().(CVE-2026-64025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: mcast: Fix a possible use-after-free when removing a bridge port\n\nWhen per-VLAN multicast snooping is enabled, the bridge iterates over\nall the bridge ports, disables the per-port multicast context on each\nport and enables the per-{port, VLAN} multicast contexts instead. The\nreverse happens when per-VLAN multicast snooping is disabled.\n\nWhen global multicast snooping is enabled, the bridge iterates over all\nthe bridge ports and enables the per-port multicast context on each\nport. The reverse happens when multicast snooping is disabled.\n\nThe above scheme can result in a situation where both types of contexts\n(per-port and per-{port, VLAN}) are enabled on a single bridge port:\n\n # ip link add name br1 up type bridge mcast_snooping 1 mcast_querier 1 vlan_filtering 1\n # ip link add name dummy1 up master br1 type dummy\n # ip link set dev br1 type bridge mcast_vlan_snooping 1\n # ip link set dev br1 type bridge mcast_snooping 0\n # ip link set dev br1 type bridge mcast_snooping 1\n\nThis is not intended and it is a problem since the commit cited below.\nPrior to this commit, when removing a bridge port,\nbr_multicast_disable_port() would disable the per-port multicast context\nand the per-{port, VLAN} multicast contexts would get disabled when\nflushing VLANs.\n\nAfter this commit, br_multicast_disable_port() only disables the\nper-port multicast context if per-VLAN multicast snooping is disabled.\nIf both types of contexts were enabled on the port when it was removed,\nthe per-port multicast context would remain enabled when freeing the\nbridge port, leading to a use-after-free [1].\n\nFix by preventing the bridge from enabling / disabling the per-port\nmulticast contexts when toggling global multicast snooping if per-VLAN\nmulticast snooping is enabled.\n\n[1]\nODEBUG: free active (active state 0) object: ffff88810f8bda78 object type: timer_list hint: br_ip6_multicast_port_query_expired (net/bridge/br_multicast.c:1927)\nWARNING: lib/debugobjects.c:629 at debug_print_object+0x1b1/0x3e0, CPU#5: swapper/5/0\n[...]\nCall Trace:\n\u0026lt;IRQ\u0026gt;\n__debug_check_no_obj_freed (lib/debugobjects.c:1116)\nkfree (mm/slub.c:2620 mm/slub.c:6250 mm/slub.c:6565)\nkobject_cleanup (lib/kobject.c:689)\nrcu_do_batch (kernel/rcu/tree.c:2617)\nrcu_core (kernel/rcu/tree.c:2869)\nhandle_softirqs (kernel/softirq.c:622)\n__irq_exit_rcu (kernel/softirq.c:656 kernel/softirq.c:496 kernel/softirq.c:735)\nirq_exit_rcu (kernel/softirq.c:752)\nsysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1061 (discriminator 47) arch/x86/kernel/apic/apic.c:1061 (discriminator 47))\n\u0026lt;/IRQ\u0026gt;(CVE-2026-64032)\n\nIn the Linux kernel, the following vulnerability has been resolved: net: tls: prevent chain-after-chain in plain text SG. Sashiko points out that if end = 0 (start != 0) the current code will create a chain link to content type right after the wrap link. This would create a chain where the wrap link points directly to another chain link. The scatterlist API sg_next iterator does not recursively resolve consecutive chain links, meaning this is illegal input to crypto. The wrapping link is unnecessary if end = 0. TLS 1.3 can use the \u0026quot;wrapping slot\u0026quot; for its chaining if end = 0, which avoids the chain-after-chain.(CVE-2026-64046)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring\n\nWhen an sk_msg scatterlist ring wraps (sg.end \u0026lt; sg.start),\ntls_push_record() chains the tail portion of the ring to the head\nusing sg_chain(). An extra entry in the sg array is reserved for\nthis:\n\n  struct sk_msg_sg {\n        [...]\n        /* The extra two elements:\n         * 1) used for chaining the front and sections when the list becomes\n         *    partitioned (e.g. end \u0026lt; start). The crypto APIs require the\n         *    chaining;\n         * 2) to chain tailer SG entries after the message.\n         */\n        struct scatterlist              data[MAX_MSG_FRAGS + 2];\n\nThe current code uses MAX_SKB_FRAGS + 1 as the ring size:\n\n    sg_chain(\u0026amp;msg_pl-\u0026gt;sg.data[msg_pl-\u0026gt;sg.start],\n             MAX_SKB_FRAGS - msg_pl-\u0026gt;sg.start + 1,\n             msg_pl-\u0026gt;sg.data);\n\nThis places the chain pointer at\n\n  sg_chain(data[start], (MAX_SKB_FRAGS - msg_start + 1) .. =\n  \u0026amp;data[start] + (MAX_SKB_FRAGS - msg_start + 1) - 1 =\n  data[start + (MAX_SKB_FRAGS - start + 1) - 1] =\n  data[MAX_SKB_FRAGS]\n\ninstead of the true last entry. This is likely due to a \u0026quot;race\u0026quot; of\nthe commit under Fixes landing close to\ncommit 031097d9e079 (\u0026quot;bpf: sk_msg, zap ingress queue on psock down\u0026quot;)\n\nConvert to ARRAY_SIZE and drop the data[start] / - start (as suggested\nby Sabrina).(CVE-2026-64047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nirq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT\n\nOn PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via\nrun_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0.\n\nAfter irq_work_single() clears BUSY via atomic_cmpxchg(), it still\ndereferences @work for irq_work_is_hard() and rcuwait_wake_up().\n\nAn irq_work_sync() caller on another CPU that enters after BUSY is cleared\ncan observe BUSY==0 immediately, return, and free the work before those\naccesses complete — causing a use-after-free.\n\nFix this by wrapping run_irq_workd() in guard(rcu)() so that the entire\nirq_work_single() execution is within an RCU read-side critical\nsection. Then add synchronize_rcu() in irq_work_sync() after\nrcuwait_wait_event() to ensure the caller waits for the RCU grace period\nbefore returning, preventing premature frees.(CVE-2026-64073)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: bridge: eb_tables: close module init race\n\nsashiko reports for unrelated patch:\n Does the core ebtables initialization in ebtables.c suffer from a similar race?\n Once nf_register_sockopt() completes, the sockopts are exposed globally.\n\nsockopt has to be registered last, just like in ip/ip6/arptables.(CVE-2026-64076)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ebtables: move to two-stage removal scheme\n\nLike previous patches for x_tables, follow same pattern in ebtables.\nWe can\u0026apos;t reuse xt helpers: ebt_table struct layout is incompatible.\n\ntable-\u0026gt;ops assignment is now done while still holding the ebt mutex\nto make sure we never expose partially-filled table struct.(CVE-2026-64077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: tt: fix negative tt_buff_len\n\nbatadv_orig_node::tt_buff_len was declared as s16, but the field is never\nintended to hold a negative value. When a value greater than 32767 is\nassigned, it wraps to a negative signed integer.\n\nIn batadv_send_other_tt_response(), tt_buff_len is temporarily widened to\ns32. The incorrectly negative s16 value propagates into the s32, causing\nbatadv_tt_prepare_tvlv_global_data() to allocate a full sized buffer but\npopulates only a small portion of it with the collected changeset. All\nremaining bits are kept uninitialized.\n\nUsing an u16 avoids this type confusion and ensures that no (negative) sign\nextension is performed in batadv_send_other_tt_response().(CVE-2026-64088)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: tt: fix negative last_changeset_len\n\nbatadv_piv_tt::last_changeset_len len was declared as s16, but the field is\nnever intended to hold a negative value. When a value greater than 32767 is\nassigned, it wraps to a negative signed integer.\n\nIn batadv_send_my_tt_response(), last_changeset_len is temporarily widened\nto s32. The incorrectly negative s16 value propagates into the s32, causing\nbatadv_tt_prepare_tvlv_local_data() to allocate a full sized buffer but\npopulates only a small portion of it with the collected changeset. All\nremaining bits are kept uninitialized.\n\nUsing an u16 avoids this type confusion and ensures that no (negative) sign\nextension is performed in batadv_send_my_tt_response().(CVE-2026-64089)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: bla: avoid double decrement of bla.num_requests\n\nThe bla.num_requests is increased when no request_sent was in progress. And\nit is decremented in various places (announcement was received, backbone is\npurged, periodic work). But the check if the request_sent is actually set\nto a specific state and the atomic_dec/_inc are not safe because they are\nnot atomic (TOCTOU) and multiple such code portions can run concurrently.\n\nAt the same time, it is necessary to modify request_sent (state) and\nbla.num_requests atomically. Otherwise batadv_bla_send_request() might set\nrequest_sent to 1 and is interrupted.  batadv_handle_announce() can then\nset request_sent back to 0 and decrement num_requests before\nbatadv_bla_send_request() incremented it.\n\nThe two operations must therefore be locked. And since state (request_sent)\nand wait_periods are only accessed inside this lock, they can be converted\nto simpler datatypes. And to avoid that the bla.num_requests is touched by\na parallel running context with a valid backbone_gw reference after\nbatadv_bla_purge_backbone_gw() ran, a third state \u0026quot;stopped\u0026quot; is required to\ncorrectly signal that a backbone_gw is in the state of being cleaned up.(CVE-2026-64095)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Validate GPIO pin LUT table size before iterating\n\n[Why\u0026amp;How]\nThe GPIO pin table parsers in get_gpio_i2c_info() and\nbios_parser_get_gpio_pin_info() derive an element count from the VBIOS\ntable_header.structuresize field, then iterate over gpio_pin[] entries.\nHowever, GET_IMAGE() only validates that the table header itself fits\nwithin the BIOS image. If the VBIOS reports a structuresize larger than\nthe actual mapped data, the loop reads past the end of the BIOS image,\ncausing an out-of-bounds read.\n\nFix this by calling bios_get_image() to validate that the full claimed\nstructuresize is accessible within the BIOS image before entering the\nloop in both functions.\n\n(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/virtio: use uninterruptible resv lock for plane updates\n\nvirtio_gpu_cursor_plane_update() and virtio_gpu_resource_flush() lock\nthe framebuffer BO\u0026apos;s dma_resv via virtio_gpu_array_lock_resv() and\nignore its return value. The function can fail with -EINTR from\ndma_resv_lock_interruptible() (signal during lock wait) or with\n-ENOMEM from dma_resv_reserve_fences() (fence slot allocation),\nleaving the resv lock not held. The queue path then walks the object\narray and calls dma_resv_add_fence(), which requires the lock held;\nwith lockdep enabled this trips dma_resv_assert_held():\n\n  WARNING: drivers/dma-buf/dma-resv.c:296 at dma_resv_add_fence+0x71e/0x840\n  Call Trace:\n   virtio_gpu_array_add_fence\n   virtio_gpu_queue_ctrl_sgs\n   virtio_gpu_queue_fenced_ctrl_buffer\n   virtio_gpu_cursor_plane_update\n   drm_atomic_helper_commit_planes\n   drm_atomic_helper_commit_tail\n   commit_tail\n   drm_atomic_helper_commit\n   drm_atomic_commit\n   drm_atomic_helper_update_plane\n   __setplane_atomic\n   drm_mode_cursor_universal\n   drm_mode_cursor_common\n   drm_mode_cursor_ioctl\n   drm_ioctl\n   __x64_sys_ioctl\n\nBeyond the WARN, mutating the dma_resv fence list without the lock\nraces with concurrent readers/writers and can corrupt the list.\n\nBoth call sites run inside the .atomic_update plane callback, which\nDRM atomic helpers do not allow to fail (by the time it runs, the\ncommit has been signed off to userspace and there is no clean\nrollback path). Moving the lock acquisition to .prepare_fb was\nrejected because the broader lock scope deadlocks against other BO\nlocking paths in the same atomic commit.\n\nIntroduce virtio_gpu_lock_one_resv_uninterruptible() that uses\ndma_resv_lock() instead of dma_resv_lock_interruptible(). This\neliminates the -EINTR failure mode -- the realistic syzbot trigger\n-- without extending the lock hold across the commit. The helper\nlocks a single BO and rejects nents \u0026gt; 1 with -EINVAL; both fix\nsites lock exactly one BO.\n\nUse it from virtio_gpu_cursor_plane_update() and\nvirtio_gpu_resource_flush(); check the return value to handle the\nremaining -ENOMEM case from dma_resv_reserve_fences() by freeing\nthe objs and skipping the plane update for that frame. The\nframebuffer BOs touched here are not shared with other contexts\nand lock contention is expected to be brief, so the loss of\nsignal-interruptibility is acceptable.\n\nOther callers of virtio_gpu_array_lock_resv() (the ioctl paths)\ncontinue to use the interruptible variant.\n\nThe bug was reported by syzbot, triggered via fault injection\n(fail_nth) on the DRM_IOCTL_MODE_CURSOR path, which forces the\n-ENOMEM branch in dma_resv_reserve_fences().(CVE-2026-64098)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits\n\nUserspace can restore an ITS Device Table Entry whose Size field encodes\nmore EventID bits than the virtual ITS supports.  The live MAPD path\nrejects that state, but vgic_its_restore_dte() accepts it and stores the\nout-of-range value in dev-\u0026gt;num_eventid_bits.\n\nReject restored DTEs with num_eventid_bits \u0026gt; VITS_TYPER_IDBITS before\nallocating the device.  This mirrors the MAPD check and prevents the\nrestored state from reaching vgic_its_restore_itt(), where the unchecked\nvalue can be converted into an oversized scan_its_table() range.(CVE-2026-64106)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Fix UAF read of tail-\u0026gt;len in unix_stream_data_wait()\n\nunix_stream_data_wait() does skb_peek_tail(\u0026amp;sk-\u0026gt;sk_receive_queue) without\nholding any lock that prevents SKBs on that queue from being dequeued and\nfreed.\nThis has been the case since commit 79f632c71bea (\u0026quot;unix/stream: fix\npeeking with an offset larger than data in queue\u0026quot;).\nThe first consequence of this is that the pointer comparison\n`tail != last` can be false even if `last` semantically refers to an\nalready-freed SKB while `tail` is a new SKB allocated at the same address;\nwhich can cause unix_stream_data_wait() to wrongly keep blocking after new\ndata has arrived, but only in a weird scenario where a peeking recv() and\na normal recv() on the same socket are racing, which is probably not a\nreal problem.\n\nBut since commit 2b514574f7e8 (\u0026quot;net: af_unix: implement splice for stream\naf_unix sockets\u0026quot;), `tail` is actually dereferenced, which can cause UAF in\nthe following race scenario (where test_setup() runs single-threaded,\nand afterwards, test_thread1() and test_thread2() run concurrently in\ntwo threads:\n```\nstatic int socks[2];\nvoid test_setup(void) {\n  socketpair(AF_UNIX, SOCK_STREAM, 0, socks);\n  send(socks[1], \u0026quot;A\u0026quot;, 1, 0);\n  int peekoff = 1;\n  setsockopt(socks[0], SOL_SOCKET, SO_PEEK_OFF, \u0026amp;peekoff, sizeof(peekoff));\n}\nvoid test_thread1(void) {\n  char dummy;\n  recv(socks[0], \u0026amp;dummy, 1, MSG_PEEK);\n}\nvoid test_thread2(void) {\n  char dummy;\n  recv(socks[0], \u0026amp;dummy, 1, 0);\n  shutdown(socks[1], SHUT_WR);\n}\n```\n\nwhen racing like this:\n```\nthread1                       thread2\nunix_stream_read_generic\n  mutex_lock(\u0026amp;u-\u0026gt;iolock)\n  skb_peek(\u0026amp;sk-\u0026gt;sk_receive_queue)\n  skb_peek_next(skb, \u0026amp;sk-\u0026gt;sk_receive_queue)\n  mutex_unlock(\u0026amp;u-\u0026gt;iolock)\n                              unix_stream_read_generic\n                                unix_state_lock(sk)\n                                skb_peek(\u0026amp;sk-\u0026gt;sk_receive_queue)\n                                unix_state_unlock(sk)\n  unix_stream_data_wait\n    unix_state_lock(sk)\n    tail = skb_peek_tail(\u0026amp;sk-\u0026gt;sk_receive_queue)\n                                spin_lock(\u0026amp;sk-\u0026gt;sk_receive_queue.lock)\n                                __skb_unlink(skb, \u0026amp;sk-\u0026gt;sk_receive_queue)\n                                spin_unlock(\u0026amp;sk-\u0026gt;sk_receive_queue.lock)\n                                consume_skb(skb) [frees the SKB]\n    `tail != last`: false\n    `tail`: true\n    `tail-\u0026gt;len != last_len` ***UAF***\n```\n\nFix the UAF by removing the read of tail-\u0026gt;len; checking tail-\u0026gt;len would\nonly make sense if SKBs in the receive queue of a UNIX socket could grow,\nwhich can no longer happen.\n\nKuniyuki explained:\n\n\u0026gt; When commit 869e7c62486e (\u0026quot;net: af_unix: implement stream sendpage\n\u0026gt; support\u0026quot;) added sendpage() support, data could be appended to the last\n\u0026gt; skb in the receiver\u0026apos;s queue.\n\u0026gt;\n\u0026gt; That\u0026apos;s why we needed to check if the length of the last skb was changed\n\u0026gt; while waiting for new data in unix_stream_data_wait().\n\u0026gt;\n\u0026gt; However, commit a0dbf5f818f9 (\u0026quot;af_unix: Support MSG_SPLICE_PAGES\u0026quot;) and\n\u0026gt; commit 57d44a354a43 (\u0026quot;unix: Convert unix_stream_sendpage() to use\n\u0026gt; MSG_SPLICE_PAGES\u0026quot;) refactored sendmsg(), and now data is always added\n\u0026gt; to a new skb.\n\nThat means this fix is not suitable for kernels before 6.5.(CVE-2026-64109)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrbd: eliminate a race in lock_dwork draining on unmap\n\nGiven how rbd_lock_add_request() and rbd_img_exclusive_lock() are\nwritten, lock_dwork may be (re)queued more than it\u0026apos;s actually needed:\nfor example in case a new I/O request comes in while we are in the\nmiddle of rbd_acquire_lock() on behalf of another I/O request.  This is\nexpected and with rbd_release_lock() preemptively canceling lock_dwork\nis benign under normal operation.\n\nA more problematic example is maybe_kick_acquire():\n\n    if (have_requests || delayed_work_pending(\u0026amp;rbd_dev-\u0026gt;lock_dwork)) {\n            dout(\u0026quot;%s rbd_dev %p kicking lock_dwork\\n\u0026quot;, __func__, rbd_dev);\n            mod_delayed_work(rbd_dev-\u0026gt;task_wq, \u0026amp;rbd_dev-\u0026gt;lock_dwork, 0);\n    }\n\nIt\u0026apos;s not unrealistic for lock_dwork to get canceled right after\ndelayed_work_pending() returns true and for mod_delayed_work() to\nrequeue it right there anyway.  This is a classic TOCTOU race.\n\nWhen it comes to unmapping the image, there is an implicit assumption\nof no self-initiated exclusive lock activity past the point of return\nfrom rbd_dev_image_unlock() which unlocks the lock if it happens to be\nheld.  This unlock is assumed to be final and lock_dwork (as well as\nall other exclusive lock tasks, really) isn\u0026apos;t expected to get queued\nagain.  However, lock_dwork is canceled only in cancel_tasks_sync()\n(i.e. later in the unmap sequence) and on top of that the cancellation\ncan get in effect nullified by maybe_kick_acquire().  This may result\nin rbd_acquire_lock() executing after rbd_dev_device_release() and\nrbd_dev_image_release() run and free and/or reset a bunch of things.\nOne of the possible failure modes then is a violated\n\n    rbd_assert(rbd_image_format_valid(rbd_dev-\u0026gt;image_format));\n\nin rbd_dev_header_info() which is called via rbd_dev_refresh() from\nrbd_post_acquire_action().\n\nRedo exclusive lock task draining to provide saner semantics and try\nto meet the assumptions around rbd_dev_image_unlock().(CVE-2026-64112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nixgbevf: fix use-after-free in VEPA multicast source pruning\n\nixgbevf_clean_rx_irq() prunes frames whose source MAC matches the VF\u0026apos;s\nown address (VEPA multicast workaround) by freeing the skb and\ncontinuing to the next descriptor:\n\n    dev_kfree_skb_irq(skb);\n    continue;\n\nThe skb pointer is declared outside the while loop and persists across\niterations.  Because the continue skips the \u0026quot;skb = NULL\u0026quot; reset at the\nbottom of the loop, the next iteration enters the \u0026quot;else if (skb)\u0026quot; path\nand calls ixgbevf_add_rx_frag() on the freed skb, dereferencing\nskb_shinfo(skb)-\u0026gt;nr_frags - a use-after-free in NAPI softirq context.\n\nThe sibling driver iavf already handles this correctly by nulling the\npointer before continuing.  Apply the same pattern here.\n\nI do not have ixgbevf hardware; the bug was found by static analysis\n(scan_drop_continue_loops.py + semgrep drop_continue_in_loop, multi-tool\ncorroboration with the highest score in the scan).  The UAF was confirmed\nunder KASAN by loading a test module that reproduces the exact code\npattern (alloc skb, kfree_skb, then read skb_shinfo(skb)-\u0026gt;nr_frags):\n\n  BUG: KASAN: slab-use-after-free in ixgbevf_uaf_test_init+0x100/0x1000\n  Read of size 8 at addr 000000006163ae78 by task insmod/30\n  freed 208-byte region [000000006163adc0, 000000006163ae90)\n\nQEMU emulates igb (82576) but not ixgbe (82599), and the igbvf VF\ndriver does not include the VEPA source pruning path, so a full\nend-to-end reproduction with emulated hardware was not possible.(CVE-2026-64113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: raw: reject IP_HDRINCL packets with ihl \u0026lt; 5\n\nraw_send_hdrinc() validates that the caller-supplied IPv4 header\nfits within the message length:\n\n    iphlen = iph-\u0026gt;ihl * 4;\n    err = -EINVAL;\n    if (iphlen \u0026gt; length)\n        goto error_free;\n\n    if (iphlen \u0026gt;= sizeof(*iph)) {\n        /* fix up saddr, tot_len, id, csum, transport_header */\n    }\n\nIt does not, however, reject ihl \u0026lt; 5.  For such a packet the\n\u0026quot;if (iphlen \u0026gt;= sizeof(*iph))\u0026quot; branch is skipped, leaving the\ncrafted iphdr untouched, but the packet is still handed to\n__ip_local_out() and onward.  Downstream consumers that read\niph-\u0026gt;ihl assume a sane value: net/ipv4/ah4.c:ah_output() in\nparticular subtracts sizeof(struct iphdr) from top_iph-\u0026gt;ihl * 4\nand passes the (signed-int-negative, then cast to size_t)\nresult to memcpy(), producing an OOB access of length close to\nSIZE_MAX and a host kernel panic.\n\nAn IPv4 header with ihl \u0026lt; 5 is malformed by definition (RFC 791:\n\u0026quot;Internet Header Length is the length of the internet header in\n32 bit words ... Note that the minimum value for a correct header\nis 5.\u0026quot;).  The kernel should not be willing to inject such a\npacket into its own output path.\n\nReject \u0026quot;iphlen \u0026lt; sizeof(*iph)\u0026quot; alongside the existing\n\u0026quot;iphlen \u0026gt; length\u0026quot; check.  This matches the principle that locally\nconstructed packets that re-enter the IP stack must pass the same\nbasic sanity tests that a foreign packet would be subjected to.\n\nOnce this lands, the \u0026quot;if (iphlen \u0026gt;= sizeof(*iph))\u0026quot; wrapper around\nthe fixup branch becomes redundant; left in place to keep the\npatch minimal and backport-friendly.  A follow-up can unwrap it.\n\nNote that commit 86f4c90a1c5c (\u0026quot;ipv4, ipv6: ensure raw socket\nmessage is big enough to hold an IP header\u0026quot;) ensures the message\nbuffer is large enough to hold an iphdr, but does not constrain\nthe self-reported iph-\u0026gt;ihl.\n\nReachability: the malformed packet source is any caller with\nCAP_NET_RAW, including an unprivileged process in a user+net\nnamespace on a kernel with CONFIG_USER_NS=y.  The reproduced AH\ncrash also requires a matching xfrm AH policy on the outgoing\nroute; a container granted CAP_NET_ADMIN can install that state\nand policy in its netns.  Loopback bypasses xfrm_output, so the\ntrigger uses a real netdev.\n\nReproduced on UML + KASAN: kernel-mode fault at addr 0x0 with\nmemcpy_orig at the crash site.  Same shape reproduces inside a\nrootless Docker container with --cap-add NET_ADMIN on a stock\ndistro kernel.(CVE-2026-64114)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nqed: fix double free in qed_cxt_tables_alloc()\n\nIf one of the later PF or VF CID bitmap allocations fails,\nqed_cid_map_alloc() jumps to cid_map_fail and frees the previously\nallocated CID bitmaps before returning an error. qed_cxt_tables_alloc()\nthen calls qed_cxt_mngr_free(), which invokes qed_cid_map_free()\nagain.\n\nFix this by setting each CID bitmap pointer to NULL after bitmap_free()\nto avoid double free.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing\nv6.13-rc1. The tool is still under development and is not yet publicly\navailable. Manual inspection confirms that the bug is still\npresent in v7.1-rc3.\n\nRuntime reproduction was not attempted because exercising the failing\nallocation path requires device-specific setup.(CVE-2026-64118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: validate Add Extended Advertising Data length\n\nMGMT_OP_ADD_EXT_ADV_DATA is registered as a variable-length command,\nwith MGMT_ADD_EXT_ADV_DATA_SIZE as the fixed header size.  The handler\nthen uses cp-\u0026gt;adv_data_len and cp-\u0026gt;scan_rsp_len to validate and copy\ncp-\u0026gt;data, but it never checks that those bytes are part of the mgmt\ncommand payload.\n\nA short command can therefore make add_ext_adv_data() pass an\nout-of-bounds pointer into tlv_data_is_valid().  If the bytes beyond\nthe command buffer are addressable, they can also be copied into the\nadvertising instance as scan response data, where the caller can read\nthem back via MGMT_OP_GET_ADV_INSTANCE.  The trigger requires\nCAP_NET_ADMIN in the initial user namespace; KASAN reports an 8-byte\nslab-out-of-bounds read.\n\nReject commands whose length does not match the fixed header plus both\nadvertising data lengths before parsing cp-\u0026gt;data.(CVE-2026-64126)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()\n\nCommit 96c4af418586 (\u0026quot;cifs: Fix locking usage for tcon fields\u0026quot;)\nrefactored cifs code to change cifs_tcp_ses_lock for tc_lock around\ntc_count changes.\n\nThere was missing lock around tc_count increment inside\nsmb2_find_smb_sess_tcon_unlocked().(CVE-2026-64136)\n\nIn the Linux kernel, an out-of-bounds read vulnerability exists in the i2c-stub driver. The I2C_SMBUS_I2C_BLOCK_DATA case in stub_xfer() function (drivers/i2c/i2c-stub.c) uses data-\u0026gt;block[0] as the transfer length. The existing check only clamps it to avoid overrunning the chip-\u0026gt;words[256] register array, but does not validate it against I2C_SMBUS_BLOCK_MAX (32), which is the limit of the union i2c_smbus_data.block buffer. A local user with access to /dev/i2c-* devices can issue an I2C_SMBUS ioctl with I2C_SMBUS_I2C_BLOCK_DATA and data-\u0026gt;block[0] \u0026gt; 32, causing stub_xfer() to read or write past the end of the union i2c_smbus_data.block buffer, resulting in a stack out-of-bounds access. This vulnerability affects confidentiality, integrity, and availability.(CVE-2026-64191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async\n\n[Why\u0026amp;How]\ndc_process_dmub_aux_transfer_async() copies payload-\u0026gt;length bytes into a\n16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which\nis a no-op in release builds. If a caller ever passes length \u0026gt; 16 this\nresults in a stack buffer overflow via memcpy.\n\nAdditionally, link_index is used to dereference dc-\u0026gt;links[] without\nbounds checking against dc-\u0026gt;link_count, risking an out-of-bounds access.\n\nReplace the ASSERT with a hard runtime check that returns false when\npayload-\u0026gt;length exceeds the destination buffer size, and add a bounds\ncheck for link_index before it is used.\n\n(cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)(CVE-2026-64219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocteontx2-pf: avoid double free of pool-\u0026gt;stack on AQ init failure\n\notx2_pool_aq_init() frees pool-\u0026gt;stack when mailbox sync or retry\nallocation fails, but leaves the pointer unchanged. Later,\notx2_sq_aura_pool_init() unwinds the partial setup through\notx2_aura_pool_free(), which frees pool-\u0026gt;stack again. The CN20K-specific\ncn20k_pool_aq_init() implementation has the same bug in\nits corresponding error path.\n\nSet pool-\u0026gt;stack to NULL immediately after the local free so the shared\ncleanup path does not free the same stack again while cleaning up\npartially initialized pool state.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing\nv6.13-rc1. The tool is still under development and is not yet publicly\navailable. Manual inspection confirms that the bug is still present in\nv7.1-rc3.\n\nRuntime validation was not performed because reproducing this path\nrequires OcteonTX2/CN20K hardware.(CVE-2026-64222)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: elan_i2c - validate firmware size before use\n\nEnsure that the firmware file is large enough to contain the expected\nnumber of pages and the signature (which resides at the end of the\nfirmware blob) before accessing them to prevent potential out-of-bounds\nreads.(CVE-2026-64237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: hyper-v: Bound the bank index when querying sparse banks\n\nWhen checking if a VP ID is included in a sparse bank set, explicitly check\nthat the ID can actually be contained in a sparse bank (the TLFS allows for\na maximum of 64 banks of 64 vCPUs each).  When handling a paravirtual TLB\nflush for L2, the VP ID is copied verbatim from the enlightened VMCS,\nwithout any bounds check, i.e. isn\u0026apos;t guaranteed to be under the limit of\n4096.\n\nFailure to check the bounds of the VP ID leads to an out-of-bounds read\nwhen testing the sparse bank, and super strictly speaking could lead to KVM\nperforming an unnecessary TLB flush for an L2 vCPU.\n\n  ==================================================================\n  BUG: KASAN: use-after-free in hv_is_vp_in_sparse_set+0x85/0x100 [kvm]\n  Read of size 8 at addr ffff88811ba5f598 by task hyperv_evmcs/2802\n\n  CPU: 12 UID: 1000 PID: 2802 Comm: hyperv_evmcs Not tainted 7.1.0-rc2 #7 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x51/0x60\n   print_report+0xcb/0x5d0\n   kasan_report+0xb4/0xe0\n   kasan_check_range+0x35/0x1b0\n   hv_is_vp_in_sparse_set+0x85/0x100 [kvm]\n   kvm_hv_flush_tlb+0xe9e/0x16c0 [kvm]\n   kvm_hv_hypercall+0xe6b/0x1e60 [kvm]\n   vmx_handle_exit+0x485/0x1b60 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0x22e3/0x5070 [kvm]\n   kvm_vcpu_ioctl+0x5d0/0x10c0 [kvm]\n   __x64_sys_ioctl+0x129/0x1a0\n   do_syscall_64+0xb9/0xcf0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f0e62d1a9bf\n   \u0026lt;/TASK\u0026gt;\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffffffffffffffff pfn:0x11ba5f\n  flags: 0x4000000000000000(zone=1)\n  raw: 4000000000000000 0000000000000000 00000000ffffffff 0000000000000000\n  raw: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff88811ba5f480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n   ffff88811ba5f500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n  \u0026gt;ffff88811ba5f580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n                              ^\n   ffff88811ba5f600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n   ffff88811ba5f680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n  ==================================================================\n  Disabling lock debugging due to kernel taint\n\nOpportunistically add a compile time assertion to ensure the maximum number\nof sparse banks exactly matches the number of possible bits in the passed\nin mask.\n\n[sean: add KASAN splat, drop comment, add assert, massage changelog](CVE-2026-64247)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4: include MAY_WRITE in open permission mask for O_TRUNC\n\nPOSIX requires write permission to truncate a file, so an open() that\nspecifies O_TRUNC must be authorized for write access regardless of the\nO_ACCMODE access mode.\n\nnfs_open_permission_mask() builds the access mask passed to\nnfs_may_open(), which is the local authorization gate for OPENs the\nclient serves itself from a cached write delegation via the\ncan_open_delegated() path in nfs4_try_open_cached().  The mask is\nderived from O_ACCMODE alone, so an open(O_RDONLY | O_TRUNC) against a\nfile the caller cannot write requests only MAY_READ and passes the\nlocal check.  The OPEN is then satisfied locally and the truncation is\nissued to the server as a SETATTR(size=0) over the delegation stateid,\nwhich the server accepts under standard write-delegation semantics.\nPOSIX requires that this open fail with EACCES.\n\nInclude MAY_WRITE in the mask whenever O_TRUNC is set so the local\ncheck matches the access the server would have enforced.(CVE-2026-64298)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Prevent out-of-bounds read in glob matching\n\nString event fields are not necessarily NUL-terminated, so the filter\npredicate functions (filter_pred_string(), filter_pred_strloc() and\nfilter_pred_strrelloc()) pass the field length to the regex match\ncallbacks, and the length-aware matchers honour it.\n\nregex_match_glob() was the exception: it ignored the length and called\nglob_match(), which scans the string until it hits a NUL byte. Some\nstring fields are not NUL-terminated. One example is the dynamic char\narray of the xfs_* namespace tracepoints, which is copied without a\ntrailing NUL. For such a field, glob matching reads past the end of\nthe event field, causing a KASAN slab-out-of-bounds read in\nglob_match(), reached via regex_match_glob() and filter_match_preds()\nfrom the xfs_lookup tracepoint.\n\nAdd a length-bounded glob_match_len() and use it from regex_match_glob()\nso glob matching always stops at the field boundary. The matching loop\nis factored into a shared helper so glob_match() keeps its behaviour.(CVE-2026-64299)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - validate RSA CRT component lengths\n\nThe generic RSA key parser (rsa_helper.c) bounds each CRT component (p,\nq, dp, dq, qinv) by the modulus size n_sz, but qat_rsa_setkey_crt()\nallocates half-size DMA buffers (key_sz / 2) and right-aligns each\ncomponent with:\n\n    memcpy(dst + half_key_sz - len, src, len)\n\nWhen a CRT component is larger than half_key_sz the subtraction\nunderflows and memcpy writes past the DMA buffer, causing memory\ncorruption.\n\nAdd a len \u0026gt; half_key_sz check next to the existing !len check for each\nof the five CRT components so the driver falls back to the non-CRT path\ninstead of writing out of bounds.(CVE-2026-64304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - protect service table iterations with service_lock\n\nThe service_table list is protected by service_lock when entries are\nadded or removed (in adf_service_add() and adf_service_remove()), but\nseveral functions iterate over the list without holding this lock.\n\nA concurrent adf_service_register() or adf_service_unregister() call\ncould modify the list during traversal, leading to list corruption or\na use-after-free.\n\nFix this by holding service_lock across all list_for_each_entry()\niterations of service_table in adf_dev_init(), adf_dev_start(),\nadf_dev_stop(), adf_dev_shutdown(), adf_dev_restarting_notify(),\nadf_dev_restarted_notify(), and adf_error_notifier().\n\nThe lock ordering is safe: callers of the static helpers (adf_dev_up()\nand adf_dev_down()) acquire state_lock before service_lock, and no\nevent_hld callback or service_lock holder ever acquires state_lock in\nthe reverse order.(CVE-2026-64305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: drbg - Fix returning success on failure in CTR_DRBG\n\ndrbg_ctr_generate() sometimes returns success when it fails, leaving the\noutput buffer uninitialized.  Fix it.(CVE-2026-64306)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: pcrypt - restore callback for non-parallel fallback\n\npcrypt installs pcrypt_aead_done() on the child AEAD request before\ntrying to submit it through padata.  If padata_do_parallel() returns\n-EBUSY, pcrypt falls back to calling the child AEAD directly.\n\nThat fallback must not keep the padata completion callback.  Otherwise\nan asynchronous completion runs pcrypt_aead_done() even though the\nrequest was never enrolled in padata.\n\nRestore the original request callback and callback data before calling\nthe child AEAD directly.  This keeps the fallback path aligned with a\ndirect AEAD request while leaving the parallel path unchanged.(CVE-2026-64312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ecc - Fix carry overflow in vli multiplication\n\nThe carry flag calculation fails when r01.m_high is saturated\n(0xFFFFFFFFFFFFFFFF) and addition of lower bits overflows.\n\nThe condition (r01.m_high \u0026lt; product.m_high) doesn\u0026apos;t handle the case\nwhere r01.m_high == product.m_high and an additional carry exists\nfrom lower-bit overflow.\n\nWhen commit 3c4b23901a0c (\u0026quot;crypto: ecdh - Add ECDH software support\u0026quot;)\nintroduced crypto/ecc.c, it split the muladd() function in the\nmicro-ecc library into separate mul_64_64() and add_128_128() helpers.\nIt seems the check got lost in translation.\n\nAdd proper handling for this boundary by accounting for the carry\nfrom the lower addition.(CVE-2026-64313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisofs: bound Rock Ridge symlink components to the SL record\n\nget_symlink_chunk() and the SL handling in\nparse_rock_ridge_inode_internal() walk the variable-length components of\na Rock Ridge \u0026quot;SL\u0026quot; (symbolic link) record.  Each component is a two-byte\nheader (flags, len) followed by len bytes of text, so it occupies\nslp-\u0026gt;len + 2 bytes.  Both loops read slp-\u0026gt;len and advance to the next\ncomponent, and get_symlink_chunk() additionally does\nmemcpy(rpnt, slp-\u0026gt;text, slp-\u0026gt;len), but neither checks that the component\nlies within the SL record before dereferencing it.\n\nA crafted SL record whose component declares a len that runs past the\nrecord (rr-\u0026gt;len) therefore triggers an out-of-bounds read of up to 255\nbytes.  When the record sits at the tail of its backing buffer - for\nexample a small kmalloc()ed continuation block reached through a CE\nrecord - the read crosses the allocation; get_symlink_chunk() then\ncopies the out-of-bounds bytes into the symlink body returned to user\nspace by readlink(), disclosing adjacent kernel memory.\n\nISO 9660 images are routinely mounted from untrusted removable media -\ndesktop environments auto-mount them (e.g. via udisks2) without\nCAP_SYS_ADMIN - so the record contents are attacker-controlled.\n\nReject any component that does not fit in the remaining record bytes\nbefore using it.  In get_symlink_chunk() return NULL, like the existing\noutput-buffer (plimit) checks, so a malformed record makes readlink()\nfail with -EIO rather than silently returning a truncated target; in\nparse_rock_ridge_inode_internal() stop the inode-size walk.(CVE-2026-64317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-auth: validate reply message payload bounds against transfer length\n\nnvmet_auth_reply() accesses the variable-length rval[] array using\nattacker-controlled hl (hash length) and dhvlen (DH value length) fields\nwithout verifying they fit within the allocated buffer of tl bytes.\n\nA malicious NVMe-oF initiator can craft a DHCHAP_REPLY message with a\nsmall transfer length but large hl/dhvlen values, causing out-of-bounds\nheap reads when the target processes the DH public key (rval + 2*hl) or\nperforms the host response memcmp.\n\nWith DH authentication configured, the OOB pointer is passed directly to\nsg_init_one() and read by crypto_kpp_compute_shared_secret(), reaching\nup to 526 bytes past the buffer. This is exploitable pre-authentication.\n\nAdd bounds validation ensuring sizeof(*data) + 2*hl + dhvlen \u0026lt;= tl before\nany access to the variable-length fields.\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.(CVE-2026-64319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page\n\nnvmet_execute_disc_get_log_page() validates only the dword alignment\nof the host-supplied Log Page Offset (lpo).  The 64-bit offset is then\nadded to a small kzalloc\u0026apos;d buffer that holds the discovery log page\nand the result is passed straight to nvmet_copy_to_sgl(), which\nmemcpy()s data_len bytes out to the host with no source-side bound\ncheck:\n\n    u64 offset      = nvmet_get_log_page_offset(req-\u0026gt;cmd);  /* 64-bit host */\n    size_t data_len = nvmet_get_log_page_len(req-\u0026gt;cmd);     /* 32-bit host */\n    ...\n    if (offset \u0026amp; 0x3) { ... }                               /* only check */\n    ...\n    alloc_len = sizeof(*hdr) + entry_size * discovery_log_entries(req);\n    buffer = kzalloc(alloc_len, GFP_KERNEL);\n    ...\n    status = nvmet_copy_to_sgl(req, 0, buffer + offset, data_len);\n\nThe Discovery controller is unauthenticated -- nvmet_host_allowed()\nreturns true unconditionally for the discovery subsystem -- so the call\nis reachable pre-authentication by any TCP/RDMA/FC peer that can reach\nthe nvmet target.  With a discovery log page of ~1 KiB, an attacker\nrequesting up to 4 KiB starting at offset == alloc_len reads the next\nslab page out and gets its content returned over the fabric (an\nempirical run on a default nvmet-tcp loopback target leaked 81\ncanonical kernel pointers in one Get Log Page response).  Pointing the\noffset at unmapped kernel memory faults the in-kernel memcpy and\ncrashes (or panics, on panic_on_oops=1) the target host instead.\n\nThe attacker-controlled source-side offset pattern\n\u0026quot;nvmet_copy_to_sgl(req, 0, buffer + ATTACKER_OFFSET, ...)\u0026quot; is unique\nto nvmet_execute_disc_get_log_page in the entire nvmet codebase: every\nother Get Log Page handler in admin-cmd.c either ignores lpo (and\nsilently starts every response at offset 0) or tracks a local\ndestination offset with a fixed source pointer.\n\nValidate the host-supplied offset against the log page size, cap the\ncopy length to what is actually available, and zero-fill any remainder\nof the host transfer buffer.  The zero-fill matches the existing\nshort-response pattern in nvmet_execute_get_log_changed_ns()\n(admin-cmd.c) and prevents leaking transport SGL contents when the\nhost asks for more bytes than the log page contains.(CVE-2026-64320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudf: validate sparing table length as an entry count, not a byte count\n\nudf_load_sparable_map() accepts a sparing table when\n\n\tsizeof(*st) + le16_to_cpu(st-\u0026gt;reallocationTableLen) \u0026gt; sb-\u0026gt;s_blocksize\n\nis false, i.e. it treats reallocationTableLen as a number of BYTES that\nmust fit in the block.  But the table is walked as an array of 8-byte\nsparingEntry elements:\n\n\tfor (i = 0; i \u0026lt; le16_to_cpu(st-\u0026gt;reallocationTableLen); i++) {\n\t\tstruct sparingEntry *entry = \u0026amp;st-\u0026gt;mapEntry[i];\n\t\t... entry-\u0026gt;origLocation ...\n\t}\n\nin udf_get_pblock_spar15() and udf_relocate_blocks().  A\nreallocationTableLen of N therefore passes the check whenever\nsizeof(*st) + N \u0026lt;= blocksize, yet the consumers index\nsizeof(*st) + N * sizeof(struct sparingEntry) bytes -- up to ~8x the\nblock.  On a crafted UDF image this is an out-of-bounds read in\nudf_get_pblock_spar15(); udf_relocate_blocks() additionally feeds the\nsame length to udf_update_tag(), whose crc_itu_t() reads far past the\nblock, and its memmove() through st-\u0026gt;mapEntry[] is an out-of-bounds\nwrite.\n\nValidate reallocationTableLen as the entry count it is, with\nstruct_size().(CVE-2026-64322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudf: validate VAT header length against the VAT inode size\n\nudf_load_vat() takes the virtual partition\u0026apos;s start offset straight from\nthe on-disk VAT 2.0 header without checking it against the VAT inode\nsize:\n\n\tmap-\u0026gt;s_type_specific.s_virtual.s_start_offset =\n\t\tle16_to_cpu(vat20-\u0026gt;lengthHeader);\n\tmap-\u0026gt;s_type_specific.s_virtual.s_num_entries =\n\t\t(sbi-\u0026gt;s_vat_inode-\u0026gt;i_size -\n\t\t\tmap-\u0026gt;s_type_specific.s_virtual.s_start_offset) \u0026gt;\u0026gt; 2;\n\nlengthHeader is a fully attacker-controlled 16-bit value.  If it exceeds\nthe VAT inode size, the s_num_entries subtraction underflows to a huge\ncount, which defeats the \u0026quot;block \u0026gt; s_num_entries\u0026quot; bound in\nudf_get_pblock_virt15(); and on the ICB-inline path that function reads\n\n\t((__le32 *)(iinfo-\u0026gt;i_data + s_start_offset))[block]\n\nso a large s_start_offset indexes past the inode\u0026apos;s in-ICB data.  Mounting\na crafted UDF image with a virtual (VAT) partition then triggers an\nout-of-bounds read.\n\nReject a VAT whose header length does not leave room for at least one\nentry within the VAT inode.(CVE-2026-64323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudf: validate free block extents against the partition length\n\nudf_free_blocks() checks the logical block number and count against the\npartition length, but drops the extent offset from that final bound.  A\ncrafted extent can pass the guard while logicalBlockNum + offset + count\npoints past the partition, which later indexes past the space bitmap\narray.\n\nA single ftruncate(2) on a file backed by such an extent reliably\npanics the kernel.  This is a local availability issue.  On desktop\nsystems where UDisks/polkit allows the active user to mount removable\nUDF media without CAP_SYS_ADMIN, an unprivileged local user can supply\nthe crafted filesystem and trigger the panic by truncating a writable\nfile on it.  Systems that require root or CAP_SYS_ADMIN to mount the\nimage have a higher prerequisite.\n\nNo confidentiality or integrity impact is claimed: the reproduced\nprimitive is an out-of-bounds read of a bitmap pointer slot followed by\na kernel panic.\n\nUse the already computed logicalBlockNum + offset + count value for the\npartition length check.  Also make load_block_bitmap() reject an\nout-of-range block group before indexing s_block_bitmap[], so corrupted\ncallers cannot walk past the flexible array.(CVE-2026-64324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject fragmented frames in devmap\n\nDevmap broadcast redirects clone the packet for all but the last\ndestination.\n\nFor native XDP, that clone path copies only the linear xdp_frame data,\nwhile fragmented frames keep skb_shared_info in tailroom outside the\nlinear area. Cloning such a frame leaves XDP_FLAGS_HAS_FRAGS set but\nwithout valid frag metadata, and the later free path can interpret\nuninitialized tail data as skb_shared_info, leading to an out-of-bounds\naccess during frame return.\n\nReject fragmented native XDP frames in dev_map_enqueue_clone().\n\nAdd the same restriction to the generic XDP clone path in\ndev_map_redirect_clone(). Generic XDP represents fragmented packets as\nnonlinear skbs, and rejecting them here keeps clone-based broadcast\nsupport aligned between native and generic XDP.(CVE-2026-64355)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: fix out-of-bounds bit access on mt_io_flags\n\nmt_io_flags is a single unsigned long, but mt_process_slot(),\nmt_release_pending_palms() and mt_release_contacts() use it as a\nper-slot bitmap indexed by the slot number. That slot number is only\nbounded by td-\u0026gt;maxcontacts, which is taken from the device\u0026apos;s\nContactCountMaximum feature report and can be up to 255, not by\nBITS_PER_LONG.\n\nAs a result, a multitouch device that advertises a large contact count\nmakes set_bit()/clear_bit() operate past the mt_io_flags word and\ncorrupt the adjacent members of struct mt_device. The sticky-fingers\nrelease timer is the easiest way to reach this. mt_release_contacts()\nruns\n\n\tfor (i = 0; i \u0026lt; mt-\u0026gt;num_slots; i++)\n\t\tclear_bit(i, \u0026amp;td-\u0026gt;mt_io_flags);\n\nwith num_slots == maxcontacts. For maxcontacts around 250 the loop\nclears the bits that overlap td-\u0026gt;applications.next, zeroing that list\nhead, and the list_for_each_entry() that immediately follows then\ndereferences NULL. The kernel panics from timer (softirq) context. On a\nKASAN build this shows up as a general protection fault in\nmt_release_contacts() with a null-ptr-deref at offset 0x58, which is\noffsetof(struct mt_application, num_received).\n\nThe state is reachable from an untrusted USB or Bluetooth HID\nmultitouch device; no local privileges are required.\n\nStore the per-slot active state in a separately allocated bitmap sized\nfor maxcontacts, the same pattern already used for pending_palm_slots,\nand keep only MT_IO_FLAGS_RUNNING in mt_io_flags. The two\n\u0026quot;mt_io_flags \u0026amp; MT_IO_SLOTS_MASK\u0026quot; arming checks become\nbitmap_empty(td-\u0026gt;active_slots, td-\u0026gt;maxcontacts).\n\nMove MT_IO_FLAGS_RUNNING back to bit 0. It was bumped to bit 32 by the\nsame commit to leave the low byte for the slot bits; with the slot bits\ngone it fits in bit 0 again, which also keeps it within the unsigned\nlong on 32-bit.(CVE-2026-64364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT\n\nRT migration is done aggressively. When a CPU schedules out a high\npriority RT task for a lower priority task, it will look to see if there\u0026apos;s\nany RT tasks that are waiting to run on another CPU that is of higher\npriority than the task this CPU is about to run. If it finds one, it will\npull that task over to the CPU and allow it to run there instead.\n\nNormally, this pulling is done by looking at the RT overloaded mask (rto)\nwhich contains all the CPUs in the scheduler domain with RT tasks that are\nwaiting to run due to a higher priority RT task currently running on their\nCPU. The CPU that is about to schedule a lower priority task will grab the\nrq lock of the overloaded CPU and move the RT task from that CPU\u0026apos;s runqueue\nto the local one and schedule the higher priority RT task.\n\nThis caused issues when a lot of CPUs would schedule a lower priority task\nat the same time. They would all try to grab the same runqueue lock of\nthe CPU with the overloaded RT tasks. Only the first CPU that got in will\nget that task. All the others would wait until they got the runqueue lock\nand see there\u0026apos;s nothing to pull and do nothing. On systems with lots of\nCPUs, this caused a large latency (up to 500us) which is beyond what\nPREEMPT_RT is to allow.\n\nThe solution to that was to create an RT_PUSH_IPI logic. When any CPU\nwanted to pull a task, instead of grabbing the runqueue lock of the\noverloaded CPU, it would start by sending an IPI to the overloaded CPU,\nand that IPI handler would have the CPU with the waiting RT task do a push\ninstead. Then that handler would send an IPI to the next CPU with\noverloaded RT tasks, and so on. Note, after the first CPU starts this\nprocess, if another CPU wanted to do a pull, it would see that the process\nhas already begun and would only increment a counter to have the IPIs\ncontinue again.\n\nThe RT_PUSH_IPI solved the latency problem with PREEMPT_RT but could cause\na new issue with non PREEMPT_RT. Namely, softirqs run in a threaded\ncontext on PREEMPT_RT but they can run in an interrupt context in non-RT.\n\nIf an IPI lands on a CPU that has just woken up multiple RT tasks and the\ncurrent CPU is running a non RT or a low priority RT task, instead of\ndoing a push, it would simply do a schedule on that CPU. But if a softirq\nwas also executing on this CPU, the schedule would need to wait until the\nsoftirq finished. Until then, the CPU would still be considered overloaded\nas there are RT tasks still waiting to run on it.\n\nA live lock occurred on a workload that was doing heavy networking traffic\non a large machine where the softirqs would run 500us out of 750us. And it\nwould also be waking up RT tasks, causing the RT pull logic to be\nconstantly executed.\n\nWhen a softirq triggered on a CPU with RT tasks queued but not running\nyet, and the other CPUs would see this CPU as being overloaded, they would\nsend an IPI over to it. The CPU would notice that the waiting RT tasks are\nof higher priority than the currently running task and simply schedule\nthat CPU instead. But because the softirq was executing, before it could\nschedule, it would receive another IPI to do the same. The amount of IPIs\nwould slow down the currently running softirq so much that before it could\nreturn back to task context, it would execute another softirq never\nallowing the CPU to schedule. This live locked that CPU.\n\nAs RT_PUSH_IPI was created to help PREEMPT_RT, make it default off if\nPREEMPT_RT is not enabled.(CVE-2026-64374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwriteback: fix race between cgroup_writeback_umount() and inode_switch_wbs()\n\nWhen a container exits, the following BUG_ON() is occasionally triggered:\n\n==================================================================\n VFS: Busy inodes after unmount of sdb (ext4)\n ------------[ cut here ]------------\n kernel BUG at fs/super.c:695!\n CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1\n pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\n pc : generic_shutdown_super+0xf0/0x100\n lr : generic_shutdown_super+0xf0/0x100\n Call trace:\n  generic_shutdown_super+0xf0/0x100\n  kill_block_super+0x20/0x48\n  ext4_kill_sb+0x28/0x60\n  deactivate_locked_super+0x54/0x130\n  deactivate_super+0x84/0xa0\n  cleanup_mnt+0xa4/0x140\n  __cleanup_mnt+0x18/0x28\n  task_work_run+0x78/0xe0\n  do_notify_resume+0x204/0x240\n==================================================================\n\nThe root cause is a race between cgroup_writeback_umount() and\ninode_switch_wbs()/cleanup_offline_cgwb(). There is a window between\ninode_prepare_wbs_switch() returning true and the subsequent\nwb_queue_isw() call. Following is the process that triggers the issue:\n\n      CPU A (umount)           |          CPU B (writeback)\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n                                 inode_switch_wbs/cleanup_offline_cgwb\n                                  atomic_inc(\u0026amp;isw_nr_in_flight)\n                                  inode_prepare_wbs_switch\n                                   -\u0026gt; passes SB_ACTIVE check\n                                   __iget(inode)\n generic_shutdown_super\n  sb-\u0026gt;s_flags \u0026amp;= ~SB_ACTIVE\n  cgroup_writeback_umount(sb)\n   smp_mb()\n   atomic_read(\u0026amp;isw_nr_in_flight)\n   rcu_barrier()\n    -\u0026gt; no pending RCU callbacks\n   flush_workqueue(isw_wq)\n    -\u0026gt; nothing queued, returns\n  evict_inodes(sb)\n   -\u0026gt; Inode skipped as isw still holds a ref.\n  sop-\u0026gt;put_super(sb)\n   /* destroys percpu counters */\n  -\u0026gt; VFS: Busy inodes after unmount!\n                                  wb_queue_isw()\n                                   queue_work(isw_wq, ...)\n                                  /* later in work function */\n                                  inode_switch_wbs_work_fn\n                                   process_inode_switch_wbs\n                                    iput() -\u0026gt; evict\n                                     percpu_counter_dec() // UAF!\n\nFix this by extending the RCU read-side critical section in\ninode_switch_wbs() and cleanup_offline_cgwb() to cover from\ninode_prepare_wbs_switch() through wb_queue_isw().  Since there is\nno sleep in this window, rcu_read_lock() can be used.  Then add a\nsynchronize_rcu() in cgroup_writeback_umount() before the existing\nrcu_barrier(), so that all in-flight switchers that have passed the\nSB_ACTIVE check have completed queue_work() before flush_workqueue()\nis called.\n\nThe existing rcu_barrier() is intentionally retained so this fix can\nbe backported unchanged to stable kernels (5.10.y, 6.6.y, ...) that\nstill queue switches via queue_rcu_work(). It is a no-op on current\nmainline (since commit e1b849cfa6b6 (\u0026quot;writeback: Avoid contention on\nwb-\u0026gt;list_lock when switching inodes\u0026quot;)) and is removed in a follow-up\npatch.(CVE-2026-64378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: mask server-provided mode to 07777 in modefromsid\n\nWhen modefromsid is active, parse_dacl() applies the server-provided\nsub_auth[2] value from the NFS mode SID to cf_mode without masking to\n07777. Apply the correct masking, same as in the read path.(CVE-2026-64379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: harden POSIX SID length parsing\n\nposix_info_sid_size() reads sid[1] to obtain the subauthority count,\nbut its existing boundary check still accepts buffers with only one\nremaining byte. Require two bytes before reading sid[1] so all client\npaths that reuse the helper reject truncated POSIX SIDs safely.(CVE-2026-64380)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix double-free in SMB2_open() replay\n\nA response-bearing attempt can return a replayable error and free its\nresponse buffer. If SMB2_open_init() fails before the next send, cleanup\nretains the previous buffer type and frees that response again.\n\nReset response bookkeeping before each attempt to prevent the stale free.(CVE-2026-64382)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix double-free in SMB2_flush() replay\n\nSMB2_flush() keeps its response buffer bookkeeping across replay\nattempts. If a replayable flush response is received and the retry then\nfails before cifs_send_recv() stores a replacement response, flush_exit\nwill free the stale response pointer a second time.\n\nReinitialize resp_buftype and rsp_iov at the top of the replay loop so\ncleanup only acts on response state produced by the current attempt.\nThis fixes a double-free without changing replay handling for successful\nrequests.(CVE-2026-64383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix change notify replay double-free\n\nA response-bearing attempt can return a replayable error and free its\nresponse buffer. If SMB2_notify_init() fails before the next send, cleanup\nretains the previous buffer type and frees that response again.\n\nReset response bookkeeping before each attempt to prevent the stale free.(CVE-2026-64384)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix double-free in SMB2_ioctl() replay\n\nA response-bearing attempt can return a replayable error and free its\nresponse buffer. If SMB2_ioctl_init() fails before the next send, cleanup\nretains the previous buffer type and frees that response again.\n\nReset response bookkeeping before each attempt to prevent the stale free.(CVE-2026-64385)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix query_info() replay double-free\n\nA response-bearing attempt can return a replayable error and free its\nresponse buffer. If SMB2_query_info_init() fails before the next send,\ncleanup retains the previous buffer type and frees that response again.\n\nReset response bookkeeping before each attempt to prevent the stale free.(CVE-2026-64386)\n\nIn the Linux kernel, an out-of-bounds read vulnerability exists in the SMB client. smb2_check_message() has a long-standing quirk that accepts a response whose calculated length is one byte larger than the bytes actually received (\u0026quot;server can return one byte more due to implied bcc[0]\u0026quot;). This was introduced to accommodate servers that omit the trailing bcc[0] overlap byte when no data area is present. However, the exemption is applied unconditionally, regardless of whether the command actually carries a data area (has_smb2_data_area[]). When a response with a data area is subject to the +1 exemption, the reported data can extend one byte beyond the bytes actually received, causing the subsequent decoder to read past the end of the receive buffer. This is reachable during NEGOTIATE and SESSION_SETUP, before the session is established. The resulting out-of-bounds reads are visible under KASAN when mounting against a non-conforming server, affecting both the SPNEGO/negTokenInit and the NTLMSSP challenge decoders.(CVE-2026-64448)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwrng: virtio: clamp device-reported used.len at copy_data()\n\nrandom_recv_done() stores the device-reported used.len directly into\nvi-\u0026gt;data_avail.  copy_data() then indexes vi-\u0026gt;data[] using\nvi-\u0026gt;data_idx (advanced by previous copy_data() calls) and issues a\nmemcpy() without re-validating either value against the posted\nbuffer size sizeof(vi-\u0026gt;data) (SMP_CACHE_BYTES bytes, typically 32\nor 64).\n\nA malicious or buggy virtio-rng backend can set used.len beyond\nsizeof(vi-\u0026gt;data), steering the memcpy() past the end of the inline\narray into adjacent kmalloc-1k slab bytes.  hwrng_fillfn() mixes\nthose bytes into the guest RNG, and guest root can also observe\nthem directly via /dev/hwrng.\n\nConcrete impact is inside the guest:\n\n - Memory-safety / hardening: any virtio-rng backend that\n   over-reports used.len causes the driver to read past vi-\u0026gt;data\n   into unrelated slab contents.  hwrng_fillfn() is a kernel thread\n   that runs as soon as the device is probed; no guest userspace\n   interaction is required to first-trigger the OOB.\n\n - Cross-boundary leak (confidential-compute threat model): a\n   malicious hypervisor cooperating with a malicious or compromised\n   guest root userspace can use /dev/hwrng as a leak channel for\n   guest-kernel heap data.  The host sets a large used.len, guest\n   root reads /dev/hwrng, and the returned bytes contain guest\n   kernel slab contents that were adjacent to vi-\u0026gt;data.  In\n   practice, confidential-compute guests (SEV-SNP, TDX) usually\n   disable virtio-rng entirely, so this path is narrow, but the\n   fix is still worth carrying because the underlying\n   memory-safety bug contaminates the guest RNG on any host.\n\nKASAN confirms the OOB on a 7.1-rc4 guest whose virtio-rng backend\nhas been patched to report used.len = 0x10000:\n\n  BUG: KASAN: slab-out-of-bounds in virtio_read+0x394/0x5d0\n  Read of size 64 at addr ffff88800ae0ba20 by task hwrng/52\n  Call Trace:\n   __asan_memcpy+0x23/0x60\n   virtio_read+0x394/0x5d0\n   hwrng_fillfn+0xb2/0x470\n   kthread+0x2cc/0x3a0\n  Allocated by task 1:\n   probe_common+0xa5/0x660\n   virtio_dev_probe+0x549/0xbc0\n  The buggy address belongs to the object at ffff88800ae0b800\n   which belongs to the cache kmalloc-1k of size 1024\n  The buggy address is located 0 bytes to the right of\n   allocated 544-byte region [ffff88800ae0b800, ffff88800ae0ba20)\n\nSame class of bug as commit c04db81cd028 (\u0026quot;net/9p: Fix buffer\noverflow in USB transport layer\u0026quot;), which hardened\nusb9pfs_rx_complete() against unchecked device-reported length in\nthe USB 9p transport.\n\nWith the clamp at point of use and array_index_nospec() in place,\nthe same harness boots cleanly: copy_data() returns zero for the\nbogus report, the device-supplied bytes after data_idx are\ndiscarded, and the driver issues a fresh request.(CVE-2026-64456)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: hda/cs35l41: Fix firmware load work teardown\n\ncs35l41_hda creates ALSA controls whose private data points at the\ncs35l41_hda object. The firmware load control can also queue\nfw_load_work.\n\nThose controls are not removed on component unbind, and device remove\nonly cancels fw_load_work through cs35l41_remove_dsp(). That helper is\nskipped when halo_initialized is false. With firmware_autostart\ndisabled, a firmware load can be requested before the DSP has been\ninitialized. If the component or device is removed before the queued\nwork runs, the worker can run after teardown and dereference driver\nstate that is no longer valid.\n\nTrack the created controls and remove them on unbind so no new control\ncallback can reach the driver data or queue more work. Then cancel\nfw_load_work to drain any request that was already queued. Also cancel\nthe work unconditionally during device remove before runtime PM teardown.(CVE-2026-64481)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: event: Fix event FIFO reset race\n\n`iio_event_getfd()` creates the event file descriptor with\n`anon_inode_getfd()`, which allocates a new fd, creates the anonymous\nfile and installs it in the process fd table before returning to the\ncaller.\n\nThe IIO code resets the event FIFO after `anon_inode_getfd()` has returned,\nbut before `IIO_GET_EVENT_FD_IOCTL` has copied the fd number to userspace.\nBut since fd tables are shared between threads, another thread can guess\nthe newly allocated fd number and issue a `read()` on it as soon as the fd\nhas been installed.\n\nThis means the `kfifo_to_user()` in `iio_event_chrdev_read()` can run in\nparallel with the `kfifo_reset_out()` in `iio_event_getfd()`.\n\nThe kfifo documentation says that `kfifo_reset_out()` is only safe when it\nis called from the reader thread and there is only one concurrent reader.\nOtherwise it is dangerous and must be handled in the same way as\n`kfifo_reset()`.\n\nIf that happens, `kfifo_to_user()` can advance the FIFO `out` index based\non state from before the reset, after the reset has already moved the `out`\nindex to the current `in` index. That can leave the FIFO with an `out`\nindex past the `in` index. A later `read()` can then see an underflowed\nFIFO length and copy more data than the event FIFO buffer contains. This\ncan result in an out-of-bounds read and leak adjacent kernel memory to\nuserspace.\n\nMove the FIFO reset before `anon_inode_getfd()`. At that point the event fd is\nmarked busy, but the new fd has not been installed yet, so userspace cannot\naccess it while the FIFO is reset.(CVE-2026-64496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: reject oversized nested action attrs\n\nOpen vSwitch stores generated flow actions as nlattrs, whose nla_len\nfield is u16. Commit a1e64addf3ff (\u0026quot;net: openvswitch: remove\nmisbehaving actions length check\u0026quot;) allowed the total sw_flow_actions\nstream to grow beyond 64 KiB, which is valid, but also removed the last\nguard preventing a generated nested action attribute from exceeding\nU16_MAX.\n\nAn oversized generated container can thus be closed with a truncated\nnla_len. A later dump or teardown then walks a structurally different\nstream than the one that was validated. In particular, an oversized\nnested CLONE/CT action may cause subsequent bytes in the generated\nstream to be interpreted as independent actions.\n\nKeep the larger total-action-stream behavior, but make nested action\nclose reject generated containers that do not fit in nla_len, and return\nthe error through all callers. For recursive SAMPLE, CLONE, DEC_TTL, and\nCHECK_PKT_LEN builders, trim resource-owning action-list tails in reverse\nconstruction order before discarding failed wrappers, so resources copied\ninto the rejected tails are released before the wrappers are removed.\n\nMost failed outer wrappers are discarded by truncating actions_len after\nchild resources have been released. CHECK_PKT_LEN also trims its parent\nafter branch resources are gone. SET/TUNNEL close failures unwind their\nknown tun_dst ownership directly, and SET_TO_MASKED has no external\nownership and truncates on close failure.(CVE-2026-64531)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nperf/core: Detach event groups during remove_on_exec\\n\\nperf_event_remove_on_exec() removes events by calling\\nperf_event_exit_event(). For top-level events, this removes the event from\\nthe context with DETACH_EXIT only.\\n\\nThis can leave inconsistent group state when a removed event is a group\\nleader and the group contains siblings without remove_on_exec. If the group\\nwas active, the surviving siblings can remain active and attached to the\\nremoved leader\u0026apos;s sibling list, but are no longer represented by a valid\\ngroup leader on the PMU context active lists.\\n\\nA later close of the removed leader uses DETACH_GROUP and can promote the\\nstill-active siblings from this stale group state. The next schedule-in can\\nthen add an already-linked active_list entry again, corrupting the PMU\\ncontext active list.\\n\\nWith DEBUG_LIST enabled, this is caught as a list_add double-add in\\nmerge_sched_in().\\n\\nFix this by detaching group relationships when remove_on_exec removes an\\nevent. This preserves the existing task-exit and revoke behavior, while\\nensuring surviving siblings are ungrouped before the removed event leaves\\nthe context.(CVE-2026-64556)\n\nIn the Linux kernel, a use-after-free (UAF) vulnerability exists caused by a non-leader exec() race condition in posix-cpu-timers. When sys_timer_delete() observes the old leader, while de_thread() executes switch_leader() and releases the old leader, a race condition occurs. Specifically, posix_cpu_timer_del() in sys_timer_delete() obtains the old leader via pid_task(), while de_thread() is executing release_task(old_leader) and setting old_leader-\u0026gt;sighand = NULL. When lock_task_sighand() returns NULL, sys_timer_delete() frees the posix timer object. However, if the timer was armed and enqueued in p-\u0026gt;signal (a TGID targeted timer is inherited on exec()), run_posix_cpu_timers() or other timerqueue add/delete operations will access the freed object\u0026apos;s timerqueue node, resulting in a use-after-free. This issue similarly affects posix_cpu_timer_set() and posix_cpu_timer_rearm(). The history of this vulnerability goes back to the early days of posix CPU timers implementation.(CVE-2026-64560)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: x86: Check for invalid/obsolete root *after* making MMU pages available\\n\\nCheck for a \\\u0026quot;stale\\\u0026quot; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is \\\u0026quot;fine\\\u0026quot;, but because child shadow pages inherit their parent\u0026apos;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM\u0026apos;s invariant that invalid pages are never on the list of active MMU pages.\\n\\nNote, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, \\\u0026quot;KVM: MMU: ignore zapped root pagetables\\\u0026quot;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can\u0026apos;t be on the list of active pages.\\n\\nNote #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.(CVE-2026-64561)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix double-free in SMB2_close() replay\n\nA response-bearing attempt can return a replayable error and free its\nresponse buffer. If SMB2_close_init() fails before the next send, cleanup\nretains the previous buffer type and frees that response again.\n\nReset response bookkeeping before each attempt to prevent the stale free.(CVE-2026-64597)\n\nIn the Linux kernel, the following vulnerability has been resolved: ipvs: reload ip header after head reallocation. __ip_vs_get_out_rt() calls skb_ensure_writable() which may reallocate skb-\u0026gt;head, causing the previously obtained IP header pointer to become a dangling pointer, leading to a use-after-free vulnerability.(CVE-2026-68476)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: fix more places with wrong ipv6 transport offsets\n\nSashiko reports for more incorrect IPv6 transport offsets.\n\nThe app code for TCP was assuming IPv4 network header\neven after the ipvsh argument was provided. This can\ncause problems with apps over IPv6. As for the only\nofficial app in the kernel tree (FTP) this problem is\nharmless because we use Netfilter to mangle the FTP\nports and we do not adjust the TCP seq numbers.\n\nAlso, provide correct offset of the ICMPV6 header in\nip_vs_out_icmp_v6() for correct checksum checks when\nthe IPv6 packet has extension headers.(CVE-2026-68477)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: use parsed transport offset in SCTP state lookup\n\nset_sctp_state() reads the SCTP chunk header again in order to drive the\nIPVS SCTP state table. For IPv6 it computes the offset with\nsizeof(struct ipv6hdr), while the surrounding IPVS code uses iph.len from\nip_vs_fill_iph_skb(), where ipv6_find_hdr() has already skipped\nextension headers and found the real transport header.\n\nThis makes the state machine read from the wrong offset for IPv6 SCTP\npackets that carry extension headers. For example, an INIT packet with an\n8-byte destination options header can be scheduled correctly by\nsctp_conn_schedule(), but set_sctp_state() reads the first byte of the\nSCTP verification tag as a DATA chunk type. The connection then moves\nfrom NONE to ESTABLISHED instead of INIT1, gets the longer established\ntimeout, and updates the active/inactive destination counters\nincorrectly. This happens even though the SCTP handshake has not\ncompleted.\n\nUse the parsed transport offset passed down from ip_vs_set_state() for\nthe SCTP chunk-header lookup. For IPv4 and IPv6 packets without\nextension headers this preserves the existing offset.(CVE-2026-72021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nieee802154: admin-gate legacy LLSEC dump operations\n\nIn net/ieee802154/netlink.c, the legacy IEEE802154_NL family ops table\nbuilds the LLSEC dump entries (LLSEC_LIST_KEY, LLSEC_LIST_DEV,\nLLSEC_LIST_DEVKEY, LLSEC_LIST_SECLEVEL) with IEEE802154_DUMP() which\nsets no .flags, so generic netlink runs them ungated. The modern\nnl802154 family admin-gates the equivalent reads via\nNL802154_CMD_GET_SEC_KEY and friends with .flags = GENL_ADMIN_PERM.\n\nAny local uid that can open AF_NETLINK / NETLINK_GENERIC can resolve\nthe \u0026quot;802.15.4 MAC\u0026quot; family and dump LLSEC_LIST_KEY on any wpan netdev\nthat has an LLSEC key installed; the dump handler writes the raw\n16-byte AES-128 key bytes (IEEE802154_ATTR_LLSEC_KEY_BYTES, copied\nverbatim from struct ieee802154_llsec_key.key) into the reply.\nRecovering the AES key compromises 802.15.4 LLSEC link confidentiality\nand authenticity, since LLSEC uses CCM* and the same key authenticates\nand encrypts frames.\n\nImpact: any local uid with no capabilities can read the raw 16-byte\nAES-128 LLSEC key from the kernel keytable on any wpan netdev that has\nan administrator-installed LLSEC key, by issuing an LLSEC_LIST_KEY\ndump on the legacy IEEE802154_NL generic-netlink family.\n\nIntroduce IEEE802154_DUMP_PRIV() mirroring IEEE802154_DUMP() but\nsetting .flags = GENL_ADMIN_PERM, and use it for the four LLSEC dump\nentries. LIST_PHY and LIST_IFACE retain IEEE802154_DUMP() because the\nmodern nl802154 family exposes their equivalents to unprivileged\nreaders by design (NL802154_CMD_GET_WPAN_PHY and\nNL802154_CMD_GET_INTERFACE carry \u0026quot;can be retrieved by unprivileged\nusers\u0026quot; annotations).(CVE-2026-72049)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink\n\nip6gre_changelink() and ip6erspan_changelink() operate on at most two\nnetns, dev_net(dev) and the tunnel link netns t-\u0026gt;net. They differ once\nthe device is created in or moved to a netns other than the one the\nrequest runs in. The rtnl changelink path checks CAP_NET_ADMIN only\nagainst dev_net(dev), so a caller privileged there but not in t-\u0026gt;net can\nrewrite a tunnel that lives in t-\u0026gt;net.\n\nGate both ops on rtnl_dev_link_net_capable() at their top, before any\nattribute is parsed.(CVE-2026-72052)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipip: require CAP_NET_ADMIN in the device netns for changelink\n\nipip_changelink() operates on at most two netns, dev_net(dev) and the\ntunnel link netns t-\u0026gt;net. They differ once the device is created in or\nmoved to a netns other than the one the request runs in. The rtnl\nchangelink path checks CAP_NET_ADMIN only against dev_net(dev), so a\ncaller privileged there but not in t-\u0026gt;net can rewrite a tunnel that\nlives in t-\u0026gt;net.\n\nGate ipip_changelink() on rtnl_dev_link_net_capable() at its top,\nbefore any attribute is parsed.(CVE-2026-72053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ip_vti: require CAP_NET_ADMIN in the device netns for changelink\n\nvti_changelink() operates on at most two netns, dev_net(dev) and the\ntunnel link netns t-\u0026gt;net. They differ once the device is created in or\nmoved to a netns other than the one the request runs in. The rtnl\nchangelink path checks CAP_NET_ADMIN only against dev_net(dev), so a\ncaller privileged there but not in t-\u0026gt;net can rewrite a tunnel that\nlives in t-\u0026gt;net.\n\nGate vti_changelink() on rtnl_dev_link_net_capable() at its top,\nbefore any attribute is parsed.(CVE-2026-72054)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sit: require CAP_NET_ADMIN in the device netns for changelink\n\nipip6_changelink() operates on at most two netns, dev_net(dev) and the\ntunnel link netns t-\u0026gt;net. They differ once the device is created in or\nmoved to a netns other than the one the request runs in. The rtnl\nchangelink path checks CAP_NET_ADMIN only against dev_net(dev), so a\ncaller privileged there but not in t-\u0026gt;net can rewrite a tunnel that\nlives in t-\u0026gt;net.\n\nGate ipip6_changelink() on rtnl_dev_link_net_capable() at its top,\nbefore any attribute is parsed. sit was the one tunnel type not covered\nby the recent series that added this check to the other changelink()\nhandlers.(CVE-2026-72061)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete\n\nWhen an offloaded MACsec RX SC is deleted, macsec_del_rxsc_ctx() freed\nthe per-SC metadata_dst with metadata_dst_free(), which kfree()s the\nobject unconditionally and ignores the dst reference count. The RX\ndatapath in mlx5e_macsec_offload_handle_rx_skb() looks up the SC under\nrcu_read_lock() via xa_load(), takes a reference with dst_hold() and\nattaches the dst to the skb with skb_dst_set(). A reader that already\nobtained the rx_sc pointer can race with the delete path and operate on\nfreed memory.\n\nFix the owner side by dropping the reference with dst_release() instead\nof freeing unconditionally, and convert the RX datapath to\ndst_hold_safe() so a reader racing the SC delete cannot attach a dst\nwhose last reference was just dropped; only attach it when a reference\nwas actually taken.\n\nmlx5e_macsec_add_rxsc() also published sc_xarray_element via xa_alloc()\nbefore rx_sc-\u0026gt;md_dst was allocated and initialised, so a datapath reader\nthat looked the SC up by fs_id could observe rx_sc with md_dst still\nNULL or, on weakly-ordered architectures, a non-NULL md_dst pointer\nwhose contents were not yet visible. NULL-check the xa_load() result and\nmd_dst on the datapath, and reorder add_rxsc() so the xa_alloc() publish\nhappens only after md_dst is fully initialised; the xarray RCU publish\nthen pairs with the rcu_read_lock()/xa_load() in the datapath.\n\nNote: macsec_del_rxsc_ctx() also kfree()s rx_sc-\u0026gt;sc_xarray_element\nwithout an RCU grace period while the same datapath reads it under\nrcu_read_lock(); that is a separate pre-existing issue left to a\nfollow-up patch.\n\nFound by 0sec automated security-research tooling (https://0sec.ai).(CVE-2026-72072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm-log: fix a bitset_size overflow on 32bit machines\n\nCommit c20e36b7631d (\u0026quot;dm log: fix out-of-bounds write due to\nregion_count overflow\u0026quot;) made sure that region_count could fit in an\nunsigned int. But the bitmap memory isn\u0026apos;t allocated based on\nregion_count. It uses bitset_size (a size_t variable). The first step of\ncalculating bitset_size is to set it to region_count, rounded up to a\nmultiple of BITS_PER_LONG. If region_size is less than BITS_PER_LONG\nsmaller than UINT_MAX, it will get rounded up to 2^32. On a 32bit\narchitecture, this will make bitset_size wrap around to 0 and fail,\ndespite region_count being valid.\n\nSince bitset_size gets divided by 8, it can hold any valid region_count.\nIt just needs a special case to handle the rollover. If it is 0, the\nvalue rolled over, and bitset size should be set to the number of bytes\nneeded to hold 2^32 bits.(CVE-2026-72105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf,fork: wipe -\u0026gt;bpf_storage before bailouts that access it\n\nCurrently, copy_process() can bail out to free_task() before p-\u0026gt;bpf_storage\nhas been initialized, with this call graph (shown here for the\n!CONFIG_MEMCG case):\n\ncopy_process\n  dup_task_struct\n    arch_dup_task_struct\n      [copies the entire task_struct, including -\u0026gt;bpf_storage member]\n  [RLIMIT_NPROC check fails]\n  delayed_free_task\n    free_task\n      bpf_task_storage_free\n        rcu_dereference(task-\u0026gt;bpf_storage)\n        bpf_local_storage_destroy\n\nIn this case, the nascent task\u0026apos;s -\u0026gt;bpf_storage member that\nbpf_local_storage_destroy() operates on is a plain copy of the parent\u0026apos;s\n-\u0026gt;bpf_storage pointer, not a real initialized pointer.\nThis leads to badness (kernel hangs, UAF).\n\nThis is reachable as long as the process calling fork() has been inserted\ninto a task storage map.(CVE-2026-72110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-rdma: handle inline data with a nonzero offset\n\nnvmet_rdma_use_inline_sg() maps the host-controlled inline data offset\ninto the per-command inline scatterlist.  The bounds check admits any\noffset with off + len \u0026lt;= inline_data_size, but the mapping still assumes\nthe data begins in the first inline page:\n\n\tsg-\u0026gt;offset = off;\n\tsg-\u0026gt;length = min_t(int, len, PAGE_SIZE - off);\n\nWhen a port is configured with inline_data_size \u0026gt; PAGE_SIZE (settable up\nto max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size]\nmakes \u0026quot;PAGE_SIZE - off\u0026quot; underflow, so sg-\u0026gt;length is set to ~4 GiB and\nthe block backend reads far past the first inline page.  num_pages(len)\nalso ignores the offset, so an in-bounds offset whose [off, off+len)\nspan crosses a page boundary under-counts the scatterlist.\n\nMap the offset properly: split it into a page index and an in-page\noffset, start the scatterlist at that page, and size the page count from\npage_off + len.  Because the request scatterlist may now start at\ninline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL\nidentity test in nvmet_rdma_release_rsp() to a range test; otherwise the\npersistent inline scatterlist is mistaken for an allocated one and\nnvmet_req_free_sgls() frees an inline page (and warns in\nfree_large_kmalloc()).(CVE-2026-72129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Make the TPM character devices non-seekable\n\nThe TPM character devices expose a sequential command/response\ninterface, but their open handlers leave FMODE_PREAD and FMODE_PWRITE\nenabled.\n\nAfter a command leaves a response pending, pread(fd, buf, 16, 0x1400)\npasses 0x1400 as *off to tpm_common_read(). The transfer length is\nbounded by response_length, but the offset is used unchecked when\nforming data_buffer + *off. A sufficiently large offset therefore causes\nan out-of-bounds heap read through copy_to_user() and, if the copy\nsucceeds, an out-of-bounds zero-write through the following memset().\n\nPositional I/O does not provide coherent semantics for this interface.\nAn arbitrary pread offset cannot represent how much of a response has\nbeen consumed sequentially. The write callback always stores a command\nat the start of data_buffer, while pwrite() does not update file-\u0026gt;f_pos\nand can leave the sequential read cursor stale.\n\nCall nonseekable_open() from both open handlers. This removes\nFMODE_PREAD and FMODE_PWRITE, causing positional reads and writes to\nfail with -ESPIPE before reaching the TPM callbacks, and explicitly\nmarks the files non-seekable. Normal read() and write() continue to use\nthe existing sequential f_pos cursor, leaving the response state machine\nunchanged.\n\nTested on Linux 6.12 with KASAN and a swtpm TPM2 device:\n\n - sequential partial reads returned the complete response\n - pread() and preadv() with offset 0x1400 returned -ESPIPE\n - pwrite() and pwritev() with offset zero returned -ESPIPE\n - the pending response remained intact after the rejected operations\n - a subsequent normal command/response cycle completed normally\n - no KASAN report was produced.(CVE-2026-72135)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink\n\nxfrmi_changelink() operates on at most two netns, dev_net(dev) and the\ninterface link netns xi-\u0026gt;net. They differ once the device is created in\nor moved to a netns other than the one the request runs in. The rtnl\nchangelink path checks CAP_NET_ADMIN only against dev_net(dev), so a\ncaller privileged there but not in xi-\u0026gt;net can rewrite an interface that\nlives in xi-\u0026gt;net.\n\nGate xfrmi_changelink() on rtnl_dev_link_net_capable() at its top,\nbefore any attribute is parsed.(CVE-2026-72136)\n\nIn the Linux kernel, the following vulnerability has been resolved: net: thunderbolt: Fix frags[] overflow by bounding frame_count. tbnet_poll() assembles a multi-frame ThunderboltIP packet into one skb. The first frame goes into the skb linear area and every further frame is added as a page fragment. A packet of frame_count frames therefore ends up with frame_count - 1 fragments. tbnet_check_frame() only bounds the peer supplied frame_count to TBNET_RING_SIZE / 4 (64), which is far above MAX_SKB_FRAGS (17 by default). A peer that sends a packet of 19 or more small frames pushes nr_frags past MAX_SKB_FRAGS, so skb_add_rx_frag() writes past skb_shinfo()-\u0026gt;frags[] and corrupts memory after the shared info.(CVE-2026-72157)\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE. If DAX memory is hotplugged into an unoccupied subsection of an early section, section_activate() reuses the unoptimized boot memmap. However, compound_nr_pages() still assumes that vmemmap optimization is in effect and initializes only the reduced number of struct pages. As a result, the remaining tail struct pages are left uninitialized, which can later lead to unexpected behavior or crashes. Fix this by treating early sections as unoptimized when calculating how many struct pages to initialize.(CVE-2026-72172)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: Bound-check xdr_buf_to_bvec() stores before writing\n\nxdr_buf_to_bvec() writes a bio_vec into the caller\u0026apos;s array before\ntesting whether that slot is in range, and the head branch performs\nthe store with no check at all. When the caller\u0026apos;s budget is exactly\nused up, the next store lands one element past the end of the array.\nThe overflow label returns count - 1, which masks the surplus store\nbut cannot undo it.\n\nrq_bvec, the array passed by nfsd_vfs_write(), is allocated to\nexactly rq_maxpages entries with no slack. The OOB store can land in\nadjacent slab memory; the bv_len and bv_offset fields written there\nare derived from client-supplied RPC payload sizes.\n\nMove the in-range check ahead of the store in the head, page-loop,\nand tail branches. With the check at the top of each sequence, count\nis incremented only after a successful store, so the overflow label\ncan return count directly.(CVE-2026-72217)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: wait for in-flight TLS handshake callback when cancel loses race\n\nWhen wait_for_completion_interruptible_timeout() in\nsvc_tcp_handshake() returns 0 (timeout) or -ERESTARTSYS (signal) and\ntls_handshake_cancel() then returns false, handshake_complete() has\nwon the cancellation race: it has set HANDSHAKE_F_REQ_COMPLETED and\nis about to invoke svc_tcp_handshake_done(), but the callback\u0026apos;s\nside effects on xpt_flags and on svsk-\u0026gt;sk_handshake_done have not\nyet committed.\n\nThe current code reads xpt_flags immediately to decide whether the\nsession succeeded. Two races result.\n\nIf the callback has executed set_bit(XPT_TLS_SESSION) but not yet\nclear_bit(XPT_HANDSHAKE), svc_tcp_handshake() sees a session,\nenqueues the transport, and returns. svc_xprt_received() then\nclears XPT_BUSY, a worker thread picks the transport up, the\ndispatcher in svc_handle_xprt() observes XPT_HANDSHAKE still set,\nand xpo_handshake is invoked a second time. That svc_tcp_handshake()\ncalls init_completion(\u0026amp;svsk-\u0026gt;sk_handshake_done) while the original\ncallback concurrently calls complete_all() on it, corrupting the\nembedded swait_queue.\n\nIf the callback has set HANDSHAKE_F_REQ_COMPLETED but not yet\nentered svc_tcp_handshake_done(), svc_tcp_handshake() reads\nXPT_TLS_SESSION as clear and tears the connection down even though\nthe handshake is about to succeed.\n\nWait for the callback to commit before inspecting xpt_flags. The\ncompletion is guaranteed to fire because handshake_complete()\ninvokes svc_tcp_handshake_done() unconditionally once it has set\nHANDSHAKE_F_REQ_COMPLETED.(CVE-2026-72221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: pin svc_xprt across the asynchronous TLS handshake callback\n\nsvc_tcp_handshake() stores the raw svc_xprt pointer in\ntls_handshake_args.ta_data and submits the request through\ntls_server_hello_x509(). The handshake core takes only\nsock_hold(req-\u0026gt;hr_sk); nothing references the embedding struct\nsvc_sock that svc_tcp_handshake_done() reaches via container_of().\n\nTwo close races leave the in-flight callback writing through a freed\nsvc_sock. svc_sock_free() calls tls_handshake_cancel() and discards\nits return value: a false return means handshake_complete() has\nalready set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not have\nfinished, yet svc_sock_free() proceeds to kfree(svsk). The\ncancel-loser fall-through inside svc_tcp_handshake() itself produces\nthe same window: when wait_for_completion_interruptible_timeout()\nreturns \u0026lt;= 0 (timeout or signal) and tls_handshake_cancel() returns\nfalse, the function does not drain, returns, and svc_handle_xprt()\ncalls svc_xprt_received(), which clears XPT_BUSY and can drop the\nlast reference. A concurrent close then runs svc_sock_free() while\nsvc_tcp_handshake_done() is still updating xpt_flags and walking\nsvsk-\u0026gt;sk_handshake_done.\n\nThe corruption surfaces as set_bit/clear_bit RMW into the freed\nxpt_flags slab slot and as complete_all() walking and writing the\nfreed wait_queue_head_t list embedded in sk_handshake_done -- a\nslab-corruption primitive, not a benign read. The path is reachable\non any TLS-enabled NFS server whenever a connection close overlaps\nthe tlshd downcall delivery window; the interruptible wait means\nsignal delivery suffices, not just SVC_HANDSHAKE_TO expiry.\n\nTake svc_xprt_get(xprt) immediately before tls_server_hello_x509()\nso the in-flight callback owns its own reference. Release it on the\ntwo edges where the callback is guaranteed not to fire -- submission\nfailure from tls_server_hello_x509() and a successful\ntls_handshake_cancel() -- and at the tail of\nsvc_tcp_handshake_done() after complete_all().\n\n[cel: rewrote commit message to describe the actual change](CVE-2026-72222)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: retrieve ethhdr after potential skb realloc on RX\n\npskb_may_pull() in batadv_interface_rx() could reallocate the buffer behind\nthe skb. Variables which were pointing to the old buffer need to be\nreassigned to avoid an use-after-free.\n\nThis was done correctly for the VLAN header but missed for the ethernet\nheader which is later used for the TT and AP isolation handling.(CVE-2026-72235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Move kvm_io_bus_get_dev() locking responsibilities to callers\n\nkvm_io_bus_get_dev() returns a device that is only matched by the\naddress, and nothing else. This can cause a lifetime issue if\nthe matched device is not the expected type, as by the time\nthe caller can introspect the object, it might be gone (the srcu\nlock having been dropped).\n\nGiven that there is only a single user of this helper, the simplest\noption is to move the locking responsibility to the caller, which\ncan keep the srcu lock held for as long as it wants.\n\nNote that this aligns with other kvm_io_bus*() helpers, which\nalready require the srcu lock to be held by the callers.(CVE-2026-72282)\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix overflow in passthrough ioctl bounds check. smb2_ioctl_query_info() validates the PASSTHRU_FSCTL response payload before copying it to userspace. The payload offset and length both come from 32-bit fields. The bounds check currently adds OutputOffset and qi.input_buffer_length directly, so the addition can wrap in 32-bit arithmetic before the result is compared against the response buffer length. A malicious server can use a large OutputOffset and a small OutputCount to make the wrapped sum pass the bounds check. The later copy_to_user() then reads from io_rsp + OutputOffset, outside the response buffer, leading to an out-of-bounds read.(CVE-2026-72310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm era: fix NULL pointer dereference in metadata_open()\n\nmetadata_open() returns NULL when kzalloc_obj() fails, but the\ncaller era_ctr() only checks IS_ERR(md).  Since IS_ERR(NULL)\nreturns false, the NULL pointer is treated as a valid result\nand later assigned to era-\u0026gt;md, leading to a NULL pointer\ndereference when the metadata is accessed.\n\nFix this by returning ERR_PTR(-ENOMEM) on allocation failure,\nconsistent with dm-cache-metadata.c, dm-thin-metadata.c, and\ndm-clone-metadata.c which all use ERR_PTR(-ENOMEM) for the\nsame pattern.(CVE-2026-72316)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: pin upper rpc_clnt across the TLS connect_worker\n\nThe TLS connect path has a use-after-free: nothing pins the\nupper rpc_clnt across the delayed connect_worker. xs_connect()\nstores task-\u0026gt;tk_client in sock_xprt::clnt as a raw pointer\nand queues the worker; for TLS-secured transports that worker\nis xs_tcp_tls_setup_socket(), which reads several fields out\nof the saved pointer (cl_timeout, cl_program, cl_prog,\ncl_vers, cl_cred, cl_stats) to construct the args for the\ninner handshake rpc_clnt.\n\nThe xprt does not reference the rpc_clnt; the rpc_clnt\nreferences the xprt. xs_destroy() does cancel the\nconnect_worker, but it runs only when the xprt\u0026apos;s refcount\ndrops to zero, which cannot happen until the rpc_clnt\nreleases its cl_xprt reference in rpc_free_client_work().\nWhen a TLS handshake fails fatally (for example, an mTLS\nmount whose client cert does not match the server), the\nconnecting task is woken with -EACCES and exits, the mount\ncaller invokes rpc_shutdown_client(), and the upper rpc_clnt\nis freed before the queued connect_worker fires.\nxs_tcp_tls_setup_socket() then dereferences the freed clnt,\nproducing the refcount_t underflow Michael Nemanov reported.\n\nTake a reference on the upper rpc_clnt in xs_connect() for\nTLS transports via a new rpc_hold_client() helper, and drop\nit in the connect_worker\u0026apos;s exit path with rpc_release_client().\nThe xprt_lock_connect() / xprt_unlock_connect() pairing\nalready serialises xs_connect() with xs_tcp_tls_setup_socket(),\nso the take and release are balanced one-for-one.\n\nThe non-TLS connect worker (xs_tcp_setup_socket) never reads\nsock_xprt::clnt, so leave that path alone and avoid the\nclnt-holds-xprt-holds-clnt cycle that would otherwise prevent\nxprt destruction.(CVE-2026-72317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: validate DFS referral string offsets\n\nparse_dfs_referrals() validates that the response header and referral\narray fit in the received buffer, but each referral also contains string\noffsets supplied by the server.\n\nThose offsets are used to compute the DfsPath and NetworkAddress string\npointers without checking whether they still point inside the response\nbuffer. A malformed referral can therefore make the computed pointer\nexceed the end of the buffer. The resulting negative max_len is then\npassed to cifs_strndup_from_utf16(), and the non-Unicode path forwards it\nto kstrndup() as a size_t, allowing strnlen() to read out of bounds.\n\nValidate each string offset before deriving the string pointer.(CVE-2026-72318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: ensure inner headers in ICMP errors are in headroom\n\nSashiko points out that after stripping the outer headers\nwith pskb_pull() we should ensure the inner IP headers\nin ICMP errors from tunnels are present in the skb headroom\nfor functions like ipv4_update_pmtu(), icmp_send() and\nIP_VS_DBG().\n\nAlso, add more checks for the length of the inner headers.(CVE-2026-72319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: Consume empty data records in tls_sw_read_sock()\n\nA peer may send a zero-length TLS application_data record; TLS 1.3\nexplicitly permits these as a traffic-analysis countermeasure (RFC\n8446, Section 5.1). After decryption such a record has full_len ==\n0. tls_sw_read_sock() hands it to the read_actor, which has no\npayload to consume and returns zero. The loop treats a zero return\nas backpressure (used \u0026lt;= 0), requeues the skb at the head of\nrx_list, and stops. rx_list is serviced head-first on the next\ncall, so the empty record is dequeued, fails the same way, and is\nrequeued again; every later record on the connection is blocked\nbehind it.\n\ntls_sw_recvmsg() does not stall on this: a zero-length data record\ncopies nothing and falls through to consume_skb(). Mirror that in\nthe read_sock() path by recognizing an empty data record before\nthe actor runs, consuming it, and continuing.(CVE-2026-72330)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nqede: fix off-by-one in BD ring consumption on build_skb failure\n\nqede_rx_build_skb() and qede_tpa_rx_build_skb() do not check for a\nNULL return from qede_build_skb(). When it returns NULL under memory\npressure, the functions still consume a BD from the ring before\nreturning NULL. The callers then recycle additional BDs, resulting in\none extra BD being consumed (off-by-one). This desynchronizes the BD\nring, which can corrupt DMA page reference counts and lead to SLUB\nfreelist corruption.\n\nCommit 4e910dbe3650 (\u0026quot;qede: confirm skb is allocated before using\u0026quot;)\nadded a NULL check inside qede_build_skb() to prevent a NULL pointer\ndereference, but did not address the missing NULL checks in the\ncallers, making this off-by-one reachable.\n\nFix this by adding NULL checks for the return value of\nqede_build_skb() in both qede_rx_build_skb() and\nqede_tpa_rx_build_skb(), returning NULL immediately before any BD ring\nmanipulation.(CVE-2026-72339)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix HV VHCA stats agent registration race\n\nmlx5e_hv_vhca_stats_create() registers the stats agent through\nmlx5_hv_vhca_agent_create(). The helper publishes the agent in\nhv_vhca-\u0026gt;agents[type] under agents_lock and immediately schedules an\nasynchronous control invalidation on the HV VHCA workqueue before\nreturning to mlx5e.\n\nThe asynchronous invalidation invokes the control agent\u0026apos;s invalidate\ncallback, which reads the hypervisor control block and forwards the\ncommand to mlx5e_hv_vhca_stats_control(). That callback may either:\n\n  - call cancel_delayed_work_sync(\u0026amp;priv-\u0026gt;stats_agent.work), or\n  - call queue_delayed_work(priv-\u0026gt;wq, \u0026amp;sagent-\u0026gt;work, sagent-\u0026gt;delay).\n\nHowever, the delayed_work and priv-\u0026gt;stats_agent.agent are only\ninitialized after mlx5_hv_vhca_agent_create() returns to mlx5e:\n\n    agent = mlx5_hv_vhca_agent_create(...);   /* publish + invalidate */\n    ...\n    priv-\u0026gt;stats_agent.agent = agent;          /* too late */\n    INIT_DELAYED_WORK(\u0026amp;priv-\u0026gt;stats_agent.work, ...); /* too late */\n\nIf the asynchronous control path runs before the two assignments\nabove, it can:\n\n  - Operate on an uninitialized delayed_work whose timer.function is\n    NULL. queue_delayed_work() calls add_timer() unconditionally, so\n    when the timer expires the timer softirq invokes a NULL function\n    pointer.\n  - Re-initialize the timer later through INIT_DELAYED_WORK() while\n    the timer is already enqueued in the timer wheel, corrupting the\n    hlist (entry.pprev cleared while the previous bucket node still\n    points at this entry).\n  - When the worker eventually runs, mlx5e_hv_vhca_stats_work() reads\n    sagent-\u0026gt;agent (NULL) and dereferences it inside\n    mlx5_hv_vhca_agent_write().\n\nFix this by:\n\n  - Initializing priv-\u0026gt;stats_agent.work before invoking\n    mlx5_hv_vhca_agent_create(), so the work is always in a valid\n    state when the control callback observes it.\n  - Adding a struct mlx5_hv_vhca_agent **ctx_update out-parameter\n    to mlx5_hv_vhca_agent_create(). The helper writes the agent\n    pointer to *ctx_update before publishing into hv_vhca-\u0026gt;agents[]\n    and triggering the agents_update flow, so any callback\n    subsequently invoked from that flow already sees a valid\n    priv-\u0026gt;stats_agent.agent. This avoids having the control\n    callback participate in agent initialization.\n\nWhile at it, access priv-\u0026gt;stats_agent.agent with\nREAD_ONCE()/WRITE_ONCE() for the cross-CPU access with the worker, and\nclear priv-\u0026gt;stats_agent.buf on the agent_create() failure path.(CVE-2026-72342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nseg6: validate SRH length before reading fixed fields\n\nseg6_validate_srh() reads fixed SRH fields such as srh-\u0026gt;type and\nsrh-\u0026gt;hdrlen before checking that the supplied length covers the fixed\nstruct ipv6_sr_hdr fields.\n\nThe BPF SEG6 encap path reaches this with a BPF program-supplied pointer\nand length: bpf_lwt_push_encap() and the SEG6 local BPF END_B6 and\nEND_B6_ENCAP actions call bpf_push_seg6_encap(), which forwards the\nlength to seg6_validate_srh() with no minimum-size guard.  A 2-byte SEG6\nencap header can therefore make the validator read srh-\u0026gt;type at offset 2\nbeyond the caller-supplied buffer.\n\nReject lengths shorter than the fixed SRH at the top of\nseg6_validate_srh(), before any field is read.  This fixes the BPF helper\npath and keeps the common validator robust.(CVE-2026-72400)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs()\n\nResetting all VFs causes resource leak on VFs with FDIR filters\nenabled as CTRL VSIs are only invalidated and not freed. Fix by using\nice_vf_ctrl_vsi_release() instead of ice_vf_ctrl_invalidate_vsi() which\naligns behavior with the ice_reset_vf() function.\n\nReproduction:\n  echo 1 \u0026gt; /sys/class/net/$pf/device/sriov_numvfs\n  ethtool -N $vf flow-type ether proto 0x9000 action 0\n  echo 1 \u0026gt; /sys/class/net/$pf/device/reset(CVE-2026-72425)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: validate selector family and prefixlen during match\n\nsyzbot reported a shift-out-of-bounds in xfrm_selector_match()\ndue to AF_UNSPEC selector with large prefixlen (e.g. 128) matched\nagainst IPv4 flow (when XFRM_STATE_AF_UNSPEC is set).\n\nFix this by:\n\n- Rejecting mismatched families in xfrm_selector_match.\n- Returning false in addr4_match if prefixlen \u0026gt; 32.\n- Returning false in addr_match if prefixlen \u0026gt; 128 (prevents overflow).(CVE-2026-72450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: aa_label_alloc use aa_label_free on alloc failure\n\naa_label_alloc() allocates a secid before allocating or taking the label\nproxy. If the later proxy step fails, the error path only freed the label\nmemory, leaking any resources initialized by aa_label_init().\n\nUse aa_label_free() on the failure path so partially initialized labels\nrelease their secid and other label resources before the backing memory is\nfreed.(CVE-2026-72459)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: check label build before no_new_privs test\n\naa_change_profile() builds a replacement label with\nfn_label_build_in_scope() before the no_new_privs subset check. The build\nhelper can fail and return NULL or an ERR_PTR, but the result was passed\nto aa_label_is_unconfined_subset() before the existing IS_ERR_OR_NULL()\ncheck.\n\nReuse the existing target-label build failure handling immediately after\nthe build. This preserves the current audit handling while preventing the\nsubset helper from dereferencing an invalid label.(CVE-2026-72460)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Repost Receive buffers for malformed replies\n\nrpcrdma_wc_receive() decrements the transport\u0026apos;s Receive count for\nevery completion before it dispatches a successful Receive to\nrpcrdma_reply_handler(). The handler must post a replacement\nReceive WR before returning unless ownership of the rep has moved\nelsewhere, as on the backchannel path.\n\nCommit 2ae50ad68cd7 (\u0026quot;xprtrdma: Close window between waking RPC\nsenders and posting Receives\u0026quot;) moved the Receive refill out of\nrpcrdma_wc_receive(), where it had run ahead of every reply, into\nrpcrdma_reply_handler() so that the responder\u0026apos;s credit grant could\nbe parsed before reposting. The bad-version and short-reply exits\nnever reach that refill: they recycle the rep and return without\ncalling rpcrdma_post_recvs().\n\nA remote peer can therefore drain the client\u0026apos;s posted Receive\nqueue by sending a sustained stream of replies that are shorter\nthan the fixed transport header or that carry an unrecognized\nRPC/RDMA version. Each such reply consumes one posted Receive\nwithout replacing it. Once the queue empties, the peer\u0026apos;s next\nSend finds no posted Receive and the transport stalls until\nreconnect.\n\nRoute both malformed-reply exits through the shared repost tail\nafter recycling the rep, refilling against buf-\u0026gt;rb_credits, the\nmost recent accepted credit grant. Neither exit updates the\ncongestion window, so RPCs admitted under the previous grant\nremain in flight awaiting replies. A smaller refill target would\nlet a stream of malformed replies ratchet the posted Receive count\ndown to the batch floor while the congestion window still admits\nrb_credits RPCs; a burst of valid replies to those RPCs could then\noverrun the posted Receives, and because the client connects with\nrnr_retry_count of zero, a single RNR NAK terminates the\nconnection. Refilling against rb_credits also restores the target\nthat applied to malformed replies before commit 2ae50ad68cd7\n(\u0026quot;xprtrdma: Close window between waking RPC senders and posting\nReceives\u0026quot;) when rpcrdma_post_recvs() computed it from rb_credits\ninternally. rb_credits is at least one from connection\nestablishment onward, so the repost path always keeps Receives\nposted.(CVE-2026-72464)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Sanitize the reply credit grant after parsing\n\nThe out_norqst exit in rpcrdma_reply_handler() branches away before\nthe credit clamp, so a reply that matches no pending request reaches\nout_post carrying the raw credit value parsed from the wire.\nrpcrdma_post_recvs() does not bound its @needed argument: the refill\nloop allocates and chains Receive WRs until the count is satisfied or\nallocation fails. A peer that sends a well-formed reply carrying an\nunknown XID and an inflated credit grant therefore drives rep\nallocation and Receive posting past re_max_requests on every such\nreply.\n\nMove the clamp to immediately after the credit field is parsed,\nahead of the first branch that can reach out_post, so every later\nconsumer sees a sanitized value. The cwnd update stays on the\nmatched-request path.(CVE-2026-72465)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Fix bcall rep leak and unbounded peek\n\nrpcrdma_is_bcall() decodes a reply\u0026apos;s first words to decide whether\nthe frame is a backchannel call. Two issues in that decode path\nlet a short or malformed reply leak the receive buffer and drain\nthe Receive queue.\n\nFirst, the speculative peek\n\n    p = xdr_inline_decode(xdr, 0);\n    /* five p++ reads follow */\n\nasks xdr_inline_decode() for zero bytes, which returns xdr-\u0026gt;p\nwithout consulting xdr-\u0026gt;end. The five subsequent __be32 reads can\nthen walk up to 20 bytes past the wire payload into stale regbuf\ncontents and misclassify the reply as a backchannel call.\n\nSecond, after the post-peek\n\n    p = xdr_inline_decode(xdr, 3 * sizeof(*p));\n    if (unlikely(!p))\n            return true;\n\nthe short-header arm returns true without calling\nrpcrdma_bc_receive_call(). The contract with the caller is that a\ntrue return transfers ownership of rep to the backchannel path:\n\n    rpcrdma_reply_handler()\n      if (rpcrdma_is_bcall(r_xprt, rep))\n              return;        /* bare return, skips out_post */\n      ...\n    out_post:\n      rpcrdma_post_recvs(r_xprt, credits + ...);\n\nBecause rpcrdma_bc_receive_call() never ran, no one took rep, but\nrpcrdma_reply_handler still bare-returns past rpcrdma_rep_put()\nand rpcrdma_post_recvs(). The rep, with its persistently\nDMA-mapped receive buffer, is orphaned on rb_all_reps and freed\nonly at transport teardown. This completion reposts nothing, so\nits slot is reclaimed only when a later forward-channel reply\nreaches out_post and rpcrdma_post_recvs() allocates a fresh rep to\nbackfill; absent that traffic the Receive queue drains and the\npeer\u0026apos;s Sends draw RNR NAKs.\n\nFix by consulting xdr-\u0026gt;end after the zero-length peek so the five\n__be32 reads cannot run unless 20 bytes of wire payload remain. A\nbyte-precise comparison against xdr-\u0026gt;end is required because a\nnon-4-aligned receive rounds the stream\u0026apos;s word count up past the\ntrue payload. Also return false from the short-header arm so the\nreply falls through the normal out_norqst cleanup chain\n(rpcrdma_rep_put() plus rpcrdma_post_recvs()).(CVE-2026-72466)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Decouple req recycling from RPC completion\n\nrl_kref formerly served two distinct lifetimes through a single\nrefcount: it gated when a Reply could wake its RPC task, and it\ngated when an rpcrdma_req could return to its free pool. The\nmarshal path took the Send-side reference only when SGEs needed\nDMA-unmap (sc_unmap_count \u0026gt; 0), which made a Send carrying only\npre-registered buffers an exception: the Reply handler dropped\nrl_kref from 1 to 0 and freed the req while the HCA might still\nbe DMA-reading from its send buffer.\n\nGive rl_kref a narrower job. The RPC layer takes one reference\nwhen slot allocation hands a req out. rpcrdma_prepare_send_sges()\ntakes a Send-side reference unconditionally after WR preparation\nsucceeds. xprt_rdma_free_slot() and xprt_rdma_bc_free_rqst() drop\nthe RPC-layer reference; rpcrdma_sendctx_unmap() drops the\nSend-side reference. The req returns to its free pool only after\nboth owners have signed off.\n\nThe existing kref_init(\u0026amp;req-\u0026gt;rl_kref) call in\nrpcrdma_prepare_send_sges() is removed. Initialization moves to\nthe slot-allocation paths (xprt_rdma_alloc_slot and\nrpcrdma_bc_rqst_get), and the release callback re-arms rl_kref\nbefore the req returns to a free pool. A re-init in the marshal\npath would discard the RPC-layer reference that already exists\non entry.\n\nThree invariants follow:\n\n  - Any rpcrdma_req held by an rpc_rqst has rl_kref \u0026gt;= 1.\n    xprt_rdma_alloc_slot(), rpcrdma_bc_rqst_get(), and the\n    backlog-wake branch in xprt_rdma_alloc_slot() each kref_init\n    rl_kref before publishing the req. Without this invariant,\n    an RPC task that aborts between slot allocation and marshal\n    (gss_refresh failure or signal during call_connect, for\n    example) would drive xprt_release() -\u0026gt;\n    xprt_rdma_free_slot() -\u0026gt; kref_put against a refcount of\n    zero, saturating refcount_t and stranding the slot.\n\n  - The Send-side reference is taken only after WR prep\n    succeeds. A mapping failure in rpcrdma_prepare_send_sges()\n    runs rpcrdma_sendctx_cancel(), which DMA-unmaps the sendctx\n    and clears sc_req without touching rl_kref. The sendctx\n    ring walks in rpcrdma_sendctx_put_locked() and\n    rpcrdma_sendctxs_destroy() skip entries with sc_req == NULL,\n    so a burst of -EIO marshal failures cannot hold reqs off\n    rb_send_bufs.\n\n  - The release callback re-arms rl_kref so the next consumer\n    enters with the invariant satisfied.\n\nReplies now complete the RPC directly. rpcrdma_reply_handler()\ncalls rpcrdma_complete_rqst() in place of kref_put on the\nnon-LocalInv branch. The LocalInv branch already completes the\nRPC from frwr_unmap_async() and is unaffected.\n\nBecause Send-side references can now outlive RPC completion,\nconnection teardown drains sendctx entries whose unsignaled\nSends never had a later signaled completion to walk the ring.\nrpcrdma_sendctxs_destroy() walks the active range and runs\nrpcrdma_sendctx_unmap() on each entry with a non-NULL sc_req\nbefore the request buffers are reset, and is moved ahead of\nrpcrdma_reqs_reset() in rpcrdma_xprt_disconnect() so the reqs\nare still in their pre-reset state when the Send-side refs are\nreleased.\n\nThe drain creates a teardown-ordering hazard on the backchannel\npath. With the new lifetime, releasing a bc_prealloc req from\nrpcrdma_req_release() re-adds it to bc_pa_list. The disconnect\nin xprt_rdma_destroy() runs after xprt_destroy_backchannel() has\nalready emptied bc_pa_list, so the drained reqs would otherwise\nleak. xprt_rdma_destroy() now runs xprt_rdma_bc_destroy(xprt, 0)\na second time after the disconnect to reclaim them.(CVE-2026-72473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: add bounds check to run_get_highest_vcn()\n\nrun_get_highest_vcn() parses a packed NTFS mapping-pairs buffer without\nany length bound, relying solely on a 0x00 terminator to stop.  A\ncrafted $LogFile UpdateMappingPairs record whose embedded attribute\ncontains mapping-pairs runs without a terminator causes the function to\nread past the slab allocation, triggering a KASAN slab-out-of-bounds\nread on mount.\n\nThe sibling function run_unpack() received an analogous bounds-check in\ncommit b62567bca474 (\u0026quot;ntfs3: add buffer boundary checks to run_unpack()\u0026quot;),\nbut run_get_highest_vcn() was missed.\n\nTake a run_buf_size parameter and reject any run header whose payload\nwould extend past the buffer end, mirroring the pattern used by\nrun_unpack().  The caller in fslog.c passes the remaining attribute\nbytes after the mapping-pairs offset.\n\nKASAN report (on mainline v7.1 merge window HEAD):\n\n  BUG: KASAN: slab-out-of-bounds in run_get_highest_vcn+0x3c0/0x410\n  Read of size 1 at addr ffff88800e2d5400 by task mount/72\n  Call Trace:\n   run_get_highest_vcn+0x3c0/0x410\n   do_action.isra.0+0x3ba8/0x7b50\n   log_replay+0x9ddd/0x10200\n   ntfs_loadlog_and_replay+0x4ad/0x610\n   ntfs_fill_super+0x214a/0x4540(CVE-2026-72478)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Guard __get_user acesss with access_ok for uprobe_multi data\n\nAs reported by sashiko [1] we need to use access_ok to check the user\nspace data bounds before we use __get-user to get it.\n\n[1] https://lore.kernel.org/bpf/(CVE-2026-74258)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: core: fix supplied_from allocations\n\nIf dts property power-supplies has multiple values, then accessing to\npsy-\u0026gt;supplied_from[i-1] in __power_supply_populate_supplied_from will\noverrun supplied_from array.(CVE-2026-74271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: require net admin for TIPCv2 netlink mutators\n\nTIPCv2 registers mutating generic-netlink operations without admin\npermission flags. Generic netlink only checks CAP_NET_ADMIN when an\noperation sets GENL_ADMIN_PERM or GENL_UNS_ADMIN_PERM, so a local\nunprivileged process can currently change TIPC state through commands\nsuch as TIPC_NL_NET_SET, TIPC_NL_KEY_SET, TIPC_NL_KEY_FLUSH, and\nbearer enable/disable.\n\nThe legacy TIPC netlink API already checks netlink_net_capable(...,\nCAP_NET_ADMIN) for administrative commands. Give the TIPCv2 mutators\nthe equivalent generic-netlink gate. Use GENL_UNS_ADMIN_PERM, which\nmaps to the same namespace-aware CAP_NET_ADMIN check that\nnetlink_net_capable() performs, so the behaviour matches the legacy\npath and keeps working for CAP_NET_ADMIN holders in a non-initial user\nnamespace (containers).\n\nA QEMU/KASAN repro run as uid/gid 65534 with zero effective\ncapabilities previously succeeded in changing the network id and node\nidentity, setting and flushing key material, and enabling/disabling a\nUDP bearer. With this patch applied the same operations fail with\n-EPERM.(CVE-2026-74283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: validate embedded address parameter length\n\nsctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP,\nand SET_PRIMARY parameters against a fixed minimum size of sizeof(struct\nsctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer\nparameter is large enough to contain an embedded address parameter header,\nbut does not verify that the embedded address parameter\u0026apos;s declared length\nfits within the bounds of the outer parameter.\n\nLater, sctp_process_param() and sctp_process_asconf_param() extract the\nembedded address parameter and pass it to af-\u0026gt;from_addr_param(), which uses\nthe address parameter length to parse the variable-length address payload.\nA malformed peer can therefore advertise an embedded address parameter\nlength that exceeds the remaining bytes in the enclosing parameter.\n\nValidate that addr_param-\u0026gt;p.length does not exceed the space available\nafter the sctp_addip_param header before processing the embedded address\nparameter. Reject malformed parameters when the embedded address length\nextends beyond the enclosing parameter bounds.\n\nThis prevents out-of-bounds reads when parsing malformed parameters carried\nin INIT or ASCONF processing paths.(CVE-2026-74287)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Tighten cgroup storage cookie checks for prog arrays\n\nThe fix in commit abad3d0bad72 (\u0026quot;bpf: Fix oob access in cgroup local\nstorage\u0026quot;) is still incomplete. The prog-array compatibility check\ntreats a program with no cgroup storage as compatible with any stored\nstorage cookie. This allows a storage-less program to bridge a tail\ncall chain between an entry program and a storage-using callee even\nthough cgroup local storage at runtime still follows the caller\u0026apos;s\ncontext, that is, A -\u0026gt; B(no storage) -\u0026gt; C(storage) path.\n\nRequiring exact cookie equality would break the legitimate case of a\nstorage-less leaf program being tail called from a storage-using one.\nInstead, only accept a zero storage cookie if the program cannot\nperform tail calls itself. This keeps A -\u0026gt; B(no storage) working\nwhile rejecting the A -\u0026gt; B(no storage) -\u0026gt; C(storage) bridge.(CVE-2026-74305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject sleepable BPF_LSM_CGROUP programs at load time\n\nThe cgroup shim runs under rcu_read_lock_dont_migrate(), so we should\nnot attach any sleepable BPF programs there. Add support to the verifier\nto explicitly reject attempts to load sleepable BPF programs destined\nfor LSM cgroup attachment.\n\nWithout this, we get the following splat from a BPF_LSM_CGROUP\nprogram marked BPF_F_SLEEPABLE attached to file_open when it calls\nbpf_get_dentry_xattr():\n\n  BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1567\n  in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 34317, name: load\n  preempt_count: 0, expected: 0\n  RCU nest depth: 2, expected: 0\n  Call Trace:\n   down_read+0x76/0x480\n   ext4_xattr_get+0x11f/0x700\n   __vfs_getxattr+0xf0/0x150\n   bpf_get_dentry_xattr+0xbb/0xf0\n   bpf_prog_e76a298dac9218c6_test_open+0x6a/0x85\n   __cgroup_bpf_run_lsm_current+0x326/0x840\n   bpf_trampoline_6442534646+0x62/0x14d\n   security_file_open+0x34/0x60\n   do_dentry_open+0x340/0x1260\n   vfs_open+0x7a/0x440\n   path_openat+0x1bac/0x30a0\n\nlibbpf provides a .s named section variant for every sleepable\nprogram type except lsm_cgroup, reflecting that per-cgroup LSM programs\nare intended to only run in a non-sleepable context.\n\nThe above splat was obtained by bypassing libbpf by using bpf(2)\ndirectly.(CVE-2026-74338)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Clear rb node linkage when freeing bpf_rb_root\n\nbpf_rb_root_free() detaches the root by copying the current rb_root_cached\nand then replacing the live root with RB_ROOT_CACHED. It then walks the\ncopied root and drops each object contained in the tree.\n\nThis leaves the rb node state intact while dropping the object. If the\nobject is refcounted and survives the drop, its bpf_rb_node_kern still\ncontains an owner pointer to the freed root and stale rb tree linkage. If\na later bpf_rb_root allocation reuses the same address, bpf_rbtree_remove()\ncan incorrectly pass the owner check and call rb_erase_cached() on a node\nwhose rb pointers belong to the old tree.\n\nMirror the list draining behavior by marking nodes as busy while the root\nis being detached, then clear the rb node and release the owner before\ndropping the containing object. This makes surviving nodes unowned and\nsafe to reject from remove or accept for a later add.(CVE-2026-74344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: fix UAF by restoring RCU-delayed inode freeing in bpffs\n\ncommit 4f375ade6aa9 (\u0026quot;bpf: Avoid RCU context warning when unpinning\nhtab with internal structs\u0026quot;) moved inode cleanup from -\u0026gt;free_inode()\ninto -\u0026gt;destroy_inode() to avoid sleeping in RCU context when calling\nbpf_any_put(). However this removed the RCU delay on freeing the\ninode itself and the cached symlink body (i_link), both of which\ncan be accessed by RCU pathwalk (pick_link, may_lookup etc.).\n\nThis causes a use-after-free when a concurrent unlinkat() drops the\nlast inode reference and destroy_inode() frees the inode immediately,\nwhile another task is still walking the path in RCU mode and reads\ninode-\u0026gt;i_opflags (offset +2) inside current_time() -\u0026gt; is_mgtime().\n\nKASAN reports:\n  BUG: KASAN: slab-use-after-free in is_mgtime include/linux/fs.h:2313\n  Read of size 2 at addr ffff8880407e4282 (offset +2 = i_opflags)\n\nThe rules (per Al Viro):\n  -\u0026gt;destroy_inode()  called immediately, can sleep, use for blocking\n                     cleanup e.g. bpf_any_put()\n  -\u0026gt;free_inode()     called after RCU grace period, use for freeing\n                     inode and anything RCU-accessible e.g. i_link\n\nFix: split the two concerns properly:\n  - keep bpf_any_put() in bpf_destroy_inode() since it is blocking\n    and needs to run promptly\n  - introduce bpf_free_inode() to handle kfree(i_link) and\n    free_inode_nonrcu() with proper RCU delay, preventing the UAF(CVE-2026-74363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Copy WQE to local buffer in non-SRQ receive path\n\nFor non-SRQ QPs, the responder reads WQE fields directly from the\nshared queue buffer mapped into userspace. This allows a malicious\nuser to modify fields like num_sge or sge entries while the kernel\nis processing the WQE, leading to out-of-bounds reads in\nrxe_resp_check_length() and copy_data().\n\nIntroduce get_recv_wqe() that validates num_sge and copies the WQE\nto a kernel-local buffer before processing, matching the approach\nalready used for SRQ WQEs in get_srq_wqe(). The srq_wqe buffer is\nreused since SRQ and non-SRQ paths are mutually exclusive per QP.(CVE-2026-74377)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe\n\nget_srq_wqe() reads wqe-\u0026gt;dma.num_sge from the shared receive queue\nbuffer, which is mapped into userspace. It validates num_sge against\nmax_sge, but then re-reads the same field to calculate the memcpy\nsize. A concurrent userspace thread can modify num_sge between\nvalidation and use, causing a heap buffer overflow when copying the\nWQE into qp-\u0026gt;resp.srq_wqe.\n\nRead num_sge into a local variable and use it for both the bounds\ncheck and the size calculation.(CVE-2026-74378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/srpt: fix integer overflow in immediate data length check\n\nimm_buf-\u0026gt;len is a user-controlled uint32_t received from the network.\nAdding it to imm_data_offset without overflow checking allows a\nmalicious initiator to send len=0xFFFFFFFF, causing req_size to wrap\naround to a small value, bypassing the bounds check, and subsequently\npassing a ~4GB length to sg_init_one().\n\nUse check_add_overflow() to detect wrapping before the comparison.(CVE-2026-74394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier\n\nmlx5_ib_alloc_transport_domain() allocates a transport domain and then\nmay fail in mlx5_ib_enable_lb(). In that case, the allocated TD is leaked.\n\nFix this by deallocating the TD when mlx5_ib_enable_lb() returns an\nerror. Also return 0 explicitly in the no-loopback-capability success\nbranch, and move dev-\u0026gt;lb.mutex initialization to mlx5_ib_stage_init_init().(CVE-2026-74397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD\n\naddrconf_dad_failure() transitions ifp-\u0026gt;state from DAD to POSTDAD\nvia addrconf_dad_end(), which drops ifp-\u0026gt;lock on return.  The lock\nis re-acquired after net_info_ratelimited().  A concurrent\nipv6_del_addr() can take the lock in that window, set ifp-\u0026gt;state\nto DEAD and run list_del_rcu(\u0026amp;ifp-\u0026gt;if_list).\n\naddrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad:\nand schedules a new dad_work.  The work calls ipv6_del_addr()\nagain, hitting the already-poisoned list entry:\n\n  general protection fault: 0000 [#1] SMP NOPTI\n  CPU: 4 PID: 217 Comm: kworker/4:1\n  Workqueue: ipv6_addrconf addrconf_dad_work\n  RIP: 0010:ipv6_del_addr+0xe9/0x280\n  RAX: dead000000000122\n  Call Trace:\n   addrconf_dad_stop+0x113/0x140\n   addrconf_dad_work+0x28c/0x430\n   process_one_work+0x1eb/0x3b0\n   worker_thread+0x4d/0x400\n   kthread+0x104/0x140\n   ret_from_fork+0x35/0x40\n\nFold the addrconf_dad_end() logic into addrconf_dad_failure() under\na single ifp-\u0026gt;lock critical section.  The STABLE_PRIVACY branch\ntemporarily drops ifp-\u0026gt;lock around address regeneration, so at\nlock_errdad: verify the state is still POSTDAD before transitioning\nto ERRDAD; bail out otherwise to avoid overwriting a state set by\nanother path while the lock was released.(CVE-2026-74398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().\n\nudp_tunnel_sock_release() could set sk-\u0026gt;sk_user_data to NULL\nwhile vxlan_gro_prepare_receive() is running.\n\nLet\u0026apos;s check if rcu_dereference_sk_user_data() is NULL after\nskb_gro_remcsum_init().(CVE-2026-74406)","status":"published","published":"2026-09-05T15:04:08Z","modified":"2026-09-05T15:16:48.225761008Z","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:47.217107Z"},{"id":"UBUNTU-CVE-2026-23317","description":"In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions Before the referenced fixes these functions used a lookup function that returned a pointer. This was changed to another lookup function that returned an error code with the pointer becoming an out parameter. The error path when the lookup failed was not changed to reflect this change and the code continued to return the PTR_ERR of the now uninitialized pointer. This could cause the vmw_translate_ptr functions to return success when they actually failed causing further uninitialized and OOB accesses.","status":"published","published":"2026-03-25T11:16:00Z","modified":"2026-11-06T13:52:08.815388849Z","cvss":[{"version":"4.0","score":7.3,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-06T14:24:04.853401Z"},{"id":"AZL-80714","title":"CVE-2026-23317 affecting package kernel for versions less than 6.6.130.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.","status":"published","published":"2026-03-25T11:16:28Z","modified":"2026-08-28T17:56:56.424117Z","updated_at":"2026-11-02T15:28:10.017343Z"},{"id":"CLSA-2026-1786352940","title":"kernel: Fix of 148 CVEs","description":"- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level {CVE-2026-63807}\n- KVM: x86: Check for invalid/obsolete root *after* making MMU pages available {CVE-2026-64561}\n- ubi: Fix use-after-free when volume resizing failed {CVE-2023-53271}\n- ice: Check VF VSI Pointer Value in ice_vc_add_fdir_fltr() {CVE-2025-37912}\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() {CVE-2026-53318}\n- dpll: Prevent duplicate registrations {CVE-2026-23129}\n- pinmux: fix race causing mux_owner NULL with active mux_usecount {CVE-2025-38632}\n- HID: apple: validate feature-report field count to prevent NULL pointer dereference {CVE-2025-38557}\n- thunderbolt: Limit XDomain response copy to actual frame size {CVE-2026-53146}\n- net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery {CVE-2026-43466}\n- virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false {CVE-2026-31469}\n- scsi: target: Reset t_task_cdb pointer in error case {CVE-2025-68782}\n- ubi: ubi_create_volume: Fix use-after-free when volume creation failed {CVE-2022-49388}\n- drm/xe/reg_sr: Fix leak on xa_store failure {CVE-2026-23418}\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets {CVE-2026-43459}\n- md/raid10: wait barrier before returning discard request with REQ_NOWAIT {CVE-2025-40325}\n- nbd: defer config put in recv_work {CVE-2025-68372}\n- nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference {CVE-2026-23148}\n- net: hns3: using the num_tqps in the vf driver to apply for resources {CVE-2025-71064}\n- net/mlx5e: Disable MACsec offload for uplink representor profile {CVE-2025-38020}\n- serial: imx: fix tx statemachine deadlock {CVE-2023-52456}\n- dm-thin: fix metadata refcount underflow {CVE-2026-46107}\n- net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure {CVE-2026-53229}\n- drm/amdgpu: Fix use-after-free race in VM acquire {CVE-2026-43370}\n- usbnet:fix NPE during rx_complete {CVE-2025-22050}\n- platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it {CVE-2025-21645}\n- driver core: class: Fix wild pointer dereferences in API class_dev_iter_next() {CVE-2025-21810}\n- usb: atm: cxacru: fix a flaw in existing endpoint checks {CVE-2025-21916}\n- ALSA: seq: dummy: fix UMP event stack overread {CVE-2026-53241}\n- pmdomain: imx8mp-blk-ctrl: Keep the NOC_HDCP clock enabled {CVE-2026-31655}\n- net/mlx5: Bridge, fix the crash caused by LAG state check {CVE-2025-21970}\n- ALSA: timer: Don't take register_mutex with copy_from/to_user() {CVE-2025-23134}\n- md/raid5: validate payload size before accessing journal metadata {CVE-2026-46070}\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op {CVE-2025-40171}\n- iommu: Fix potential memory leak in iopf_queue_remove_device() {CVE-2025-21770}\n- Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak {CVE-2025-40035}\n- scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails {CVE-2026-45997}\n- can: dev: can_set_termination(): allow sleeping GPIOs {CVE-2024-56625}\n- nvme-tcp: fix the memleak while create new ctrl failed {CVE-2024-56632}\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() {CVE-2026-46146}\n- pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains {CVE-2026-23187}\n- wifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path {CVE-2025-22128}\n- octeon_ep: Fix memory leak in octep_device_setup() {CVE-2026-23160}\n- pinctrl: check the return value of pinmux_ops::get_function_name() {CVE-2025-40030}\n- net: tun: fix tun_napi_alloc_frags() {CVE-2024-56372}\n- wifi: iwlwifi: mvm: clean up ROC on failure {CVE-2025-21906}\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd {CVE-2025-40275}\n- dpll: fix xa_alloc_cyclic() error handling {CVE-2025-22016}\n- usb: usbtmc: Flush anchored URBs in usbtmc_release {CVE-2026-31758}\n- RDMA/siw: Fix potential NULL pointer dereference in header processing {CVE-2026-23242}\n- wifi: rtw88: check for PCI upstream bridge existence {CVE-2026-46092}\n- scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show() {CVE-2025-68229}\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed {CVE-2026-31697}\n- drm/display/dp_mst: Add protection against 0 vcpi {CVE-2025-71305}\n- ASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe() {CVE-2025-37793}\n- drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() {CVE-2026-53190}\n- HID: apple: avoid memory leak in apple_report_fixup() {CVE-2026-31520}\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() {CVE-2026-31522}\n- wifi: rtw88: Fix alignment fault in rtw_core_enable_beacon() {CVE-2025-71229}\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi {CVE-2026-53105}\n- net: bonding: fix NULL pointer dereference in bond_do_ioctl() {CVE-2026-53337}\n- firmware_loader: Fix possible resource leak in fw_log_firmware_info() {CVE-2024-53202}\n- drm/virtio: Fix driver removal with disabled KMS {CVE-2026-53347}\n- vxlan: Fix uninit-value in vxlan_vnifilter_dump() {CVE-2025-21716}\n- gpiolib: Fix crash on error in gpiochip_get_ngpios() {CVE-2025-21783}\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check {CVE-2025-38543}\n- net: bcmgenet: fix off-by-one in bcmgenet_put_txcb {CVE-2026-53088}\n- HID: multitouch: Check to ensure report responses match the request {CVE-2026-43047}\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() {CVE-2025-40115}\n- drm/xe/vm: Clear the scratch_pt pointer on error {CVE-2025-39811}\n- ice: ptp: don't WARN when controlling PF is unavailable {CVE-2026-43346}\n- ALSA: usb-audio: Fix NULL pointer deference in try_to_register_card {CVE-2025-40085}\n- regmap: maple: free entry on mas_store_gfp() failure {CVE-2026-23260}\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans {CVE-2026-52964}\n- wifi: brcmfmac: Fix error pointer dereference {CVE-2026-53093}\n- usb: storage: Fix memory leak in USB bulk transport {CVE-2025-68288}\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues {CVE-2026-43473}\n- HID: roccat: fix use-after-free in roccat_report_event {CVE-2026-43111}\n- drm/hyperv: Fix address space leak when Hyper-V DRM device is removed {CVE-2025-21978}\n- tap: free page on error paths in tap_get_user_xdp() {CVE-2026-46320}\n- net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode {CVE-2026-43180}\n- wifi: rtw88: fix device leak on probe failure {CVE-2026-31604}\n- zram: do not forget to endio for partial discard requests {CVE-2026-46089}\n- drm/vmwgfx: Return the correct value in vmw_translate_ptr functions {CVE-2026-23317}\n- usb: xhci: Fix memory leak in xhci_disable_slot() {CVE-2026-43432}\n- RDMA/mlx5: Fix memory leak in GET_DATA_DIRECT_SYSFS_PATH handler {CVE-2026-45922}\n- PCI: Fix reset_method_store() memory leak {CVE-2024-56745}\n- rbd: fix null-ptr-deref when device_add_disk() fails {CVE-2026-46079}\n- dm-integrity: Avoid divide by zero in table status in Inline mode {CVE-2025-21874}\n- net: stmmac: fix integer underflow in chain mode {CVE-2026-31649}\n- net/mlx5e: TC, delete flows only for existing peers {CVE-2026-23173}\n- idpf: fix checksums set in idpf_rx_rsc() {CVE-2025-21890}\n- be2net: pass wrb_params in case of OS2BMC {CVE-2025-40264}\n- wifi: ath12k: fix dma_free_coherent() pointer {CVE-2026-23135}\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() {CVE-2026-45872}\n- bus: mhi: host: Fix race between unprepare and queue_buf {CVE-2025-23151}\n- x86/tdx: Fix data leak in mmio_read() {CVE-2024-46794}\n- wifi: ath11k: fix memory leaks in beacon template setup {CVE-2026-53113}\n- Fix userfaultfd_api to return EINVAL as expected {CVE-2024-41027}\n- ice: fix using untrusted value of pkt_len in ice_vc_fdir_parse_raw() {CVE-2025-22117}\n- thunderbolt: Validate XDomain request packet size before type cast {CVE-2026-53147}\n- pps: fix warning in pps_register_cdev when register device fail {CVE-2025-40070}\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() {CVE-2026-53102}\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) {CVE-2026-43488}\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used {CVE-2025-38113}\n- ACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch() {CVE-2026-45982}\n- ACPI: video: Fix use-after-free in acpi_video_switch_brightness() {CVE-2025-40211}\n- libceph: define and enforce CEPH_MAX_KEY_LEN {CVE-2026-43304}\n- smb: client: fix off-by-8 bounds check in check_wsl_eas() {CVE-2026-31614}\n- ipv6: prevent possible UaF in addrconf_permanent_addr() {CVE-2026-43339}\n- efi: Fix reservation of unaccepted memory table {CVE-2026-45851}\n- ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access {CVE-2026-46094}\n- X.509: Fix out-of-bounds access when parsing extensions {CVE-2026-31430}\n- topology: Keep the cpumask unchanged when printing cpumap {CVE-2024-57917}\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check {CVE-2026-46006}\n- net: mana: fix use-after-free in add_adev() error path {CVE-2026-43056}\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation {CVE-2026-43133}\n- RDMA/irdma: Fix double free related to rereg_user_mr {CVE-2026-43120}\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response {CVE-2026-43334}\n- netfilter: flowtable: strictly check for maximum number of actions {CVE-2026-43329}\n- ACPI: pfr_update: Fix the driver update version check {CVE-2025-39701}\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early {CVE-2025-39861}\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet {CVE-2026-53112}\n- wifi: mac80211: increase scan_ies_len for S1G {CVE-2025-39957}\n- clsact: Fix use-after-free in init/destroy rollback asymmetry {CVE-2026-23413}\n- netfilter: nf_conntrack_h323: fix OOB read in decode_choice() {CVE-2026-43233}\n- netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry {CVE-2026-43114}\n- netfilter: bpf: defer hook memory release until rcu readers are done {CVE-2026-23412}\n- bpf: Fix stack-out-of-bounds write in devmap {CVE-2026-23359}\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow {CVE-2026-46136}\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() {CVE-2026-23363}\n- wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add {CVE-2025-71234}\n- crypto: iaa - Fix out-of-bounds index in find_empty_iaa_compression_mode {CVE-2025-71231}\n- io_uring: fix incorrect io_kiocb reference in io_link_skb {CVE-2025-39963}\n- octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() {CVE-2025-39944}\n- ixgbe: fix incorrect map used in eee linkmode {CVE-2025-39922}\n- mm/damon/sysfs: fix use-after-free in state_show() {CVE-2025-39877}\n- Bluetooth: btmtk: validate WMT event SKB length before struct access {CVE-2026-46140}\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() {CVE-2025-39860}\n- iommu/amd: Avoid stack buffer overflow from kernel cmdline {CVE-2025-38676}\n- scsi: megaraid_sas: Fix invalid node index {CVE-2025-38239}\n- KVM: SVM: Forcibly leave SMM mode on SHUTDOWN interception {CVE-2025-37957}\n- bnxt_en: Fix RSS context delete logic {CVE-2026-43260}\n- eth: bnxt: fix kernel panic in the bnxt_get_queue_stats{rx | tx} {CVE-2025-21973}\n- PCI/ASPM: Fix link state exit during switch upstream function removal {CVE-2024-58093}\n- mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file {CVE-2024-42138}\n- kdb: Fix buffer overflow during tab-complete {CVE-2024-39480}","status":"published","published":"2026-10-18T05:08:55Z","modified":"2026-10-26T09:43:33.426287911Z","updated_at":"2026-11-02T15:43:46.850893Z"},{"id":"MGASA-2026-0097","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:41.57748Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0098","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:42.526844Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2026:20826-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-2058: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2024-14027: xattr: switch to CLASS(fd) (bsc#1259420).\n- CVE-2025-40181: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (bsc#1253471).\n- CVE-2025-68265: nvme: fix admin request_queue lifetime (bsc#1255360).\n- CVE-2025-68310: s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump (bsc#1255160).\n- CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules (bsc#1264837).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: add xmit recursion limit to tunnel xmit functions (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23316: net: ipv4: fix ARM64 alignment fault in multipath hash seed (bsc#1260573).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23346: arm64: io: Rename ioremap_prot() to __ioremap_prot() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23375: mm: thp: deny THP for files on anonymous inodes (bsc#1260576).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23417: bpf: Fix constant blinding for PROBE_MEM32 stores (bsc#1261410).\n- CVE-2026-23436: net: add helpers for lookup and walking netdevs under netdev_lock() (bsc#1261617).\n- CVE-2026-23437: net: shaper: protect late read accesses to the hierarchy (bsc#1261635).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31392: smb: client: fix krb5 mount with username option (bsc#1261788).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31406: xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (bsc#1261629).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31435: netfs: Fix read abandonment during retry (bsc#1262601).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks (bsc#1262617).\n- CVE-2026-31456: mm/pagewalk: fix race between concurrent split and refault (bsc#1262627).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31503: udp: Fix wildcard bind conflict check when using hash2 (bsc#1263077).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31526: bpf: Fix exception exit lock checking for subprogs (bsc#1262662).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags (bsc#1263107).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit (bsc#1263074).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload() (bsc#1263048).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31658: net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() (bsc#1263052).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() (bsc#1263138).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31691: igb: remove napi_synchronize() in igb_down() (bsc#1263604).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43045: mshv: Refactor and rename memory region handling functions (bsc#1263942).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43082: net: txgbe: leave space for null terminators on property_entry (bsc#1264233).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43153: xfs: remove xfs_attr_leaf_hasname (bsc#1264586).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ACPI: video: Move Lenovo Legion S7 15ACH6 quirk to the right section (git-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/hdmi: Add quirk for TUXEDO IBS14G6 (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (stable-fixes).\n- ALSA: pcmtest: fix reference leak on failed device registration (git-fixes).\n- ALSA: pcmtest: Fix resource leaks in module init error paths (git-fixes).\n- ALSA: pcmtest: Return -EFAULT on pattern read copy failure (git-fixes).\n- ALSA: sc6000: Keep the programmed board state in card-private data (git-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- ALSA: virtio: drop an extaneous kernel-doc comment (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for \"VAD Detected\" (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- backlight: sky81452-backlight: Check return value of devm_gpiod_get_optional() in sky81452_bl_parse_dt() (git-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- bitfield: Add FIELD_MODIFY() helper (jsc#PED-14238).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (bsc#1260996).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: fix memset typo (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- bpf: Add third round of bounds deduction (git-fixes).\n- bpf: Fix u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- bpf: Improve bounds when s64 crosses sign boundary (git-fixes).\n- bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI (git-fixes).\n- btrfs: qgroup: update all parent qgroups when doing quick inherit (bsc#1258933).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays (git-fixes).\n- bus: rifsc: fix RIF configuration check for peripherals (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from \"scaling factor\" list (bsc#1249104).\n- crypto: af_alg - limit RX SG extraction by receive buffer budget (git-fixes).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix error codes in OTP reads (git-fixes).\n- crypto: atmel-sha204a - Fix OTP sysfs read and error handling (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-sha204a - Fix uninitialized data access on OTP read error (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: drivers - Switch back to struct platform_driver::remove() (jsc#PED-14238).\n- crypto: drivers - Use str_enable_disable-like helpers (jsc#PED-14238).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: iaa - Adjust workqueue allocation type (jsc#PED-14238).\n- crypto: iaa - fix per-node CPU counter reset in rebalance_wq_table() (git-fixes).\n- crypto: iaa - Move compression CRC into request object (jsc#PED-14238).\n- crypto: iaa - Optimize rebalance_wq_table() (jsc#PED-14238).\n- crypto: iaa - Remove potential infinite loop in check_completion() (jsc#PED-14238).\n- crypto: iaa - Remove unreachable pr_debug from iaa_crypto_cleanup_module (jsc#PED-14238).\n- crypto: iaa - Remove unused disable_async argument from iaa_decompress (jsc#PED-14238).\n- crypto: iaa - Replace sprintf with sysfs_emit in sysfs show functions (jsc#PED-14238).\n- crypto: iaa - Simplify init_iaa_device() (jsc#PED-14238).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: nx - Fix packed layout in struct nx842_crypto_header (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - #undef field_get() before local definition (jsc#PED-14238).\n- crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting (jsc#PED-14238).\n- crypto: qat - add bank state save and restore for qat_420xx (jsc#PED-14238).\n- crypto: qat - add command queue telemetry counters for GEN6 (jsc#PED-14238).\n- crypto: qat - add compression slice count for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service to telemetry (jsc#PED-14238).\n- crypto: qat - add firmware headers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add GEN6 firmware loader (jsc#PED-14238).\n- crypto: qat - add get_svc_slice_cnt() in device data structure (jsc#PED-14238).\n- crypto: qat - add live migration enablers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add macro to write 64-bit values to registers (jsc#PED-14238).\n- crypto: qat - add missing header inclusion (jsc#PED-14238).\n- crypto: qat - add qat_6xxx driver (jsc#PED-14238).\n- crypto: qat - add ring buffer idle telemetry counter for GEN6 (jsc#PED-14238).\n- crypto: qat - add support for decompression service to GEN6 devices (jsc#PED-14238).\n- crypto: qat - consolidate service enums (jsc#PED-14238).\n- crypto: qat - Constify struct pm_status_row (jsc#PED-14238).\n- crypto: qat - disable 4xxx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - disable 420xx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - do not export adf_cfg_services (jsc#PED-14238).\n- crypto: qat - enable power management debugfs for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable RAS support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable rate limiting feature for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable reporting of error counters for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable telemetry for GEN6 devices (jsc#PED-14238).\n- crypto: qat - export adf_get_service_mask() (jsc#PED-14238).\n- crypto: qat - export adf_init_admin_pm() (jsc#PED-14238).\n- crypto: qat - expose configuration functions (jsc#PED-14238).\n- crypto: qat - fix compression instance leak (git-fixes).\n- crypto: qat - fix IRQ cleanup on 6xxx probe failure (git-fixes).\n- crypto: qat - fix object goals in Makefiles (jsc#PED-14238.\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - Fix typo \"accelaration\" (jsc#PED-14238).\n- crypto: qat - fix virtual channel configuration for GEN6 devices (jsc#PED-14238).\n- crypto: qat - include qat_common in top Makefile (jsc#PED-14238).\n- crypto: qat - introduce fuse array (jsc#PED-14238).\n- crypto: qat - make adf_dev_autoreset() static (jsc#PED-14238).\n- crypto: qat - optimize allocations for fw authentication (jsc#PED-14238).\n- crypto: qat - refactor compression template logic (jsc#PED-14238).\n- crypto: qat - refactor FW signing algorithm (jsc#PED-14238).\n- crypto: qat - refactor ring-related debug functions (jsc#PED-14238).\n- crypto: qat - refactor service parsing logic (jsc#PED-14238).\n- crypto: qat - relocate and rename bank state structure definition (jsc#PED-14238).\n- crypto: qat - relocate bank state helper functions (jsc#PED-14238).\n- crypto: qat - relocate power management debugfs helper APIs (jsc#PED-14238).\n- crypto: qat - relocate service related functions (jsc#PED-14238).\n- crypto: qat - remove BITS_IN_DWORD() (jsc#PED-14238).\n- crypto: qat - Remove dst_null support (jsc#PED-14238).\n- crypto: qat - remove duplicate masking for GEN6 devices (jsc#PED-14238).\n- crypto: qat - remove initialization in device class (jsc#PED-14238).\n- crypto: qat - remove redundant FW image size check (jsc#PED-14238).\n- crypto: qat - remove unused adf_devmgr_get_first (jsc#PED-14238).\n- crypto: qat - remove unused members in suof structure (jsc#PED-14238).\n- crypto: qat - rename and relocate timer logic (jsc#PED-14238).\n- crypto: qat - reorder objects in qat_common Makefile (jsc#PED-14238).\n- crypto: qat - replace CHECK_STAT macro with static inline function (jsc#PED-14238).\n- crypto: qat - Replace kzalloc() + copy_from_user() with memdup_user() (jsc#PED-14238).\n- crypto: qat - restore ASYM service support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - Return pointer directly in adf_ctl_alloc_resources (jsc#PED-14238).\n- crypto: qat - set command ids as reserved (jsc#PED-14238).\n- crypto: qat - switch to standard pattern for PCI IDs (jsc#PED-14238).\n- crypto: qat - update firmware api (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in adf_gen4_hw_data.c (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in qat uclo.c (jsc#PED-14238).\n- crypto: qat - use simple_strtoull to improve qat_uclo_parse_num (jsc#PED-14238).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: qat - validate service in rate limiting sysfs api (jsc#PED-14238).\n- crypto: qat/qat_6xxx - Fix NULL vs IS_ERR() check in adf_probe() (jsc#PED-14238).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: tegra - Disable softirqs before finalizing request (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dmaengine: dw-axi-dmac: fix Alignment should match open parenthesis (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drivers/base/memory: fix memory block reference leak in poison accounting (git-fixes).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- erofs: add GFP_NOIO in the bio completion if needed (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: Fixed sysfs duplicate filename issue (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: arm_ffa: Use the correct buffer size during RXTX_MAP (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- firmware: google: framebuffer: Do not mark framebuffer as busy (git-fixes).\n- firmware: google: framebuffer: Do not unregister platform device (git-fixes).\n- gpio: of: clear OF_POPULATED on hog nodes in remove path (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: amd_sfh: don't log error when device discovery fails with -EOPNOTSUPP (git-fixes).\n- HID: apple: ensure the keyboard backlight is off if suspending (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: logitech-hidpp: Enable MX Master 4 over bluetooth (stable-fixes).\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hisi_acc_vfio_pci: add eq and aeq interruption restore (git-fixes).\n- hisi_acc_vfio_pci: bugfix cache write-back issue (git-fixes).\n- hisi_acc_vfio_pci: bugfix the problem of uninstalling driver (git-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hv_sock: update outdated comment for renamed vsock_stream_recvmsg() (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- hwmon: (ltc4286) Add missing MODULE_IMPORT_NS(\"PMBUS\") (git-fixes).\n- hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt (git-fixes).\n- hwmon: (powerz) Fix use-after-free on USB disconnect (git-fixes).\n- hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i2c: tegra: Add HS mode support (bsc#1261550).\n- i2c: tegra: Add Tegra256 support (bsc#1261550).\n- i2c: tegra: Do not configure DMA if not supported (bsc#1261550).\n- i2c: tegra: Don't mark devices with pins as IRQ safe (stable-fixes).\n- i2c: tegra: Update Tegra256 timing parameters (bsc#1261550).\n- i2c: tegra: Use separate variables for fast and fastplus (bsc#1261550).\n- i3c: dw: Fix memory leak in dw_i3c_master_i3c_xfers() (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- iio: adc: ad7192: Revert \"properly check spi_get_device_match_data()\" (stable-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- iio: frequency: admv1013: add dev variable (stable-fixes).\n- iio: frequency: admv1013: fix NULL pointer dereference on str (git-fixes).\n- Input: bcm5974 - recover from failed mode switch (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request \"event\" (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- interconnect: debugfs: fix devm_kstrdup and kfree mismatch (git-fixes).\n- io_uring/timeout: check unused sqe fields (git-fixes).\n- iommu/amd: move wait_on_sem() out of spinlock (git-fixes bsc#1260593).\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations (git-fixes bsc#1260593).\n- iommu/vt-d: Remove LPIG from page group response descriptor (jsc#PED-16113).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- ipv6: rpl: reserve mac_len headroom when recompressed SRH grows (git-fixes).\n- KVM: arm64: Allow cacheable stage 2 mapping using VMA flags (git-fixes).\n- KVM: arm64: Assume non-PFNMAP/MIXEDMAP VMAs can be mapped cacheable (git-fixes).\n- KVM: arm64: Block cacheable PFNMAP mapping (git-fixes).\n- KVM: arm64: Consolidate idreg callbacks (git-fixes).\n- KVM: arm64: Discard PC update state on vcpu reset (git-fixes).\n- KVM: arm64: Finalize ID registers only once per VM (git-fixes).\n- KVM: arm64: Fix MTE flag initialization for protected VMs (git-fixes).\n- KVM: arm64: Fix page leak in user_mem_abort() (git-fixes).\n- KVM: arm64: Fix Trace Buffer trap polarity for protected VMs (git-fixes).\n- KVM: arm64: Fix Trace Buffer trapping for protected VMs (git-fixes).\n- KVM: arm64: Fix vma_shift staleness on nested hwpoison path (git-fixes).\n- KVM: arm64: Hide S1POE from guests when not supported by the host (git-fixes).\n- KVM: arm64: Limit clearing of ID_{AA64PFR0,PFR1}_EL1.GIC to userspace irqchip (git-fixes).\n- KVM: arm64: Make all 32bit ID registers fully writable (git-fixes).\n- KVM: arm64: nv: Add trap config for DBGWCR\u003c15\u003e_EL1 (git-fixes).\n- KVM: arm64: nv: Return correct RES0 bits for FGT registers (git-fixes).\n- KVM: arm64: pkvm: Fallback to level-3 mapping on host stage-2 fault (git-fixes).\n- KVM: arm64: Read PMUVer as unsigned (git-fixes).\n- KVM: arm64: Rename the device variable to s2_force_noncacheable (git-fixes).\n- KVM: arm64: Return early from trace helpers when KVM isn't available (git-fixes).\n- KVM: arm64: Set ID_{AA64PFR0,PFR1}_EL1.GIC when GICv3 is configured (git-fixes).\n- KVM: arm64: vgic-v3: Release reserved slot outside of lpi_xa's lock (git-fixes).\n- KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).\n- KVM: nSVM: Use vcpu-\u003earch.cr2 when updating vmcb12 on nested #VMEXIT (git-fixes).\n- KVM: nVMX: Add consistency check for TSC_MULTIPLIER=0 (git-fixes).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created (git-fixes).\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (git-fixes).\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish (git-fixes).\n- KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock (git-fixes).\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU (git-fixes).\n- KVM: SVM: Disallow EFER.LMSLE when not supported by hardware (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Properly check RAX in the emulator for SVM instructions (git-fixes).\n- KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated (git-fixes).\n- KVM: TDX: Explicitly set user-return MSRs that *may* be clobbered by the TDX-Module (git-fixes).\n- KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter (git-fixes).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (git-fixes).\n- KVM: x86: Advertise EferLmsleUnsupported to userspace (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: X86: Fix array_index_nospec protection in __pv_send_ipi (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx283: Enter full standby when stopping streaming (git-fixes).\n- media: i2c: imx283: Fix hang when going from large to small resolution (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: core: Preserve OF node when ACPI handle is present (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net-shapers: don't free reply skb after genlmsg_reply() (git-fixes).\n- net/mlx5: Fix HCA caps leak on notifier init failure (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of \"old\" filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: Move current_speed debugfs file to mana_init_port() (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: broadcom: Save PHY counters during suspend (git-fixes).\n- net: phy: DP83TC811: add reading of abilities (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: phy: fix a return path in get_phy_c45_ids() (git-fixes).\n- net: phy: qcom: at803x: Use the correct bit to disable extended next page (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-apple: drop invalid put of admin queue reference count (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4 (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix admin queue leak on controller reset (git-fixes).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- openvswitch: vport: fix self-deadlock on release of tunnel ports (git-fixes).\n- panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() (bsc#1261149).\n- panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() (bsc#1261149).\n- panic: introduce helper functions for panic state (bsc#1261149).\n- panic: use angle-bracket include for panic.h (bsc#1261149).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI/ASPM: Fix pci_clear_and_set_config_dword() usage (git-fixes).\n- PCI/NPEM: Set LED_HW_PLUGGABLE for hotplug-capable ports (git-fixes).\n- PCI/TPH: Allow TPH enable for RCiEPs (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: dwc: rcar-gen4: Change EPC BAR alignment to 4K as per the documentation (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup (git-fixes).\n- PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (bsc#1261648).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Free up Endpoint resources during remove() (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse \"nvidia,refclk-select\" (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- pinctrl: realtek: Fix function signature for config argument (git-fixes).\n- pinctrl: renesas: rzg2l: Fix save/restore of {IOLH,IEN,PUPD,SMT} registers (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86: asus-wmi: adjust screenpad power/brightness handling (git-fixes).\n- platform/x86: asus-wmi: fix screenpad brightness range (git-fixes).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- printk/nbcon/panic: Allow printk kthread to sleep when the system is in panic (bsc#1261149).\n- printk/nbcon: Block printk kthreads when any CPU is in an emergency context (bsc#1261149).\n- printk/nbcon: Release nbcon consoles ownership in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: Restore IRQ in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: use panic_on_this_cpu() helper (bsc#1261149).\n- printk: Allow printk_trigger_flush() to flush all types (bsc#1262750).\n- printk: Allow to use the printk kthread immediately even for 1st nbcon (jsc#PED-7912).\n- printk: Avoid irq_work for printk_deferred() on suspend (bsc#1262750).\n- printk: Avoid scheduling irq_work on suspend (bsc#1262750).\n- printk: console_flush_one_record() code cleanup (bsc#1261149).\n- printk: Introduce console_flush_one_record (bsc#1261149).\n- printk: Use console_flush_one_record for legacy printer kthread (bsc#1261149).\n- pwm: imx-tpm: Count the number of enabled channels in probe (git-fixes).\n- qat: don't mess with -\u003ed_name (jsc#PED-14238).\n- r8152: fix incorrect register write to USB_UPHY_XTAL (git-fixes).\n- RDMA/irdma: Fix double free related to rereg_user_mr (git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- regulator: rk808: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Fix sram property parsing (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert \"ALSA: usb: Increase volume range that triggers a warning\" (git-fixes).\n- Revert \"serial: 8250: Revert \"drop lockdep annotation from serial8250_clear_IER()\"\" (bsc#1262480).\n- Revert \"serial: 8250: Switch to nbcon console\" (bsc#1262480).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259994).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259994).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259994).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: lpfc: Use the crc32c() function (bsc#1262019).\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues (git-fixes).\n- scsi: ses: Fix devices attaching to different hosts (git-fixes).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- scsi: ufs: ufs-pci: Add support for Intel Wildcat Lake (jsc#PED-13771).\n- selftests/bpf: Test cross-sign 64bits range refinement (git-fixes).\n- selftests/bpf: Test invariants on JSLT crossing sign (git-fixes).\n- selftests/bpf: test refining u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- selftests: net: build net/lib dependency in all target (bsc#1262245).\n- selinux: don't reserve xattr slot when we won't fill it (stable-fixes).\n- selinux: prune /sys/fs/selinux/disable (stable-fixes).\n- selinux: shrink critical section in sel_write_load() (stable-fixes).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- Set CONFIG_INTEL_TSX_MODE to follow upstream AUTO default (bsc#1263044).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- soc: qcom: ocmem: make the core clock optional (git-fixes).\n- soc: qcom: ocmem: register reasons for probe deferrals (git-fixes).\n- soc: qcom: ocmem: return -EPROBE_DEFER is ocmem is not available (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- soundwire: debugfs: initialize firmware_file to empty string (git-fixes).\n- spi: aspeed-smc: fix controller deregistration (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: bcm63xx: fix controller deregistration (git-fixes).\n- spi: bcmbca-hsspi: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: cadence: fix unclocked access on unbind (git-fixes).\n- spi: ch341: fix memory leaks on probe failures (git-fixes).\n- spi: coldfire-qspi: fix controller deregistration (git-fixes).\n- spi: dln2: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-espi: fix controller deregistration (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: fsl: fix controller deregistration (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: img-spfi: fix controller deregistration (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: lantiq-ssc: fix controller deregistration (git-fixes).\n- spi: meson-spicc: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix use-after-free on registration failure (git-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: fix memory leak in probe (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: mxic: fix controller deregistration (git-fixes).\n- spi: mxs: fix controller deregistration (git-fixes).\n- spi: npcm-pspi: fix controller deregistration (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix controller deregistration (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: pic32-sqi: fix controller deregistration (git-fixes).\n- spi: pic32: fix controller deregistration (git-fixes).\n- spi: pl022: fix controller deregistration (git-fixes).\n- spi: qup: fix controller deregistration (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rockchip: Read ISR, not IMR, to detect cs-inactive IRQ (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix NULL-deref on driver unbind (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: st-ssc4: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun6i: fix controller deregistration (git-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: ti-qspi: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix use-after-free on unbind (git-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynq-qspi: fix controller deregistration (git-fixes).\n- spi: zynq-qspi: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tools/power/turbostat: Fix microcode patch level output for AMD/Hygon (git-fixes).\n- tools: hv: Fix cross-compilation (git-fixes).\n- tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public() (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: Fix auth session leak in tpm2_get_random() error path (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tpm: Use kfree_sensitive() to free auth session in tpm_dev_release() (git-fixes).\n- tty: serial: ip22zilog: Fix section mispatch warning (git-fixes).\n- udp: Force compute_score to always inline (bsc#1241259).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (git-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_hid: Add missing error code (git-fixes).\n- usb: gadget: f_hid: don't call cdev_init while cdev in use (git-fixes).\n- usb: gadget: f_hid: move list and spinlock inits from bind to alloc (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (git-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (git-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (git-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- vfio/pci: Lock upstream bridge for vfio_pci_core_disable() (git-fixes).\n- vfio/pds: Fix memory leak in pds_vfio_dirty_enable() (git-fixes).\n- vfio/pds: Fix missing detach_ioas op (git-fixes).\n- vfio/pds: replace bitmap_free with vfree (git-fixes).\n- vfio/type1: Fix error unwind in migration dirty bitmap allocation (git-fixes).\n- vfio: Fix unbalanced vfio_df_close call in no-iommu mode (git-fixes).\n- vfio: Prevent open_count decrement to negative (git-fixes).\n- virt: arm-cca-guest: fix error check for RSI_INCOMPLETE (git-fixes).\n- virt: sev-guest: Do not use host-controlled page order in cleanup path (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath10k: fix station lookup failure during disconnect (git-fixes).\n- wifi: ath11k: fix memory leaks in beacon template setup (git-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert \"Fix locking in error paths\" (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Place upper limit on station AID (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix AMPDU state handling in mt7925_tx_check_aggr (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7925: Fix incorrect MLO mode in firmware control (git-fixes).\n- wifi: mt76: mt7925: fix incorrect TLV length in CLC command (git-fixes).\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtl8xxxu: fix potential use of uninitialized value (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: Add additional USB IDs for RTL8812BU (bsc#1263135).\n- wifi: rtw88: Add BUFFALO WI-U3-866DHP to the USB ID list (bsc#1263135).\n- wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 (bsc#1263135).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw88: rtw8822bu VID/PID for BUFFALO WI-U2-866DM (bsc#1263135).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- x86/acpi/boot: Correct acpi_is_processor_usable() check again (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot/sev: Support memory acceptance in the EFI stub under SVSM (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Fix early boot failures on SEV-ES/SNP guests (git-fixes).\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges() (git-fixes).\n- x86/sev: Add missing RIP_REL_REF() invocations during sme_enable() (git-fixes).\n- x86/sev: Do not touch VMSA pages during SNP guest memory kdump (git-fixes).\n- x86/sev: Ensure SVSM reserved fields in a page validation entry are initialized to zero (git-fixes).\n- x86/sev: Fix operator precedence in GHCB_MSR_VMPL_REQ_LEVEL macro (git-fixes).\n- x86/sev: Improve handling of writes to intercepted TSC MSRs (git-fixes).\n- x86/sev: Make sure pages are not skipped during kdump (git-fixes).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951 bsc#1263044).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951 bsc#1263044).\n- x86/vmware: Parse MP tables for SEV-SNP enabled guests under VMware hypervisors (git-fixes).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n","status":"published","published":"2026-05-28T12:58:58Z","modified":"2026-05-31T18:24:29.154766683Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-23317","title":"CVE-2026-23317 in linux - Patched by Root","description":"Root has patched CVE-2026-23317 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:16:01.321066007Z","updated_at":"2026-11-02T15:53:31.773105Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23317","title":"CVE-2026-23317 in linux - Patched by Root","description":"Root has patched CVE-2026-23317 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:04.415309185Z","updated_at":"2026-11-06T16:59:13.602872Z"},{"id":"SUSE-SU-2026:1573-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23259: io_uring/rw: free potentially allocated iovec on cache put failure (bsc#1259866).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: boards: fix unmet dependency on PINCTRL (git-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: cs42l43: Report insert for exotic peripherals (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: ISO: Fix defer tests being unstable (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: qca: fix ROM version reading on WCN3998 chips (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove 'scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans)' changes (bsc#1257506).\n- Revert 'drm/i915/display: Add quirk to skip retraining of dp link' (bsc#1253129).\n- Revert 'drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug' (git-fixes).\n- USB: add QUIRK_NO_BOS for video capture several devices (stable-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- cifs: Fix locking usage for tcon fields (git-fixes).\n- cifs: force interface update before a fresh session setup (git-fixes).\n- cifs: make default value of retrans as zero (git-fixes).\n- cifs: some missing initializations on replay (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- cpufreq/amd-pstate: Remove the redundant verify() function (bsc#1252803).\n- cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq (bsc#1252803).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Do not skip unrelated mode changes in DSC validation (git-fixes).\n- drm/amd/display: Fallback to boot snapshot for dispclk (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd/display: Wrap dcn32_override_min_req_memclk() in DC_FP_{START, END} (git-fixes).\n- drm/amd/pm: add missing od setting PP_OD_FEATURE_ZERO_FAN_BIT for smu v14 (git-fixes).\n- drm/amd/pm: remove invalid gpu_metrics.energy_accumulator on smu v13.0.x (stable-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd: fix dcn 2.01 check (git-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub4.1.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/vcn5: Add SMU dpm interface type (stable-fixes).\n- drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB (git-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix kernel-doc comments for some LUT properties (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: fix gpu idle power consumption issue for gfx v12 (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu: prevent immediate PASID reuse case (stable-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/exynos/vidi: Remove redundant error handling in vidi_get_modes() (stable-fixes).\n- drm/exynos: vidi: fix to avoid directly dereferencing user pointer (stable-fixes).\n- drm/exynos: vidi: use ctx-\u003elock to protect struct vidi_context member variables related to memory alloc/free\n  (stable-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state (git-fixes).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- drm/i915/dsi: Do not do DSC horizontal timing adjustments in command mode (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/imagination: Fix deadlock in soft reset sequence (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/msm: Fix dma_free_attrs() buffer size (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/ttm/tests: Fix build failure on PREEMPT_RT (stable-fixes).\n- drm/xe/oa: Allow reading after disabling OA stream (git-fixes).\n- drm/xe/reg_sr: Fix leak on xa_store failure (git-fixes).\n- drm/xe: Do not preempt fence signaling CS instructions (git-fixes).\n- drm/xe: Open-code GGTT MMIO access protection (git-fixes).\n- drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- irqchip/qcom-mpm: Add missing mailbox TX done acknowledgment (git-fixes).\n- mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations (stable-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fixes).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208). Refresh:\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- s390/debug: Pass in and enforce output buffer size for format handlers (jsc#PED-15582).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- smb: client: add proper locking around ses-\u003eiface_last_update (git-fixes).\n- smb: client: fix broken multichannel with krb5+signing (git-fixes).\n- smb: client: fix cifs_pick_channel when channels are equally loaded (git-fixes).\n- smb: client: fix in-place encryption corruption in SMB2_write() (git-fixes).\n- smb: client: fix krb5 mount with username option (git-fixes).\n- smb: client: prevent races in -\u003equery_interfaces() (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: core: new quirk to handle devices with zero configurations (stable-fixes).\n- usb: core: phy: avoid double use of 'usb3-phy' (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- vhost: fix caching attributes of MMIO regions by setting them explicitly (git-fixes).\n- vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 (git-fixes).\n- watchdog/perf: properly initialize the turbo mode timestamp and rearm counter (bsc#1256504).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n- xenbus: Use .freeze/.thaw to handle xenbus devices (git-fixes).\n","status":"published","published":"2026-04-23T15:52:40Z","modified":"2026-04-24T08:15:33.422826Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:1574-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-68818: scsi: Revert 'scsi: qla2xxx: Perform lockless command completion in abort path' (bsc#1256675).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n\nThe following non-security bugs were fixed:\n\n- PCI/ACS: Fix 'pci=config_acs=' parameter (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix pci_slot_trylock() error handling (git-fixes).\n- PCI: dwc: ep: Return -ENOMEM for allocation failures (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- nvme-fc: use ctrl state getter (git-fixes bsc#1215492).\n- nvme-pci: fix queue unquiesce check on slot_reset (git-fixes).\n- nvme-pci: skip nvme_write_sq_db on empty rqlist (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-23T15:52:59Z","modified":"2026-04-24T08:15:42.484711Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:1606-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-nelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n\nThe following non security issues were fixed:\n\n- nvme-fc: use ctrl state getter (git-fixes bsc#1215492).\n- nvme-pci: fix queue unquiesce check on slot_reset (git-fixes).\n- nvme-pci: skip nvme_write_sq_db on empty rqlist (git-fixes).\n- PCI: dwc: ep: Return -ENOMEM for allocation failures (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix pci_slot_trylock() error handling (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI/ACS: Fix 'pci=config_acs=' parameter (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-24T11:50:23Z","modified":"2026-04-25T07:46:03.231244Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:1643-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing (bsc#1253122).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-28T13:27:21Z","modified":"2026-04-30T18:24:15.617097Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:1661-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: register hooks last when adding new chain/flowtable (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23259: io_uring/rw: free potentially allocated iovec on cache put failure (bsc#1259866).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: export bpf_link_inc_not_zero (bsc#1260735).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: cs42l43: Report insert for exotic peripherals (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: Intel: boards: fix unmet dependency on PINCTRL (git-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: ISO: Fix defer tests being unstable (git-fixes).\n- Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: qca: fix ROM version reading on WCN3998 chips (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- cifs: Fix locking usage for tcon fields (git-fixes).\n- cifs: force interface update before a fresh session setup (git-fixes).\n- cifs: make default value of retrans as zero (git-fixes).\n- cifs: some missing initializations on replay (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- cpufreq/amd-pstate: Remove the redundant verify() function (bsc#1252803).\n- cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq (bsc#1252803).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug (git-fixes).\n- drm/amd: fix dcn 2.01 check (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Do not skip unrelated mode changes in DSC validation (git-fixes).\n- drm/amd/display: Fallback to boot snapshot for dispclk (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd/display: Wrap dcn32_override_min_req_memclk() in DC_FP_{START, END} (git-fixes).\n- drm/amd/pm: add missing od setting PP_OD_FEATURE_ZERO_FAN_BIT for smu v14 (git-fixes).\n- drm/amd/pm: remove invalid gpu_metrics.energy_accumulator on smu v13.0.x (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB (git-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: fix gpu idle power consumption issue for gfx v12 (stable-fixes).\n- drm/amdgpu: Fix kernel-doc comments for some LUT properties (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu: prevent immediate PASID reuse case (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub4.1.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/vcn5: Add SMU dpm interface type (stable-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/exynos: vidi: fix to avoid directly dereferencing user pointer (stable-fixes).\n- drm/exynos/vidi: Remove redundant error handling in vidi_get_modes() (stable-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state (git-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/imagination: Fix deadlock in soft reset sequence (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm: Fix dma_free_attrs() buffer size (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/ttm/tests: Fix build failure on PREEMPT_RT (stable-fixes).\n- drm/xe: Do not preempt fence signaling CS instructions (git-fixes).\n- drm/xe: Open-code GGTT MMIO access protection (git-fixes).\n- drm/xe/oa: Allow reading after disabling OA stream (git-fixes).\n- drm/xe/reg_sr: Fix leak on xa_store failure (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: don't use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- irqchip/qcom-mpm: Add missing mailbox TX done acknowledgment (git-fixes).\n- mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations (stable-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fixes).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- s390/debug: Pass in and enforce output buffer size for format handlers (jsc#PED-15582.\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- smb: client: add proper locking around ses-\u003eiface_last_update (git-fixes).\n- smb: client: fix broken multichannel with krb5+signing (git-fixes).\n- smb: client: fix cifs_pick_channel when channels are equally loaded (git-fixes).\n- smb: client: fix in-place encryption corruption in SMB2_write() (git-fixes).\n- smb: client: fix krb5 mount with username option (git-fixes).\n- smb: client: prevent races in -\u003equery_interfaces() (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- USB: add QUIRK_NO_BOS for video capture several devices (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: don't power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- usb: core: new quirk to handle devices with zero configurations (stable-fixes).\n- usb: core: phy: avoid double use of 'usb3-phy' (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- vhost: fix caching attributes of MMIO regions by setting them explicitly (git-fixes).\n- vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 (git-fixes).\n- watchdog/perf: properly initialize the turbo mode timestamp and rearm counter (bsc#1256504).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n- xenbus: Use .freeze/.thaw to handle xenbus devices (git-fixes).\n","status":"published","published":"2026-04-30T12:05:10Z","modified":"2026-05-01T08:17:19.513034Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:21114-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T17:04:49Z","modified":"2026-04-18T18:25:53.212585Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21123-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T18:28:29Z","modified":"2026-04-18T18:25:56.735736Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21255-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Micro (RT) 6.0 and 6.1 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: register hooks last when adding new chain/flowtable (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: export bpf_link_inc_not_zero (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- comedi: Reinit dev-spinlock between attachments to low-level drivers (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: don't use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186 bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669 ltc#212590).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669 ltc#212590).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: don't power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Don't default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-17T15:00:24Z","modified":"2026-04-24T18:25:08.602484Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:2134-1","title":"Security update for the Linux Kernel RT (Live Patch 0 for SUSE Linux Enterprise 15 SP7)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-150700.5 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-05-29T23:44:06Z","modified":"2026-06-02T18:24:25.566548933Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:2149-1","title":"Security update for the Linux Kernel (Live Patch 27 for SUSE Linux Enterprise 15 SP5)","description":"\nThis update for the SUSE Linux Enterprise Kernel 5.14.21-150500.55.110 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-05-31T07:06:33Z","modified":"2026-06-02T08:45:04.383504708Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:2159-1","title":"Security update for the Linux Kernel (Live Patch 29 for SUSE Linux Enterprise 15 SP5)","description":"\nThis update for the SUSE Linux Enterprise Kernel 5.14.21-150500.55.116 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-05-31T10:06:26Z","modified":"2026-06-02T08:45:04.383537213Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:2172-1","title":"Security update for the Linux Kernel (Live Patch 20 for SUSE Linux Enterprise 15 SP6)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-150600.23.87 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-05-31T14:06:07Z","modified":"2026-06-02T08:45:04.328054457Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:2176-1","title":"Security update for the Linux Kernel (Live Patch 1 for SUSE Linux Enterprise 15 SP7)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-150700.53.3 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-05-31T19:36:13Z","modified":"2026-06-02T08:45:04.474215019Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:2181-1","title":"Security update for the Linux Kernel (Live Patch 8 for SUSE Linux Enterprise 15 SP7)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-150700.53.28 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T00:34:11Z","modified":"2026-06-02T08:45:04.480730764Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21834-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-2058: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2024-14027: xattr: switch to CLASS(fd) (bsc#1259420).\n- CVE-2025-40181: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (bsc#1253471).\n- CVE-2025-68265: nvme: fix admin request_queue lifetime (bsc#1255360).\n- CVE-2025-68310: s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump (bsc#1255160).\n- CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules (bsc#1264837).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: add xmit recursion limit to tunnel xmit functions (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23316: net: ipv4: fix ARM64 alignment fault in multipath hash seed (bsc#1260573).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23346: arm64: io: Rename ioremap_prot() to __ioremap_prot() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23375: mm: thp: deny THP for files on anonymous inodes (bsc#1260576).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23417: bpf: Fix constant blinding for PROBE_MEM32 stores (bsc#1261410).\n- CVE-2026-23436: net: add helpers for lookup and walking netdevs under netdev_lock() (bsc#1261617).\n- CVE-2026-23437: net: shaper: protect late read accesses to the hierarchy (bsc#1261635).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31392: smb: client: fix krb5 mount with username option (bsc#1261788).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31406: xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (bsc#1261629).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31435: netfs: Fix read abandonment during retry (bsc#1262601).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks (bsc#1262617).\n- CVE-2026-31456: mm/pagewalk: fix race between concurrent split and refault (bsc#1262627).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31503: udp: Fix wildcard bind conflict check when using hash2 (bsc#1263077).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31526: bpf: Fix exception exit lock checking for subprogs (bsc#1262662).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags (bsc#1263107).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit (bsc#1263074).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload() (bsc#1263048).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31658: net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() (bsc#1263052).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() (bsc#1263138).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31691: igb: remove napi_synchronize() in igb_down() (bsc#1263604).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43045: mshv: Refactor and rename memory region handling functions (bsc#1263942).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43082: net: txgbe: leave space for null terminators on property_entry (bsc#1264233).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43153: xfs: remove xfs_attr_leaf_hasname (bsc#1264586).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ACPI: video: Move Lenovo Legion S7 15ACH6 quirk to the right section (git-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/hdmi: Add quirk for TUXEDO IBS14G6 (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (stable-fixes).\n- ALSA: pcmtest: fix reference leak on failed device registration (git-fixes).\n- ALSA: pcmtest: Fix resource leaks in module init error paths (git-fixes).\n- ALSA: pcmtest: Return -EFAULT on pattern read copy failure (git-fixes).\n- ALSA: sc6000: Keep the programmed board state in card-private data (git-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- ALSA: virtio: drop an extaneous kernel-doc comment (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for \"VAD Detected\" (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- backlight: sky81452-backlight: Check return value of devm_gpiod_get_optional() in sky81452_bl_parse_dt() (git-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- bitfield: Add FIELD_MODIFY() helper (jsc#PED-14238).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (bsc#1260996).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: fix memset typo (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- bpf: Add third round of bounds deduction (git-fixes).\n- bpf: Fix u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- bpf: Improve bounds when s64 crosses sign boundary (git-fixes).\n- bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI (git-fixes).\n- btrfs: qgroup: update all parent qgroups when doing quick inherit (bsc#1258933).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays (git-fixes).\n- bus: rifsc: fix RIF configuration check for peripherals (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from \"scaling factor\" list (bsc#1249104).\n- crypto: af_alg - limit RX SG extraction by receive buffer budget (git-fixes).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix error codes in OTP reads (git-fixes).\n- crypto: atmel-sha204a - Fix OTP sysfs read and error handling (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-sha204a - Fix uninitialized data access on OTP read error (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: drivers - Switch back to struct platform_driver::remove() (jsc#PED-14238).\n- crypto: drivers - Use str_enable_disable-like helpers (jsc#PED-14238).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: iaa - Adjust workqueue allocation type (jsc#PED-14238).\n- crypto: iaa - fix per-node CPU counter reset in rebalance_wq_table() (git-fixes).\n- crypto: iaa - Move compression CRC into request object (jsc#PED-14238).\n- crypto: iaa - Optimize rebalance_wq_table() (jsc#PED-14238).\n- crypto: iaa - Remove potential infinite loop in check_completion() (jsc#PED-14238).\n- crypto: iaa - Remove unreachable pr_debug from iaa_crypto_cleanup_module (jsc#PED-14238).\n- crypto: iaa - Remove unused disable_async argument from iaa_decompress (jsc#PED-14238).\n- crypto: iaa - Replace sprintf with sysfs_emit in sysfs show functions (jsc#PED-14238).\n- crypto: iaa - Simplify init_iaa_device() (jsc#PED-14238).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: nx - Fix packed layout in struct nx842_crypto_header (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - #undef field_get() before local definition (jsc#PED-14238).\n- crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting (jsc#PED-14238).\n- crypto: qat - add bank state save and restore for qat_420xx (jsc#PED-14238).\n- crypto: qat - add command queue telemetry counters for GEN6 (jsc#PED-14238).\n- crypto: qat - add compression slice count for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service to telemetry (jsc#PED-14238).\n- crypto: qat - add firmware headers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add GEN6 firmware loader (jsc#PED-14238).\n- crypto: qat - add get_svc_slice_cnt() in device data structure (jsc#PED-14238).\n- crypto: qat - add live migration enablers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add macro to write 64-bit values to registers (jsc#PED-14238).\n- crypto: qat - add missing header inclusion (jsc#PED-14238).\n- crypto: qat - add qat_6xxx driver (jsc#PED-14238).\n- crypto: qat - add ring buffer idle telemetry counter for GEN6 (jsc#PED-14238).\n- crypto: qat - add support for decompression service to GEN6 devices (jsc#PED-14238).\n- crypto: qat - consolidate service enums (jsc#PED-14238).\n- crypto: qat - Constify struct pm_status_row (jsc#PED-14238).\n- crypto: qat - disable 4xxx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - disable 420xx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - do not export adf_cfg_services (jsc#PED-14238).\n- crypto: qat - enable power management debugfs for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable RAS support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable rate limiting feature for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable reporting of error counters for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable telemetry for GEN6 devices (jsc#PED-14238).\n- crypto: qat - export adf_get_service_mask() (jsc#PED-14238).\n- crypto: qat - export adf_init_admin_pm() (jsc#PED-14238).\n- crypto: qat - expose configuration functions (jsc#PED-14238).\n- crypto: qat - fix compression instance leak (git-fixes).\n- crypto: qat - fix IRQ cleanup on 6xxx probe failure (git-fixes).\n- crypto: qat - fix object goals in Makefiles (jsc#PED-14238.\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - Fix typo \"accelaration\" (jsc#PED-14238).\n- crypto: qat - fix virtual channel configuration for GEN6 devices (jsc#PED-14238).\n- crypto: qat - include qat_common in top Makefile (jsc#PED-14238).\n- crypto: qat - introduce fuse array (jsc#PED-14238).\n- crypto: qat - make adf_dev_autoreset() static (jsc#PED-14238).\n- crypto: qat - optimize allocations for fw authentication (jsc#PED-14238).\n- crypto: qat - refactor compression template logic (jsc#PED-14238).\n- crypto: qat - refactor FW signing algorithm (jsc#PED-14238).\n- crypto: qat - refactor ring-related debug functions (jsc#PED-14238).\n- crypto: qat - refactor service parsing logic (jsc#PED-14238).\n- crypto: qat - relocate and rename bank state structure definition (jsc#PED-14238).\n- crypto: qat - relocate bank state helper functions (jsc#PED-14238).\n- crypto: qat - relocate power management debugfs helper APIs (jsc#PED-14238).\n- crypto: qat - relocate service related functions (jsc#PED-14238).\n- crypto: qat - remove BITS_IN_DWORD() (jsc#PED-14238).\n- crypto: qat - Remove dst_null support (jsc#PED-14238).\n- crypto: qat - remove duplicate masking for GEN6 devices (jsc#PED-14238).\n- crypto: qat - remove initialization in device class (jsc#PED-14238).\n- crypto: qat - remove redundant FW image size check (jsc#PED-14238).\n- crypto: qat - remove unused adf_devmgr_get_first (jsc#PED-14238).\n- crypto: qat - remove unused members in suof structure (jsc#PED-14238).\n- crypto: qat - rename and relocate timer logic (jsc#PED-14238).\n- crypto: qat - reorder objects in qat_common Makefile (jsc#PED-14238).\n- crypto: qat - replace CHECK_STAT macro with static inline function (jsc#PED-14238).\n- crypto: qat - Replace kzalloc() + copy_from_user() with memdup_user() (jsc#PED-14238).\n- crypto: qat - restore ASYM service support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - Return pointer directly in adf_ctl_alloc_resources (jsc#PED-14238).\n- crypto: qat - set command ids as reserved (jsc#PED-14238).\n- crypto: qat - switch to standard pattern for PCI IDs (jsc#PED-14238).\n- crypto: qat - update firmware api (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in adf_gen4_hw_data.c (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in qat uclo.c (jsc#PED-14238).\n- crypto: qat - use simple_strtoull to improve qat_uclo_parse_num (jsc#PED-14238).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: qat - validate service in rate limiting sysfs api (jsc#PED-14238).\n- crypto: qat/qat_6xxx - Fix NULL vs IS_ERR() check in adf_probe() (jsc#PED-14238).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: tegra - Disable softirqs before finalizing request (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dmaengine: dw-axi-dmac: fix Alignment should match open parenthesis (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drivers/base/memory: fix memory block reference leak in poison accounting (git-fixes).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- erofs: add GFP_NOIO in the bio completion if needed (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: Fixed sysfs duplicate filename issue (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: arm_ffa: Use the correct buffer size during RXTX_MAP (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- firmware: google: framebuffer: Do not mark framebuffer as busy (git-fixes).\n- firmware: google: framebuffer: Do not unregister platform device (git-fixes).\n- gpio: of: clear OF_POPULATED on hog nodes in remove path (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: amd_sfh: don't log error when device discovery fails with -EOPNOTSUPP (git-fixes).\n- HID: apple: ensure the keyboard backlight is off if suspending (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: logitech-hidpp: Enable MX Master 4 over bluetooth (stable-fixes).\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hisi_acc_vfio_pci: add eq and aeq interruption restore (git-fixes).\n- hisi_acc_vfio_pci: bugfix cache write-back issue (git-fixes).\n- hisi_acc_vfio_pci: bugfix the problem of uninstalling driver (git-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hv_sock: update outdated comment for renamed vsock_stream_recvmsg() (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- hwmon: (ltc4286) Add missing MODULE_IMPORT_NS(\"PMBUS\") (git-fixes).\n- hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt (git-fixes).\n- hwmon: (powerz) Fix use-after-free on USB disconnect (git-fixes).\n- hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i2c: tegra: Add HS mode support (bsc#1261550).\n- i2c: tegra: Add Tegra256 support (bsc#1261550).\n- i2c: tegra: Do not configure DMA if not supported (bsc#1261550).\n- i2c: tegra: Don't mark devices with pins as IRQ safe (stable-fixes).\n- i2c: tegra: Update Tegra256 timing parameters (bsc#1261550).\n- i2c: tegra: Use separate variables for fast and fastplus (bsc#1261550).\n- i3c: dw: Fix memory leak in dw_i3c_master_i3c_xfers() (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- iio: adc: ad7192: Revert \"properly check spi_get_device_match_data()\" (stable-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- iio: frequency: admv1013: add dev variable (stable-fixes).\n- iio: frequency: admv1013: fix NULL pointer dereference on str (git-fixes).\n- Input: bcm5974 - recover from failed mode switch (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request \"event\" (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- interconnect: debugfs: fix devm_kstrdup and kfree mismatch (git-fixes).\n- io_uring/timeout: check unused sqe fields (git-fixes).\n- iommu/amd: move wait_on_sem() out of spinlock (git-fixes bsc#1260593).\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations (git-fixes bsc#1260593).\n- iommu/vt-d: Remove LPIG from page group response descriptor (jsc#PED-16113).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- ipv6: rpl: reserve mac_len headroom when recompressed SRH grows (git-fixes).\n- KVM: arm64: Allow cacheable stage 2 mapping using VMA flags (git-fixes).\n- KVM: arm64: Assume non-PFNMAP/MIXEDMAP VMAs can be mapped cacheable (git-fixes).\n- KVM: arm64: Block cacheable PFNMAP mapping (git-fixes).\n- KVM: arm64: Consolidate idreg callbacks (git-fixes).\n- KVM: arm64: Discard PC update state on vcpu reset (git-fixes).\n- KVM: arm64: Finalize ID registers only once per VM (git-fixes).\n- KVM: arm64: Fix MTE flag initialization for protected VMs (git-fixes).\n- KVM: arm64: Fix page leak in user_mem_abort() (git-fixes).\n- KVM: arm64: Fix Trace Buffer trap polarity for protected VMs (git-fixes).\n- KVM: arm64: Fix Trace Buffer trapping for protected VMs (git-fixes).\n- KVM: arm64: Fix vma_shift staleness on nested hwpoison path (git-fixes).\n- KVM: arm64: Hide S1POE from guests when not supported by the host (git-fixes).\n- KVM: arm64: Limit clearing of ID_{AA64PFR0,PFR1}_EL1.GIC to userspace irqchip (git-fixes).\n- KVM: arm64: Make all 32bit ID registers fully writable (git-fixes).\n- KVM: arm64: nv: Add trap config for DBGWCR\u003c15\u003e_EL1 (git-fixes).\n- KVM: arm64: nv: Return correct RES0 bits for FGT registers (git-fixes).\n- KVM: arm64: pkvm: Fallback to level-3 mapping on host stage-2 fault (git-fixes).\n- KVM: arm64: Read PMUVer as unsigned (git-fixes).\n- KVM: arm64: Rename the device variable to s2_force_noncacheable (git-fixes).\n- KVM: arm64: Return early from trace helpers when KVM isn't available (git-fixes).\n- KVM: arm64: Set ID_{AA64PFR0,PFR1}_EL1.GIC when GICv3 is configured (git-fixes).\n- KVM: arm64: vgic-v3: Release reserved slot outside of lpi_xa's lock (git-fixes).\n- KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).\n- KVM: nSVM: Use vcpu-\u003earch.cr2 when updating vmcb12 on nested #VMEXIT (git-fixes).\n- KVM: nVMX: Add consistency check for TSC_MULTIPLIER=0 (git-fixes).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created (git-fixes).\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (git-fixes).\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish (git-fixes).\n- KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock (git-fixes).\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU (git-fixes).\n- KVM: SVM: Disallow EFER.LMSLE when not supported by hardware (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Properly check RAX in the emulator for SVM instructions (git-fixes).\n- KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated (git-fixes).\n- KVM: TDX: Explicitly set user-return MSRs that *may* be clobbered by the TDX-Module (git-fixes).\n- KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter (git-fixes).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (git-fixes).\n- KVM: x86: Advertise EferLmsleUnsupported to userspace (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: X86: Fix array_index_nospec protection in __pv_send_ipi (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx283: Enter full standby when stopping streaming (git-fixes).\n- media: i2c: imx283: Fix hang when going from large to small resolution (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: core: Preserve OF node when ACPI handle is present (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net-shapers: don't free reply skb after genlmsg_reply() (git-fixes).\n- net/mlx5: Fix HCA caps leak on notifier init failure (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of \"old\" filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: Move current_speed debugfs file to mana_init_port() (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: broadcom: Save PHY counters during suspend (git-fixes).\n- net: phy: DP83TC811: add reading of abilities (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: phy: fix a return path in get_phy_c45_ids() (git-fixes).\n- net: phy: qcom: at803x: Use the correct bit to disable extended next page (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-apple: drop invalid put of admin queue reference count (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4 (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix admin queue leak on controller reset (git-fixes).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- openvswitch: vport: fix self-deadlock on release of tunnel ports (git-fixes).\n- panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() (bsc#1261149).\n- panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() (bsc#1261149).\n- panic: introduce helper functions for panic state (bsc#1261149).\n- panic: use angle-bracket include for panic.h (bsc#1261149).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI/ASPM: Fix pci_clear_and_set_config_dword() usage (git-fixes).\n- PCI/NPEM: Set LED_HW_PLUGGABLE for hotplug-capable ports (git-fixes).\n- PCI/TPH: Allow TPH enable for RCiEPs (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: dwc: rcar-gen4: Change EPC BAR alignment to 4K as per the documentation (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup (git-fixes).\n- PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (bsc#1261648).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Free up Endpoint resources during remove() (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse \"nvidia,refclk-select\" (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- pinctrl: realtek: Fix function signature for config argument (git-fixes).\n- pinctrl: renesas: rzg2l: Fix save/restore of {IOLH,IEN,PUPD,SMT} registers (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86: asus-wmi: adjust screenpad power/brightness handling (git-fixes).\n- platform/x86: asus-wmi: fix screenpad brightness range (git-fixes).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- printk/nbcon/panic: Allow printk kthread to sleep when the system is in panic (bsc#1261149).\n- printk/nbcon: Block printk kthreads when any CPU is in an emergency context (bsc#1261149).\n- printk/nbcon: Release nbcon consoles ownership in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: Restore IRQ in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: use panic_on_this_cpu() helper (bsc#1261149).\n- printk: Allow printk_trigger_flush() to flush all types (bsc#1262750).\n- printk: Allow to use the printk kthread immediately even for 1st nbcon (jsc#PED-7912).\n- printk: Avoid irq_work for printk_deferred() on suspend (bsc#1262750).\n- printk: Avoid scheduling irq_work on suspend (bsc#1262750).\n- printk: console_flush_one_record() code cleanup (bsc#1261149).\n- printk: Introduce console_flush_one_record (bsc#1261149).\n- printk: Use console_flush_one_record for legacy printer kthread (bsc#1261149).\n- pwm: imx-tpm: Count the number of enabled channels in probe (git-fixes).\n- qat: don't mess with -\u003ed_name (jsc#PED-14238).\n- r8152: fix incorrect register write to USB_UPHY_XTAL (git-fixes).\n- RDMA/irdma: Fix double free related to rereg_user_mr (git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- regulator: rk808: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Fix sram property parsing (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert \"ALSA: usb: Increase volume range that triggers a warning\" (git-fixes).\n- Revert \"serial: 8250: Revert \"drop lockdep annotation from serial8250_clear_IER()\"\" (bsc#1262480).\n- Revert \"serial: 8250: Switch to nbcon console\" (bsc#1262480).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259994).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259994).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259994).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: lpfc: Use the crc32c() function (bsc#1262019).\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues (git-fixes).\n- scsi: ses: Fix devices attaching to different hosts (git-fixes).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- scsi: ufs: ufs-pci: Add support for Intel Wildcat Lake (jsc#PED-13771).\n- selftests/bpf: Test cross-sign 64bits range refinement (git-fixes).\n- selftests/bpf: Test invariants on JSLT crossing sign (git-fixes).\n- selftests/bpf: test refining u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- selftests: net: build net/lib dependency in all target (bsc#1262245).\n- selinux: don't reserve xattr slot when we won't fill it (stable-fixes).\n- selinux: prune /sys/fs/selinux/disable (stable-fixes).\n- selinux: shrink critical section in sel_write_load() (stable-fixes).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- Set CONFIG_INTEL_TSX_MODE to follow upstream AUTO default (bsc#1263044).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- soc: qcom: ocmem: make the core clock optional (git-fixes).\n- soc: qcom: ocmem: register reasons for probe deferrals (git-fixes).\n- soc: qcom: ocmem: return -EPROBE_DEFER is ocmem is not available (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- soundwire: debugfs: initialize firmware_file to empty string (git-fixes).\n- spi: aspeed-smc: fix controller deregistration (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: bcm63xx: fix controller deregistration (git-fixes).\n- spi: bcmbca-hsspi: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: cadence: fix unclocked access on unbind (git-fixes).\n- spi: ch341: fix memory leaks on probe failures (git-fixes).\n- spi: coldfire-qspi: fix controller deregistration (git-fixes).\n- spi: dln2: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-espi: fix controller deregistration (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: fsl: fix controller deregistration (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: img-spfi: fix controller deregistration (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: lantiq-ssc: fix controller deregistration (git-fixes).\n- spi: meson-spicc: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix use-after-free on registration failure (git-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: fix memory leak in probe (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: mxic: fix controller deregistration (git-fixes).\n- spi: mxs: fix controller deregistration (git-fixes).\n- spi: npcm-pspi: fix controller deregistration (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix controller deregistration (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: pic32-sqi: fix controller deregistration (git-fixes).\n- spi: pic32: fix controller deregistration (git-fixes).\n- spi: pl022: fix controller deregistration (git-fixes).\n- spi: qup: fix controller deregistration (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rockchip: Read ISR, not IMR, to detect cs-inactive IRQ (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix NULL-deref on driver unbind (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: st-ssc4: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun6i: fix controller deregistration (git-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: ti-qspi: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix use-after-free on unbind (git-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynq-qspi: fix controller deregistration (git-fixes).\n- spi: zynq-qspi: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tools/power/turbostat: Fix microcode patch level output for AMD/Hygon (git-fixes).\n- tools: hv: Fix cross-compilation (git-fixes).\n- tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public() (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: Fix auth session leak in tpm2_get_random() error path (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tpm: Use kfree_sensitive() to free auth session in tpm_dev_release() (git-fixes).\n- tty: serial: ip22zilog: Fix section mispatch warning (git-fixes).\n- udp: Force compute_score to always inline (bsc#1241259).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (git-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_hid: Add missing error code (git-fixes).\n- usb: gadget: f_hid: don't call cdev_init while cdev in use (git-fixes).\n- usb: gadget: f_hid: move list and spinlock inits from bind to alloc (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (git-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (git-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (git-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- vfio/pci: Lock upstream bridge for vfio_pci_core_disable() (git-fixes).\n- vfio/pds: Fix memory leak in pds_vfio_dirty_enable() (git-fixes).\n- vfio/pds: Fix missing detach_ioas op (git-fixes).\n- vfio/pds: replace bitmap_free with vfree (git-fixes).\n- vfio/type1: Fix error unwind in migration dirty bitmap allocation (git-fixes).\n- vfio: Fix unbalanced vfio_df_close call in no-iommu mode (git-fixes).\n- vfio: Prevent open_count decrement to negative (git-fixes).\n- virt: arm-cca-guest: fix error check for RSI_INCOMPLETE (git-fixes).\n- virt: sev-guest: Do not use host-controlled page order in cleanup path (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath10k: fix station lookup failure during disconnect (git-fixes).\n- wifi: ath11k: fix memory leaks in beacon template setup (git-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert \"Fix locking in error paths\" (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Place upper limit on station AID (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix AMPDU state handling in mt7925_tx_check_aggr (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7925: Fix incorrect MLO mode in firmware control (git-fixes).\n- wifi: mt76: mt7925: fix incorrect TLV length in CLC command (git-fixes).\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtl8xxxu: fix potential use of uninitialized value (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: Add additional USB IDs for RTL8812BU (bsc#1263135).\n- wifi: rtw88: Add BUFFALO WI-U3-866DHP to the USB ID list (bsc#1263135).\n- wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 (bsc#1263135).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw88: rtw8822bu VID/PID for BUFFALO WI-U2-866DM (bsc#1263135).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- x86/acpi/boot: Correct acpi_is_processor_usable() check again (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot/sev: Support memory acceptance in the EFI stub under SVSM (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Fix early boot failures on SEV-ES/SNP guests (git-fixes).\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges() (git-fixes).\n- x86/sev: Add missing RIP_REL_REF() invocations during sme_enable() (git-fixes).\n- x86/sev: Do not touch VMSA pages during SNP guest memory kdump (git-fixes).\n- x86/sev: Ensure SVSM reserved fields in a page validation entry are initialized to zero (git-fixes).\n- x86/sev: Fix operator precedence in GHCB_MSR_VMPL_REQ_LEVEL macro (git-fixes).\n- x86/sev: Improve handling of writes to intercepted TSC MSRs (git-fixes).\n- x86/sev: Make sure pages are not skipped during kdump (git-fixes).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951 bsc#1263044).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951 bsc#1263044).\n- x86/vmware: Parse MP tables for SEV-SNP enabled guests under VMware hypervisors (git-fixes).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n","status":"published","published":"2026-05-28T11:12:43Z","modified":"2026-07-09T18:24:07.906973973Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21841-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-2058: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2024-14027: xattr: switch to CLASS(fd) (bsc#1259420).\n- CVE-2025-40181: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (bsc#1253471).\n- CVE-2025-68265: nvme: fix admin request_queue lifetime (bsc#1255360).\n- CVE-2025-68310: s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump (bsc#1255160).\n- CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules (bsc#1264837).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: add xmit recursion limit to tunnel xmit functions (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23316: net: ipv4: fix ARM64 alignment fault in multipath hash seed (bsc#1260573).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23346: arm64: io: Rename ioremap_prot() to __ioremap_prot() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23375: mm: thp: deny THP for files on anonymous inodes (bsc#1260576).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23417: bpf: Fix constant blinding for PROBE_MEM32 stores (bsc#1261410).\n- CVE-2026-23436: net: add helpers for lookup and walking netdevs under netdev_lock() (bsc#1261617).\n- CVE-2026-23437: net: shaper: protect late read accesses to the hierarchy (bsc#1261635).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31392: smb: client: fix krb5 mount with username option (bsc#1261788).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31406: xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (bsc#1261629).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31435: netfs: Fix read abandonment during retry (bsc#1262601).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks (bsc#1262617).\n- CVE-2026-31456: mm/pagewalk: fix race between concurrent split and refault (bsc#1262627).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31503: udp: Fix wildcard bind conflict check when using hash2 (bsc#1263077).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31526: bpf: Fix exception exit lock checking for subprogs (bsc#1262662).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags (bsc#1263107).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit (bsc#1263074).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload() (bsc#1263048).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31658: net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() (bsc#1263052).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() (bsc#1263138).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31691: igb: remove napi_synchronize() in igb_down() (bsc#1263604).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43045: mshv: Refactor and rename memory region handling functions (bsc#1263942).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43082: net: txgbe: leave space for null terminators on property_entry (bsc#1264233).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43153: xfs: remove xfs_attr_leaf_hasname (bsc#1264586).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ACPI: video: Move Lenovo Legion S7 15ACH6 quirk to the right section (git-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/hdmi: Add quirk for TUXEDO IBS14G6 (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (stable-fixes).\n- ALSA: pcmtest: fix reference leak on failed device registration (git-fixes).\n- ALSA: pcmtest: Fix resource leaks in module init error paths (git-fixes).\n- ALSA: pcmtest: Return -EFAULT on pattern read copy failure (git-fixes).\n- ALSA: sc6000: Keep the programmed board state in card-private data (git-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- ALSA: virtio: drop an extaneous kernel-doc comment (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for \"VAD Detected\" (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- backlight: sky81452-backlight: Check return value of devm_gpiod_get_optional() in sky81452_bl_parse_dt() (git-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- bitfield: Add FIELD_MODIFY() helper (jsc#PED-14238).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (bsc#1260996).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: fix memset typo (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- bpf: Add third round of bounds deduction (git-fixes).\n- bpf: Fix u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- bpf: Improve bounds when s64 crosses sign boundary (git-fixes).\n- bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI (git-fixes).\n- btrfs: qgroup: update all parent qgroups when doing quick inherit (bsc#1258933).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays (git-fixes).\n- bus: rifsc: fix RIF configuration check for peripherals (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from \"scaling factor\" list (bsc#1249104).\n- crypto: af_alg - limit RX SG extraction by receive buffer budget (git-fixes).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix error codes in OTP reads (git-fixes).\n- crypto: atmel-sha204a - Fix OTP sysfs read and error handling (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-sha204a - Fix uninitialized data access on OTP read error (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: drivers - Switch back to struct platform_driver::remove() (jsc#PED-14238).\n- crypto: drivers - Use str_enable_disable-like helpers (jsc#PED-14238).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: iaa - Adjust workqueue allocation type (jsc#PED-14238).\n- crypto: iaa - fix per-node CPU counter reset in rebalance_wq_table() (git-fixes).\n- crypto: iaa - Move compression CRC into request object (jsc#PED-14238).\n- crypto: iaa - Optimize rebalance_wq_table() (jsc#PED-14238).\n- crypto: iaa - Remove potential infinite loop in check_completion() (jsc#PED-14238).\n- crypto: iaa - Remove unreachable pr_debug from iaa_crypto_cleanup_module (jsc#PED-14238).\n- crypto: iaa - Remove unused disable_async argument from iaa_decompress (jsc#PED-14238).\n- crypto: iaa - Replace sprintf with sysfs_emit in sysfs show functions (jsc#PED-14238).\n- crypto: iaa - Simplify init_iaa_device() (jsc#PED-14238).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: nx - Fix packed layout in struct nx842_crypto_header (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - #undef field_get() before local definition (jsc#PED-14238).\n- crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting (jsc#PED-14238).\n- crypto: qat - add bank state save and restore for qat_420xx (jsc#PED-14238).\n- crypto: qat - add command queue telemetry counters for GEN6 (jsc#PED-14238).\n- crypto: qat - add compression slice count for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service to telemetry (jsc#PED-14238).\n- crypto: qat - add firmware headers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add GEN6 firmware loader (jsc#PED-14238).\n- crypto: qat - add get_svc_slice_cnt() in device data structure (jsc#PED-14238).\n- crypto: qat - add live migration enablers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add macro to write 64-bit values to registers (jsc#PED-14238).\n- crypto: qat - add missing header inclusion (jsc#PED-14238).\n- crypto: qat - add qat_6xxx driver (jsc#PED-14238).\n- crypto: qat - add ring buffer idle telemetry counter for GEN6 (jsc#PED-14238).\n- crypto: qat - add support for decompression service to GEN6 devices (jsc#PED-14238).\n- crypto: qat - consolidate service enums (jsc#PED-14238).\n- crypto: qat - Constify struct pm_status_row (jsc#PED-14238).\n- crypto: qat - disable 4xxx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - disable 420xx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - do not export adf_cfg_services (jsc#PED-14238).\n- crypto: qat - enable power management debugfs for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable RAS support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable rate limiting feature for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable reporting of error counters for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable telemetry for GEN6 devices (jsc#PED-14238).\n- crypto: qat - export adf_get_service_mask() (jsc#PED-14238).\n- crypto: qat - export adf_init_admin_pm() (jsc#PED-14238).\n- crypto: qat - expose configuration functions (jsc#PED-14238).\n- crypto: qat - fix compression instance leak (git-fixes).\n- crypto: qat - fix IRQ cleanup on 6xxx probe failure (git-fixes).\n- crypto: qat - fix object goals in Makefiles (jsc#PED-14238.\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - Fix typo \"accelaration\" (jsc#PED-14238).\n- crypto: qat - fix virtual channel configuration for GEN6 devices (jsc#PED-14238).\n- crypto: qat - include qat_common in top Makefile (jsc#PED-14238).\n- crypto: qat - introduce fuse array (jsc#PED-14238).\n- crypto: qat - make adf_dev_autoreset() static (jsc#PED-14238).\n- crypto: qat - optimize allocations for fw authentication (jsc#PED-14238).\n- crypto: qat - refactor compression template logic (jsc#PED-14238).\n- crypto: qat - refactor FW signing algorithm (jsc#PED-14238).\n- crypto: qat - refactor ring-related debug functions (jsc#PED-14238).\n- crypto: qat - refactor service parsing logic (jsc#PED-14238).\n- crypto: qat - relocate and rename bank state structure definition (jsc#PED-14238).\n- crypto: qat - relocate bank state helper functions (jsc#PED-14238).\n- crypto: qat - relocate power management debugfs helper APIs (jsc#PED-14238).\n- crypto: qat - relocate service related functions (jsc#PED-14238).\n- crypto: qat - remove BITS_IN_DWORD() (jsc#PED-14238).\n- crypto: qat - Remove dst_null support (jsc#PED-14238).\n- crypto: qat - remove duplicate masking for GEN6 devices (jsc#PED-14238).\n- crypto: qat - remove initialization in device class (jsc#PED-14238).\n- crypto: qat - remove redundant FW image size check (jsc#PED-14238).\n- crypto: qat - remove unused adf_devmgr_get_first (jsc#PED-14238).\n- crypto: qat - remove unused members in suof structure (jsc#PED-14238).\n- crypto: qat - rename and relocate timer logic (jsc#PED-14238).\n- crypto: qat - reorder objects in qat_common Makefile (jsc#PED-14238).\n- crypto: qat - replace CHECK_STAT macro with static inline function (jsc#PED-14238).\n- crypto: qat - Replace kzalloc() + copy_from_user() with memdup_user() (jsc#PED-14238).\n- crypto: qat - restore ASYM service support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - Return pointer directly in adf_ctl_alloc_resources (jsc#PED-14238).\n- crypto: qat - set command ids as reserved (jsc#PED-14238).\n- crypto: qat - switch to standard pattern for PCI IDs (jsc#PED-14238).\n- crypto: qat - update firmware api (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in adf_gen4_hw_data.c (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in qat uclo.c (jsc#PED-14238).\n- crypto: qat - use simple_strtoull to improve qat_uclo_parse_num (jsc#PED-14238).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: qat - validate service in rate limiting sysfs api (jsc#PED-14238).\n- crypto: qat/qat_6xxx - Fix NULL vs IS_ERR() check in adf_probe() (jsc#PED-14238).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: tegra - Disable softirqs before finalizing request (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dmaengine: dw-axi-dmac: fix Alignment should match open parenthesis (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drivers/base/memory: fix memory block reference leak in poison accounting (git-fixes).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- erofs: add GFP_NOIO in the bio completion if needed (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: Fixed sysfs duplicate filename issue (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: arm_ffa: Use the correct buffer size during RXTX_MAP (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- firmware: google: framebuffer: Do not mark framebuffer as busy (git-fixes).\n- firmware: google: framebuffer: Do not unregister platform device (git-fixes).\n- gpio: of: clear OF_POPULATED on hog nodes in remove path (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: amd_sfh: don't log error when device discovery fails with -EOPNOTSUPP (git-fixes).\n- HID: apple: ensure the keyboard backlight is off if suspending (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: logitech-hidpp: Enable MX Master 4 over bluetooth (stable-fixes).\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hisi_acc_vfio_pci: add eq and aeq interruption restore (git-fixes).\n- hisi_acc_vfio_pci: bugfix cache write-back issue (git-fixes).\n- hisi_acc_vfio_pci: bugfix the problem of uninstalling driver (git-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hv_sock: update outdated comment for renamed vsock_stream_recvmsg() (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- hwmon: (ltc4286) Add missing MODULE_IMPORT_NS(\"PMBUS\") (git-fixes).\n- hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt (git-fixes).\n- hwmon: (powerz) Fix use-after-free on USB disconnect (git-fixes).\n- hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i2c: tegra: Add HS mode support (bsc#1261550).\n- i2c: tegra: Add Tegra256 support (bsc#1261550).\n- i2c: tegra: Do not configure DMA if not supported (bsc#1261550).\n- i2c: tegra: Don't mark devices with pins as IRQ safe (stable-fixes).\n- i2c: tegra: Update Tegra256 timing parameters (bsc#1261550).\n- i2c: tegra: Use separate variables for fast and fastplus (bsc#1261550).\n- i3c: dw: Fix memory leak in dw_i3c_master_i3c_xfers() (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- iio: adc: ad7192: Revert \"properly check spi_get_device_match_data()\" (stable-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- iio: frequency: admv1013: add dev variable (stable-fixes).\n- iio: frequency: admv1013: fix NULL pointer dereference on str (git-fixes).\n- Input: bcm5974 - recover from failed mode switch (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request \"event\" (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- interconnect: debugfs: fix devm_kstrdup and kfree mismatch (git-fixes).\n- io_uring/timeout: check unused sqe fields (git-fixes).\n- iommu/amd: move wait_on_sem() out of spinlock (git-fixes bsc#1260593).\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations (git-fixes bsc#1260593).\n- iommu/vt-d: Remove LPIG from page group response descriptor (jsc#PED-16113).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- ipv6: rpl: reserve mac_len headroom when recompressed SRH grows (git-fixes).\n- KVM: arm64: Allow cacheable stage 2 mapping using VMA flags (git-fixes).\n- KVM: arm64: Assume non-PFNMAP/MIXEDMAP VMAs can be mapped cacheable (git-fixes).\n- KVM: arm64: Block cacheable PFNMAP mapping (git-fixes).\n- KVM: arm64: Consolidate idreg callbacks (git-fixes).\n- KVM: arm64: Discard PC update state on vcpu reset (git-fixes).\n- KVM: arm64: Finalize ID registers only once per VM (git-fixes).\n- KVM: arm64: Fix MTE flag initialization for protected VMs (git-fixes).\n- KVM: arm64: Fix page leak in user_mem_abort() (git-fixes).\n- KVM: arm64: Fix Trace Buffer trap polarity for protected VMs (git-fixes).\n- KVM: arm64: Fix Trace Buffer trapping for protected VMs (git-fixes).\n- KVM: arm64: Fix vma_shift staleness on nested hwpoison path (git-fixes).\n- KVM: arm64: Hide S1POE from guests when not supported by the host (git-fixes).\n- KVM: arm64: Limit clearing of ID_{AA64PFR0,PFR1}_EL1.GIC to userspace irqchip (git-fixes).\n- KVM: arm64: Make all 32bit ID registers fully writable (git-fixes).\n- KVM: arm64: nv: Add trap config for DBGWCR\u003c15\u003e_EL1 (git-fixes).\n- KVM: arm64: nv: Return correct RES0 bits for FGT registers (git-fixes).\n- KVM: arm64: pkvm: Fallback to level-3 mapping on host stage-2 fault (git-fixes).\n- KVM: arm64: Read PMUVer as unsigned (git-fixes).\n- KVM: arm64: Rename the device variable to s2_force_noncacheable (git-fixes).\n- KVM: arm64: Return early from trace helpers when KVM isn't available (git-fixes).\n- KVM: arm64: Set ID_{AA64PFR0,PFR1}_EL1.GIC when GICv3 is configured (git-fixes).\n- KVM: arm64: vgic-v3: Release reserved slot outside of lpi_xa's lock (git-fixes).\n- KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).\n- KVM: nSVM: Use vcpu-\u003earch.cr2 when updating vmcb12 on nested #VMEXIT (git-fixes).\n- KVM: nVMX: Add consistency check for TSC_MULTIPLIER=0 (git-fixes).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created (git-fixes).\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (git-fixes).\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish (git-fixes).\n- KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock (git-fixes).\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU (git-fixes).\n- KVM: SVM: Disallow EFER.LMSLE when not supported by hardware (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Properly check RAX in the emulator for SVM instructions (git-fixes).\n- KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated (git-fixes).\n- KVM: TDX: Explicitly set user-return MSRs that *may* be clobbered by the TDX-Module (git-fixes).\n- KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter (git-fixes).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (git-fixes).\n- KVM: x86: Advertise EferLmsleUnsupported to userspace (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: X86: Fix array_index_nospec protection in __pv_send_ipi (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx283: Enter full standby when stopping streaming (git-fixes).\n- media: i2c: imx283: Fix hang when going from large to small resolution (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: core: Preserve OF node when ACPI handle is present (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net-shapers: don't free reply skb after genlmsg_reply() (git-fixes).\n- net/mlx5: Fix HCA caps leak on notifier init failure (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of \"old\" filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: Move current_speed debugfs file to mana_init_port() (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: broadcom: Save PHY counters during suspend (git-fixes).\n- net: phy: DP83TC811: add reading of abilities (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: phy: fix a return path in get_phy_c45_ids() (git-fixes).\n- net: phy: qcom: at803x: Use the correct bit to disable extended next page (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-apple: drop invalid put of admin queue reference count (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4 (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix admin queue leak on controller reset (git-fixes).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- openvswitch: vport: fix self-deadlock on release of tunnel ports (git-fixes).\n- panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() (bsc#1261149).\n- panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() (bsc#1261149).\n- panic: introduce helper functions for panic state (bsc#1261149).\n- panic: use angle-bracket include for panic.h (bsc#1261149).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI/ASPM: Fix pci_clear_and_set_config_dword() usage (git-fixes).\n- PCI/NPEM: Set LED_HW_PLUGGABLE for hotplug-capable ports (git-fixes).\n- PCI/TPH: Allow TPH enable for RCiEPs (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: dwc: rcar-gen4: Change EPC BAR alignment to 4K as per the documentation (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup (git-fixes).\n- PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (bsc#1261648).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Free up Endpoint resources during remove() (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse \"nvidia,refclk-select\" (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- pinctrl: realtek: Fix function signature for config argument (git-fixes).\n- pinctrl: renesas: rzg2l: Fix save/restore of {IOLH,IEN,PUPD,SMT} registers (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86: asus-wmi: adjust screenpad power/brightness handling (git-fixes).\n- platform/x86: asus-wmi: fix screenpad brightness range (git-fixes).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- printk/nbcon/panic: Allow printk kthread to sleep when the system is in panic (bsc#1261149).\n- printk/nbcon: Block printk kthreads when any CPU is in an emergency context (bsc#1261149).\n- printk/nbcon: Release nbcon consoles ownership in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: Restore IRQ in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: use panic_on_this_cpu() helper (bsc#1261149).\n- printk: Allow printk_trigger_flush() to flush all types (bsc#1262750).\n- printk: Allow to use the printk kthread immediately even for 1st nbcon (jsc#PED-7912).\n- printk: Avoid irq_work for printk_deferred() on suspend (bsc#1262750).\n- printk: Avoid scheduling irq_work on suspend (bsc#1262750).\n- printk: console_flush_one_record() code cleanup (bsc#1261149).\n- printk: Introduce console_flush_one_record (bsc#1261149).\n- printk: Use console_flush_one_record for legacy printer kthread (bsc#1261149).\n- pwm: imx-tpm: Count the number of enabled channels in probe (git-fixes).\n- qat: don't mess with -\u003ed_name (jsc#PED-14238).\n- r8152: fix incorrect register write to USB_UPHY_XTAL (git-fixes).\n- RDMA/irdma: Fix double free related to rereg_user_mr (git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- regulator: rk808: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Fix sram property parsing (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert \"ALSA: usb: Increase volume range that triggers a warning\" (git-fixes).\n- Revert \"serial: 8250: Revert \"drop lockdep annotation from serial8250_clear_IER()\"\" (bsc#1262480).\n- Revert \"serial: 8250: Switch to nbcon console\" (bsc#1262480).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259994).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259994).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259994).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: lpfc: Use the crc32c() function (bsc#1262019).\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues (git-fixes).\n- scsi: ses: Fix devices attaching to different hosts (git-fixes).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- scsi: ufs: ufs-pci: Add support for Intel Wildcat Lake (jsc#PED-13771).\n- selftests/bpf: Test cross-sign 64bits range refinement (git-fixes).\n- selftests/bpf: Test invariants on JSLT crossing sign (git-fixes).\n- selftests/bpf: test refining u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- selftests: net: build net/lib dependency in all target (bsc#1262245).\n- selinux: don't reserve xattr slot when we won't fill it (stable-fixes).\n- selinux: prune /sys/fs/selinux/disable (stable-fixes).\n- selinux: shrink critical section in sel_write_load() (stable-fixes).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- Set CONFIG_INTEL_TSX_MODE to follow upstream AUTO default (bsc#1263044).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- soc: qcom: ocmem: make the core clock optional (git-fixes).\n- soc: qcom: ocmem: register reasons for probe deferrals (git-fixes).\n- soc: qcom: ocmem: return -EPROBE_DEFER is ocmem is not available (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- soundwire: debugfs: initialize firmware_file to empty string (git-fixes).\n- spi: aspeed-smc: fix controller deregistration (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: bcm63xx: fix controller deregistration (git-fixes).\n- spi: bcmbca-hsspi: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: cadence: fix unclocked access on unbind (git-fixes).\n- spi: ch341: fix memory leaks on probe failures (git-fixes).\n- spi: coldfire-qspi: fix controller deregistration (git-fixes).\n- spi: dln2: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-espi: fix controller deregistration (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: fsl: fix controller deregistration (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: img-spfi: fix controller deregistration (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: lantiq-ssc: fix controller deregistration (git-fixes).\n- spi: meson-spicc: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix use-after-free on registration failure (git-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: fix memory leak in probe (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: mxic: fix controller deregistration (git-fixes).\n- spi: mxs: fix controller deregistration (git-fixes).\n- spi: npcm-pspi: fix controller deregistration (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix controller deregistration (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: pic32-sqi: fix controller deregistration (git-fixes).\n- spi: pic32: fix controller deregistration (git-fixes).\n- spi: pl022: fix controller deregistration (git-fixes).\n- spi: qup: fix controller deregistration (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rockchip: Read ISR, not IMR, to detect cs-inactive IRQ (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix NULL-deref on driver unbind (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: st-ssc4: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun6i: fix controller deregistration (git-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: ti-qspi: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix use-after-free on unbind (git-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynq-qspi: fix controller deregistration (git-fixes).\n- spi: zynq-qspi: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tools/power/turbostat: Fix microcode patch level output for AMD/Hygon (git-fixes).\n- tools: hv: Fix cross-compilation (git-fixes).\n- tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public() (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: Fix auth session leak in tpm2_get_random() error path (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tpm: Use kfree_sensitive() to free auth session in tpm_dev_release() (git-fixes).\n- tty: serial: ip22zilog: Fix section mispatch warning (git-fixes).\n- udp: Force compute_score to always inline (bsc#1241259).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (git-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_hid: Add missing error code (git-fixes).\n- usb: gadget: f_hid: don't call cdev_init while cdev in use (git-fixes).\n- usb: gadget: f_hid: move list and spinlock inits from bind to alloc (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (git-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (git-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (git-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- vfio/pci: Lock upstream bridge for vfio_pci_core_disable() (git-fixes).\n- vfio/pds: Fix memory leak in pds_vfio_dirty_enable() (git-fixes).\n- vfio/pds: Fix missing detach_ioas op (git-fixes).\n- vfio/pds: replace bitmap_free with vfree (git-fixes).\n- vfio/type1: Fix error unwind in migration dirty bitmap allocation (git-fixes).\n- vfio: Fix unbalanced vfio_df_close call in no-iommu mode (git-fixes).\n- vfio: Prevent open_count decrement to negative (git-fixes).\n- virt: arm-cca-guest: fix error check for RSI_INCOMPLETE (git-fixes).\n- virt: sev-guest: Do not use host-controlled page order in cleanup path (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath10k: fix station lookup failure during disconnect (git-fixes).\n- wifi: ath11k: fix memory leaks in beacon template setup (git-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert \"Fix locking in error paths\" (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Place upper limit on station AID (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix AMPDU state handling in mt7925_tx_check_aggr (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7925: Fix incorrect MLO mode in firmware control (git-fixes).\n- wifi: mt76: mt7925: fix incorrect TLV length in CLC command (git-fixes).\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtl8xxxu: fix potential use of uninitialized value (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: Add additional USB IDs for RTL8812BU (bsc#1263135).\n- wifi: rtw88: Add BUFFALO WI-U3-866DHP to the USB ID list (bsc#1263135).\n- wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 (bsc#1263135).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw88: rtw8822bu VID/PID for BUFFALO WI-U2-866DM (bsc#1263135).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- x86/acpi/boot: Correct acpi_is_processor_usable() check again (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot/sev: Support memory acceptance in the EFI stub under SVSM (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Fix early boot failures on SEV-ES/SNP guests (git-fixes).\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges() (git-fixes).\n- x86/sev: Add missing RIP_REL_REF() invocations during sme_enable() (git-fixes).\n- x86/sev: Do not touch VMSA pages during SNP guest memory kdump (git-fixes).\n- x86/sev: Ensure SVSM reserved fields in a page validation entry are initialized to zero (git-fixes).\n- x86/sev: Fix operator precedence in GHCB_MSR_VMPL_REQ_LEVEL macro (git-fixes).\n- x86/sev: Improve handling of writes to intercepted TSC MSRs (git-fixes).\n- x86/sev: Make sure pages are not skipped during kdump (git-fixes).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951 bsc#1263044).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951 bsc#1263044).\n- x86/vmware: Parse MP tables for SEV-SNP enabled guests under VMware hypervisors (git-fixes).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n","status":"published","published":"2026-05-28T11:40:20Z","modified":"2026-05-31T18:24:29.197819689Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21845-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-2058: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2024-14027: xattr: switch to CLASS(fd) (bsc#1259420).\n- CVE-2025-40181: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (bsc#1253471).\n- CVE-2025-68265: nvme: fix admin request_queue lifetime (bsc#1255360).\n- CVE-2025-68310: s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump (bsc#1255160).\n- CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules (bsc#1264837).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: add xmit recursion limit to tunnel xmit functions (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23316: net: ipv4: fix ARM64 alignment fault in multipath hash seed (bsc#1260573).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23346: arm64: io: Rename ioremap_prot() to __ioremap_prot() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23375: mm: thp: deny THP for files on anonymous inodes (bsc#1260576).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23417: bpf: Fix constant blinding for PROBE_MEM32 stores (bsc#1261410).\n- CVE-2026-23436: net: add helpers for lookup and walking netdevs under netdev_lock() (bsc#1261617).\n- CVE-2026-23437: net: shaper: protect late read accesses to the hierarchy (bsc#1261635).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31392: smb: client: fix krb5 mount with username option (bsc#1261788).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31406: xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (bsc#1261629).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31435: netfs: Fix read abandonment during retry (bsc#1262601).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks (bsc#1262617).\n- CVE-2026-31456: mm/pagewalk: fix race between concurrent split and refault (bsc#1262627).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31503: udp: Fix wildcard bind conflict check when using hash2 (bsc#1263077).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31526: bpf: Fix exception exit lock checking for subprogs (bsc#1262662).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags (bsc#1263107).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit (bsc#1263074).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload() (bsc#1263048).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31658: net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() (bsc#1263052).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() (bsc#1263138).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31691: igb: remove napi_synchronize() in igb_down() (bsc#1263604).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43045: mshv: Refactor and rename memory region handling functions (bsc#1263942).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43082: net: txgbe: leave space for null terminators on property_entry (bsc#1264233).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43153: xfs: remove xfs_attr_leaf_hasname (bsc#1264586).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ACPI: video: Move Lenovo Legion S7 15ACH6 quirk to the right section (git-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/hdmi: Add quirk for TUXEDO IBS14G6 (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (stable-fixes).\n- ALSA: pcmtest: fix reference leak on failed device registration (git-fixes).\n- ALSA: pcmtest: Fix resource leaks in module init error paths (git-fixes).\n- ALSA: pcmtest: Return -EFAULT on pattern read copy failure (git-fixes).\n- ALSA: sc6000: Keep the programmed board state in card-private data (git-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- ALSA: virtio: drop an extaneous kernel-doc comment (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for \"VAD Detected\" (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- backlight: sky81452-backlight: Check return value of devm_gpiod_get_optional() in sky81452_bl_parse_dt() (git-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- bitfield: Add FIELD_MODIFY() helper (jsc#PED-14238).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (bsc#1260996).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: fix memset typo (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- bpf: Add third round of bounds deduction (git-fixes).\n- bpf: Fix u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- bpf: Improve bounds when s64 crosses sign boundary (git-fixes).\n- bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI (git-fixes).\n- btrfs: qgroup: update all parent qgroups when doing quick inherit (bsc#1258933).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays (git-fixes).\n- bus: rifsc: fix RIF configuration check for peripherals (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from \"scaling factor\" list (bsc#1249104).\n- crypto: af_alg - limit RX SG extraction by receive buffer budget (git-fixes).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix error codes in OTP reads (git-fixes).\n- crypto: atmel-sha204a - Fix OTP sysfs read and error handling (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-sha204a - Fix uninitialized data access on OTP read error (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: drivers - Switch back to struct platform_driver::remove() (jsc#PED-14238).\n- crypto: drivers - Use str_enable_disable-like helpers (jsc#PED-14238).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: iaa - Adjust workqueue allocation type (jsc#PED-14238).\n- crypto: iaa - fix per-node CPU counter reset in rebalance_wq_table() (git-fixes).\n- crypto: iaa - Move compression CRC into request object (jsc#PED-14238).\n- crypto: iaa - Optimize rebalance_wq_table() (jsc#PED-14238).\n- crypto: iaa - Remove potential infinite loop in check_completion() (jsc#PED-14238).\n- crypto: iaa - Remove unreachable pr_debug from iaa_crypto_cleanup_module (jsc#PED-14238).\n- crypto: iaa - Remove unused disable_async argument from iaa_decompress (jsc#PED-14238).\n- crypto: iaa - Replace sprintf with sysfs_emit in sysfs show functions (jsc#PED-14238).\n- crypto: iaa - Simplify init_iaa_device() (jsc#PED-14238).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: nx - Fix packed layout in struct nx842_crypto_header (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - #undef field_get() before local definition (jsc#PED-14238).\n- crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting (jsc#PED-14238).\n- crypto: qat - add bank state save and restore for qat_420xx (jsc#PED-14238).\n- crypto: qat - add command queue telemetry counters for GEN6 (jsc#PED-14238).\n- crypto: qat - add compression slice count for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service to telemetry (jsc#PED-14238).\n- crypto: qat - add firmware headers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add GEN6 firmware loader (jsc#PED-14238).\n- crypto: qat - add get_svc_slice_cnt() in device data structure (jsc#PED-14238).\n- crypto: qat - add live migration enablers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add macro to write 64-bit values to registers (jsc#PED-14238).\n- crypto: qat - add missing header inclusion (jsc#PED-14238).\n- crypto: qat - add qat_6xxx driver (jsc#PED-14238).\n- crypto: qat - add ring buffer idle telemetry counter for GEN6 (jsc#PED-14238).\n- crypto: qat - add support for decompression service to GEN6 devices (jsc#PED-14238).\n- crypto: qat - consolidate service enums (jsc#PED-14238).\n- crypto: qat - Constify struct pm_status_row (jsc#PED-14238).\n- crypto: qat - disable 4xxx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - disable 420xx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - do not export adf_cfg_services (jsc#PED-14238).\n- crypto: qat - enable power management debugfs for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable RAS support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable rate limiting feature for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable reporting of error counters for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable telemetry for GEN6 devices (jsc#PED-14238).\n- crypto: qat - export adf_get_service_mask() (jsc#PED-14238).\n- crypto: qat - export adf_init_admin_pm() (jsc#PED-14238).\n- crypto: qat - expose configuration functions (jsc#PED-14238).\n- crypto: qat - fix compression instance leak (git-fixes).\n- crypto: qat - fix IRQ cleanup on 6xxx probe failure (git-fixes).\n- crypto: qat - fix object goals in Makefiles (jsc#PED-14238.\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - Fix typo \"accelaration\" (jsc#PED-14238).\n- crypto: qat - fix virtual channel configuration for GEN6 devices (jsc#PED-14238).\n- crypto: qat - include qat_common in top Makefile (jsc#PED-14238).\n- crypto: qat - introduce fuse array (jsc#PED-14238).\n- crypto: qat - make adf_dev_autoreset() static (jsc#PED-14238).\n- crypto: qat - optimize allocations for fw authentication (jsc#PED-14238).\n- crypto: qat - refactor compression template logic (jsc#PED-14238).\n- crypto: qat - refactor FW signing algorithm (jsc#PED-14238).\n- crypto: qat - refactor ring-related debug functions (jsc#PED-14238).\n- crypto: qat - refactor service parsing logic (jsc#PED-14238).\n- crypto: qat - relocate and rename bank state structure definition (jsc#PED-14238).\n- crypto: qat - relocate bank state helper functions (jsc#PED-14238).\n- crypto: qat - relocate power management debugfs helper APIs (jsc#PED-14238).\n- crypto: qat - relocate service related functions (jsc#PED-14238).\n- crypto: qat - remove BITS_IN_DWORD() (jsc#PED-14238).\n- crypto: qat - Remove dst_null support (jsc#PED-14238).\n- crypto: qat - remove duplicate masking for GEN6 devices (jsc#PED-14238).\n- crypto: qat - remove initialization in device class (jsc#PED-14238).\n- crypto: qat - remove redundant FW image size check (jsc#PED-14238).\n- crypto: qat - remove unused adf_devmgr_get_first (jsc#PED-14238).\n- crypto: qat - remove unused members in suof structure (jsc#PED-14238).\n- crypto: qat - rename and relocate timer logic (jsc#PED-14238).\n- crypto: qat - reorder objects in qat_common Makefile (jsc#PED-14238).\n- crypto: qat - replace CHECK_STAT macro with static inline function (jsc#PED-14238).\n- crypto: qat - Replace kzalloc() + copy_from_user() with memdup_user() (jsc#PED-14238).\n- crypto: qat - restore ASYM service support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - Return pointer directly in adf_ctl_alloc_resources (jsc#PED-14238).\n- crypto: qat - set command ids as reserved (jsc#PED-14238).\n- crypto: qat - switch to standard pattern for PCI IDs (jsc#PED-14238).\n- crypto: qat - update firmware api (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in adf_gen4_hw_data.c (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in qat uclo.c (jsc#PED-14238).\n- crypto: qat - use simple_strtoull to improve qat_uclo_parse_num (jsc#PED-14238).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: qat - validate service in rate limiting sysfs api (jsc#PED-14238).\n- crypto: qat/qat_6xxx - Fix NULL vs IS_ERR() check in adf_probe() (jsc#PED-14238).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: tegra - Disable softirqs before finalizing request (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dmaengine: dw-axi-dmac: fix Alignment should match open parenthesis (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drivers/base/memory: fix memory block reference leak in poison accounting (git-fixes).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- erofs: add GFP_NOIO in the bio completion if needed (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: Fixed sysfs duplicate filename issue (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: arm_ffa: Use the correct buffer size during RXTX_MAP (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- firmware: google: framebuffer: Do not mark framebuffer as busy (git-fixes).\n- firmware: google: framebuffer: Do not unregister platform device (git-fixes).\n- gpio: of: clear OF_POPULATED on hog nodes in remove path (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: amd_sfh: don't log error when device discovery fails with -EOPNOTSUPP (git-fixes).\n- HID: apple: ensure the keyboard backlight is off if suspending (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: logitech-hidpp: Enable MX Master 4 over bluetooth (stable-fixes).\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hisi_acc_vfio_pci: add eq and aeq interruption restore (git-fixes).\n- hisi_acc_vfio_pci: bugfix cache write-back issue (git-fixes).\n- hisi_acc_vfio_pci: bugfix the problem of uninstalling driver (git-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hv_sock: update outdated comment for renamed vsock_stream_recvmsg() (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- hwmon: (ltc4286) Add missing MODULE_IMPORT_NS(\"PMBUS\") (git-fixes).\n- hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt (git-fixes).\n- hwmon: (powerz) Fix use-after-free on USB disconnect (git-fixes).\n- hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i2c: tegra: Add HS mode support (bsc#1261550).\n- i2c: tegra: Add Tegra256 support (bsc#1261550).\n- i2c: tegra: Do not configure DMA if not supported (bsc#1261550).\n- i2c: tegra: Don't mark devices with pins as IRQ safe (stable-fixes).\n- i2c: tegra: Update Tegra256 timing parameters (bsc#1261550).\n- i2c: tegra: Use separate variables for fast and fastplus (bsc#1261550).\n- i3c: dw: Fix memory leak in dw_i3c_master_i3c_xfers() (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- iio: adc: ad7192: Revert \"properly check spi_get_device_match_data()\" (stable-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- iio: frequency: admv1013: add dev variable (stable-fixes).\n- iio: frequency: admv1013: fix NULL pointer dereference on str (git-fixes).\n- Input: bcm5974 - recover from failed mode switch (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request \"event\" (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- interconnect: debugfs: fix devm_kstrdup and kfree mismatch (git-fixes).\n- io_uring/timeout: check unused sqe fields (git-fixes).\n- iommu/amd: move wait_on_sem() out of spinlock (git-fixes bsc#1260593).\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations (git-fixes bsc#1260593).\n- iommu/vt-d: Remove LPIG from page group response descriptor (jsc#PED-16113).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- ipv6: rpl: reserve mac_len headroom when recompressed SRH grows (git-fixes).\n- KVM: arm64: Allow cacheable stage 2 mapping using VMA flags (git-fixes).\n- KVM: arm64: Assume non-PFNMAP/MIXEDMAP VMAs can be mapped cacheable (git-fixes).\n- KVM: arm64: Block cacheable PFNMAP mapping (git-fixes).\n- KVM: arm64: Consolidate idreg callbacks (git-fixes).\n- KVM: arm64: Discard PC update state on vcpu reset (git-fixes).\n- KVM: arm64: Finalize ID registers only once per VM (git-fixes).\n- KVM: arm64: Fix MTE flag initialization for protected VMs (git-fixes).\n- KVM: arm64: Fix page leak in user_mem_abort() (git-fixes).\n- KVM: arm64: Fix Trace Buffer trap polarity for protected VMs (git-fixes).\n- KVM: arm64: Fix Trace Buffer trapping for protected VMs (git-fixes).\n- KVM: arm64: Fix vma_shift staleness on nested hwpoison path (git-fixes).\n- KVM: arm64: Hide S1POE from guests when not supported by the host (git-fixes).\n- KVM: arm64: Limit clearing of ID_{AA64PFR0,PFR1}_EL1.GIC to userspace irqchip (git-fixes).\n- KVM: arm64: Make all 32bit ID registers fully writable (git-fixes).\n- KVM: arm64: nv: Add trap config for DBGWCR\u003c15\u003e_EL1 (git-fixes).\n- KVM: arm64: nv: Return correct RES0 bits for FGT registers (git-fixes).\n- KVM: arm64: pkvm: Fallback to level-3 mapping on host stage-2 fault (git-fixes).\n- KVM: arm64: Read PMUVer as unsigned (git-fixes).\n- KVM: arm64: Rename the device variable to s2_force_noncacheable (git-fixes).\n- KVM: arm64: Return early from trace helpers when KVM isn't available (git-fixes).\n- KVM: arm64: Set ID_{AA64PFR0,PFR1}_EL1.GIC when GICv3 is configured (git-fixes).\n- KVM: arm64: vgic-v3: Release reserved slot outside of lpi_xa's lock (git-fixes).\n- KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).\n- KVM: nSVM: Use vcpu-\u003earch.cr2 when updating vmcb12 on nested #VMEXIT (git-fixes).\n- KVM: nVMX: Add consistency check for TSC_MULTIPLIER=0 (git-fixes).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created (git-fixes).\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (git-fixes).\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish (git-fixes).\n- KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock (git-fixes).\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU (git-fixes).\n- KVM: SVM: Disallow EFER.LMSLE when not supported by hardware (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Properly check RAX in the emulator for SVM instructions (git-fixes).\n- KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated (git-fixes).\n- KVM: TDX: Explicitly set user-return MSRs that *may* be clobbered by the TDX-Module (git-fixes).\n- KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter (git-fixes).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (git-fixes).\n- KVM: x86: Advertise EferLmsleUnsupported to userspace (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: X86: Fix array_index_nospec protection in __pv_send_ipi (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx283: Enter full standby when stopping streaming (git-fixes).\n- media: i2c: imx283: Fix hang when going from large to small resolution (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: core: Preserve OF node when ACPI handle is present (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net-shapers: don't free reply skb after genlmsg_reply() (git-fixes).\n- net/mlx5: Fix HCA caps leak on notifier init failure (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of \"old\" filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: Move current_speed debugfs file to mana_init_port() (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: broadcom: Save PHY counters during suspend (git-fixes).\n- net: phy: DP83TC811: add reading of abilities (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: phy: fix a return path in get_phy_c45_ids() (git-fixes).\n- net: phy: qcom: at803x: Use the correct bit to disable extended next page (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-apple: drop invalid put of admin queue reference count (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4 (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix admin queue leak on controller reset (git-fixes).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- openvswitch: vport: fix self-deadlock on release of tunnel ports (git-fixes).\n- panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() (bsc#1261149).\n- panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() (bsc#1261149).\n- panic: introduce helper functions for panic state (bsc#1261149).\n- panic: use angle-bracket include for panic.h (bsc#1261149).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI/ASPM: Fix pci_clear_and_set_config_dword() usage (git-fixes).\n- PCI/NPEM: Set LED_HW_PLUGGABLE for hotplug-capable ports (git-fixes).\n- PCI/TPH: Allow TPH enable for RCiEPs (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: dwc: rcar-gen4: Change EPC BAR alignment to 4K as per the documentation (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup (git-fixes).\n- PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (bsc#1261648).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Free up Endpoint resources during remove() (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse \"nvidia,refclk-select\" (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- pinctrl: realtek: Fix function signature for config argument (git-fixes).\n- pinctrl: renesas: rzg2l: Fix save/restore of {IOLH,IEN,PUPD,SMT} registers (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86: asus-wmi: adjust screenpad power/brightness handling (git-fixes).\n- platform/x86: asus-wmi: fix screenpad brightness range (git-fixes).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- printk/nbcon/panic: Allow printk kthread to sleep when the system is in panic (bsc#1261149).\n- printk/nbcon: Block printk kthreads when any CPU is in an emergency context (bsc#1261149).\n- printk/nbcon: Release nbcon consoles ownership in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: Restore IRQ in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: use panic_on_this_cpu() helper (bsc#1261149).\n- printk: Allow printk_trigger_flush() to flush all types (bsc#1262750).\n- printk: Allow to use the printk kthread immediately even for 1st nbcon (jsc#PED-7912).\n- printk: Avoid irq_work for printk_deferred() on suspend (bsc#1262750).\n- printk: Avoid scheduling irq_work on suspend (bsc#1262750).\n- printk: console_flush_one_record() code cleanup (bsc#1261149).\n- printk: Introduce console_flush_one_record (bsc#1261149).\n- printk: Use console_flush_one_record for legacy printer kthread (bsc#1261149).\n- pwm: imx-tpm: Count the number of enabled channels in probe (git-fixes).\n- qat: don't mess with -\u003ed_name (jsc#PED-14238).\n- r8152: fix incorrect register write to USB_UPHY_XTAL (git-fixes).\n- RDMA/irdma: Fix double free related to rereg_user_mr (git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- regulator: rk808: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Fix sram property parsing (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert \"ALSA: usb: Increase volume range that triggers a warning\" (git-fixes).\n- Revert \"serial: 8250: Revert \"drop lockdep annotation from serial8250_clear_IER()\"\" (bsc#1262480).\n- Revert \"serial: 8250: Switch to nbcon console\" (bsc#1262480).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259994).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259994).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259994).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: lpfc: Use the crc32c() function (bsc#1262019).\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues (git-fixes).\n- scsi: ses: Fix devices attaching to different hosts (git-fixes).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- scsi: ufs: ufs-pci: Add support for Intel Wildcat Lake (jsc#PED-13771).\n- selftests/bpf: Test cross-sign 64bits range refinement (git-fixes).\n- selftests/bpf: Test invariants on JSLT crossing sign (git-fixes).\n- selftests/bpf: test refining u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- selftests: net: build net/lib dependency in all target (bsc#1262245).\n- selinux: don't reserve xattr slot when we won't fill it (stable-fixes).\n- selinux: prune /sys/fs/selinux/disable (stable-fixes).\n- selinux: shrink critical section in sel_write_load() (stable-fixes).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- Set CONFIG_INTEL_TSX_MODE to follow upstream AUTO default (bsc#1263044).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- soc: qcom: ocmem: make the core clock optional (git-fixes).\n- soc: qcom: ocmem: register reasons for probe deferrals (git-fixes).\n- soc: qcom: ocmem: return -EPROBE_DEFER is ocmem is not available (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- soundwire: debugfs: initialize firmware_file to empty string (git-fixes).\n- spi: aspeed-smc: fix controller deregistration (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: bcm63xx: fix controller deregistration (git-fixes).\n- spi: bcmbca-hsspi: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: cadence: fix unclocked access on unbind (git-fixes).\n- spi: ch341: fix memory leaks on probe failures (git-fixes).\n- spi: coldfire-qspi: fix controller deregistration (git-fixes).\n- spi: dln2: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-espi: fix controller deregistration (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: fsl: fix controller deregistration (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: img-spfi: fix controller deregistration (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: lantiq-ssc: fix controller deregistration (git-fixes).\n- spi: meson-spicc: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix use-after-free on registration failure (git-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: fix memory leak in probe (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: mxic: fix controller deregistration (git-fixes).\n- spi: mxs: fix controller deregistration (git-fixes).\n- spi: npcm-pspi: fix controller deregistration (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix controller deregistration (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: pic32-sqi: fix controller deregistration (git-fixes).\n- spi: pic32: fix controller deregistration (git-fixes).\n- spi: pl022: fix controller deregistration (git-fixes).\n- spi: qup: fix controller deregistration (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rockchip: Read ISR, not IMR, to detect cs-inactive IRQ (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix NULL-deref on driver unbind (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: st-ssc4: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun6i: fix controller deregistration (git-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: ti-qspi: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix use-after-free on unbind (git-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynq-qspi: fix controller deregistration (git-fixes).\n- spi: zynq-qspi: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tools/power/turbostat: Fix microcode patch level output for AMD/Hygon (git-fixes).\n- tools: hv: Fix cross-compilation (git-fixes).\n- tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public() (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: Fix auth session leak in tpm2_get_random() error path (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tpm: Use kfree_sensitive() to free auth session in tpm_dev_release() (git-fixes).\n- tty: serial: ip22zilog: Fix section mispatch warning (git-fixes).\n- udp: Force compute_score to always inline (bsc#1241259).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (git-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_hid: Add missing error code (git-fixes).\n- usb: gadget: f_hid: don't call cdev_init while cdev in use (git-fixes).\n- usb: gadget: f_hid: move list and spinlock inits from bind to alloc (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (git-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (git-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (git-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- vfio/pci: Lock upstream bridge for vfio_pci_core_disable() (git-fixes).\n- vfio/pds: Fix memory leak in pds_vfio_dirty_enable() (git-fixes).\n- vfio/pds: Fix missing detach_ioas op (git-fixes).\n- vfio/pds: replace bitmap_free with vfree (git-fixes).\n- vfio/type1: Fix error unwind in migration dirty bitmap allocation (git-fixes).\n- vfio: Fix unbalanced vfio_df_close call in no-iommu mode (git-fixes).\n- vfio: Prevent open_count decrement to negative (git-fixes).\n- virt: arm-cca-guest: fix error check for RSI_INCOMPLETE (git-fixes).\n- virt: sev-guest: Do not use host-controlled page order in cleanup path (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath10k: fix station lookup failure during disconnect (git-fixes).\n- wifi: ath11k: fix memory leaks in beacon template setup (git-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert \"Fix locking in error paths\" (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Place upper limit on station AID (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix AMPDU state handling in mt7925_tx_check_aggr (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7925: Fix incorrect MLO mode in firmware control (git-fixes).\n- wifi: mt76: mt7925: fix incorrect TLV length in CLC command (git-fixes).\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtl8xxxu: fix potential use of uninitialized value (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: Add additional USB IDs for RTL8812BU (bsc#1263135).\n- wifi: rtw88: Add BUFFALO WI-U3-866DHP to the USB ID list (bsc#1263135).\n- wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 (bsc#1263135).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw88: rtw8822bu VID/PID for BUFFALO WI-U2-866DM (bsc#1263135).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- x86/acpi/boot: Correct acpi_is_processor_usable() check again (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot/sev: Support memory acceptance in the EFI stub under SVSM (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Fix early boot failures on SEV-ES/SNP guests (git-fixes).\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges() (git-fixes).\n- x86/sev: Add missing RIP_REL_REF() invocations during sme_enable() (git-fixes).\n- x86/sev: Do not touch VMSA pages during SNP guest memory kdump (git-fixes).\n- x86/sev: Ensure SVSM reserved fields in a page validation entry are initialized to zero (git-fixes).\n- x86/sev: Fix operator precedence in GHCB_MSR_VMPL_REQ_LEVEL macro (git-fixes).\n- x86/sev: Improve handling of writes to intercepted TSC MSRs (git-fixes).\n- x86/sev: Make sure pages are not skipped during kdump (git-fixes).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951 bsc#1263044).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951 bsc#1263044).\n- x86/vmware: Parse MP tables for SEV-SNP enabled guests under VMware hypervisors (git-fixes).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n","status":"published","published":"2026-05-28T11:49:10Z","modified":"2026-06-02T18:24:25.768544597Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21860-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-2058: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2024-14027: xattr: switch to CLASS(fd) (bsc#1259420).\n- CVE-2025-40181: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (bsc#1253471).\n- CVE-2025-68265: nvme: fix admin request_queue lifetime (bsc#1255360).\n- CVE-2025-68310: s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump (bsc#1255160).\n- CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules (bsc#1264837).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: add xmit recursion limit to tunnel xmit functions (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23316: net: ipv4: fix ARM64 alignment fault in multipath hash seed (bsc#1260573).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23346: arm64: io: Rename ioremap_prot() to __ioremap_prot() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23375: mm: thp: deny THP for files on anonymous inodes (bsc#1260576).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23417: bpf: Fix constant blinding for PROBE_MEM32 stores (bsc#1261410).\n- CVE-2026-23436: net: add helpers for lookup and walking netdevs under netdev_lock() (bsc#1261617).\n- CVE-2026-23437: net: shaper: protect late read accesses to the hierarchy (bsc#1261635).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31392: smb: client: fix krb5 mount with username option (bsc#1261788).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31406: xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (bsc#1261629).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31435: netfs: Fix read abandonment during retry (bsc#1262601).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31453: xfs: avoid dereferencing log items after push callbacks (bsc#1262617).\n- CVE-2026-31456: mm/pagewalk: fix race between concurrent split and refault (bsc#1262627).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31503: udp: Fix wildcard bind conflict check when using hash2 (bsc#1263077).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31526: bpf: Fix exception exit lock checking for subprogs (bsc#1262662).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags (bsc#1263107).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit (bsc#1263074).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload() (bsc#1263048).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31658: net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() (bsc#1263052).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31666: btrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref() (bsc#1263138).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release (bsc#1263562).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31691: igb: remove napi_synchronize() in igb_down() (bsc#1263604).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43045: mshv: Refactor and rename memory region handling functions (bsc#1263942).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43082: net: txgbe: leave space for null terminators on property_entry (bsc#1264233).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43153: xfs: remove xfs_attr_leaf_hasname (bsc#1264586).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ACPI: video: Move Lenovo Legion S7 15ACH6 quirk to the right section (git-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/hdmi: Add quirk for TUXEDO IBS14G6 (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger (stable-fixes).\n- ALSA: pcmtest: fix reference leak on failed device registration (git-fixes).\n- ALSA: pcmtest: Fix resource leaks in module init error paths (git-fixes).\n- ALSA: pcmtest: Return -EFAULT on pattern read copy failure (git-fixes).\n- ALSA: sc6000: Keep the programmed board state in card-private data (git-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- ALSA: virtio: drop an extaneous kernel-doc comment (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for \"VAD Detected\" (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- backlight: sky81452-backlight: Check return value of devm_gpiod_get_optional() in sky81452_bl_parse_dt() (git-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- bitfield: Add FIELD_MODIFY() helper (jsc#PED-14238).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (bsc#1260996).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: fix memset typo (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- bpf: Add third round of bounds deduction (git-fixes).\n- bpf: Fix u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- bpf: Improve bounds when s64 crosses sign boundary (git-fixes).\n- bpf: Switch CONFIG_CFI_CLANG to CONFIG_CFI (git-fixes).\n- btrfs: qgroup: update all parent qgroups when doing quick inherit (bsc#1258933).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- bus: mhi: host: pci_generic: Switch to async power up to avoid boot delays (git-fixes).\n- bus: rifsc: fix RIF configuration check for peripherals (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from \"scaling factor\" list (bsc#1249104).\n- crypto: af_alg - limit RX SG extraction by receive buffer budget (git-fixes).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix error codes in OTP reads (git-fixes).\n- crypto: atmel-sha204a - Fix OTP sysfs read and error handling (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-sha204a - Fix uninitialized data access on OTP read error (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: drivers - Switch back to struct platform_driver::remove() (jsc#PED-14238).\n- crypto: drivers - Use str_enable_disable-like helpers (jsc#PED-14238).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: iaa - Adjust workqueue allocation type (jsc#PED-14238).\n- crypto: iaa - fix per-node CPU counter reset in rebalance_wq_table() (git-fixes).\n- crypto: iaa - Move compression CRC into request object (jsc#PED-14238).\n- crypto: iaa - Optimize rebalance_wq_table() (jsc#PED-14238).\n- crypto: iaa - Remove potential infinite loop in check_completion() (jsc#PED-14238).\n- crypto: iaa - Remove unreachable pr_debug from iaa_crypto_cleanup_module (jsc#PED-14238).\n- crypto: iaa - Remove unused disable_async argument from iaa_decompress (jsc#PED-14238).\n- crypto: iaa - Replace sprintf with sysfs_emit in sysfs show functions (jsc#PED-14238).\n- crypto: iaa - Simplify init_iaa_device() (jsc#PED-14238).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: nx - Fix packed layout in struct nx842_crypto_header (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - #undef field_get() before local definition (jsc#PED-14238).\n- crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting (jsc#PED-14238).\n- crypto: qat - add bank state save and restore for qat_420xx (jsc#PED-14238).\n- crypto: qat - add command queue telemetry counters for GEN6 (jsc#PED-14238).\n- crypto: qat - add compression slice count for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service for rate limiting (jsc#PED-14238).\n- crypto: qat - add decompression service to telemetry (jsc#PED-14238).\n- crypto: qat - add firmware headers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add GEN6 firmware loader (jsc#PED-14238).\n- crypto: qat - add get_svc_slice_cnt() in device data structure (jsc#PED-14238).\n- crypto: qat - add live migration enablers for GEN6 devices (jsc#PED-14238).\n- crypto: qat - add macro to write 64-bit values to registers (jsc#PED-14238).\n- crypto: qat - add missing header inclusion (jsc#PED-14238).\n- crypto: qat - add qat_6xxx driver (jsc#PED-14238).\n- crypto: qat - add ring buffer idle telemetry counter for GEN6 (jsc#PED-14238).\n- crypto: qat - add support for decompression service to GEN6 devices (jsc#PED-14238).\n- crypto: qat - consolidate service enums (jsc#PED-14238).\n- crypto: qat - Constify struct pm_status_row (jsc#PED-14238).\n- crypto: qat - disable 4xxx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - disable 420xx AE cluster when lead engine is fused off (git-fixes).\n- crypto: qat - do not export adf_cfg_services (jsc#PED-14238).\n- crypto: qat - enable power management debugfs for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable RAS support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable rate limiting feature for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable reporting of error counters for GEN6 devices (jsc#PED-14238).\n- crypto: qat - enable telemetry for GEN6 devices (jsc#PED-14238).\n- crypto: qat - export adf_get_service_mask() (jsc#PED-14238).\n- crypto: qat - export adf_init_admin_pm() (jsc#PED-14238).\n- crypto: qat - expose configuration functions (jsc#PED-14238).\n- crypto: qat - fix compression instance leak (git-fixes).\n- crypto: qat - fix IRQ cleanup on 6xxx probe failure (git-fixes).\n- crypto: qat - fix object goals in Makefiles (jsc#PED-14238.\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - Fix typo \"accelaration\" (jsc#PED-14238).\n- crypto: qat - fix virtual channel configuration for GEN6 devices (jsc#PED-14238).\n- crypto: qat - include qat_common in top Makefile (jsc#PED-14238).\n- crypto: qat - introduce fuse array (jsc#PED-14238).\n- crypto: qat - make adf_dev_autoreset() static (jsc#PED-14238).\n- crypto: qat - optimize allocations for fw authentication (jsc#PED-14238).\n- crypto: qat - refactor compression template logic (jsc#PED-14238).\n- crypto: qat - refactor FW signing algorithm (jsc#PED-14238).\n- crypto: qat - refactor ring-related debug functions (jsc#PED-14238).\n- crypto: qat - refactor service parsing logic (jsc#PED-14238).\n- crypto: qat - relocate and rename bank state structure definition (jsc#PED-14238).\n- crypto: qat - relocate bank state helper functions (jsc#PED-14238).\n- crypto: qat - relocate power management debugfs helper APIs (jsc#PED-14238).\n- crypto: qat - relocate service related functions (jsc#PED-14238).\n- crypto: qat - remove BITS_IN_DWORD() (jsc#PED-14238).\n- crypto: qat - Remove dst_null support (jsc#PED-14238).\n- crypto: qat - remove duplicate masking for GEN6 devices (jsc#PED-14238).\n- crypto: qat - remove initialization in device class (jsc#PED-14238).\n- crypto: qat - remove redundant FW image size check (jsc#PED-14238).\n- crypto: qat - remove unused adf_devmgr_get_first (jsc#PED-14238).\n- crypto: qat - remove unused members in suof structure (jsc#PED-14238).\n- crypto: qat - rename and relocate timer logic (jsc#PED-14238).\n- crypto: qat - reorder objects in qat_common Makefile (jsc#PED-14238).\n- crypto: qat - replace CHECK_STAT macro with static inline function (jsc#PED-14238).\n- crypto: qat - Replace kzalloc() + copy_from_user() with memdup_user() (jsc#PED-14238).\n- crypto: qat - restore ASYM service support for GEN6 devices (jsc#PED-14238).\n- crypto: qat - Return pointer directly in adf_ctl_alloc_resources (jsc#PED-14238).\n- crypto: qat - set command ids as reserved (jsc#PED-14238).\n- crypto: qat - switch to standard pattern for PCI IDs (jsc#PED-14238).\n- crypto: qat - update firmware api (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in adf_gen4_hw_data.c (jsc#PED-14238).\n- crypto: qat - use pr_fmt() in qat uclo.c (jsc#PED-14238).\n- crypto: qat - use simple_strtoull to improve qat_uclo_parse_num (jsc#PED-14238).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: qat - validate service in rate limiting sysfs api (jsc#PED-14238).\n- crypto: qat/qat_6xxx - Fix NULL vs IS_ERR() check in adf_probe() (jsc#PED-14238).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: tegra - Disable softirqs before finalizing request (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dmaengine: dw-axi-dmac: fix Alignment should match open parenthesis (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drivers/base/memory: fix memory block reference leak in poison accounting (git-fixes).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- erofs: add GFP_NOIO in the bio completion if needed (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: Fixed sysfs duplicate filename issue (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: arm_ffa: Use the correct buffer size during RXTX_MAP (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- firmware: google: framebuffer: Do not mark framebuffer as busy (git-fixes).\n- firmware: google: framebuffer: Do not unregister platform device (git-fixes).\n- gpio: of: clear OF_POPULATED on hog nodes in remove path (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: amd_sfh: don't log error when device discovery fails with -EOPNOTSUPP (git-fixes).\n- HID: apple: ensure the keyboard backlight is off if suspending (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: logitech-hidpp: Enable MX Master 4 over bluetooth (stable-fixes).\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hisi_acc_vfio_pci: add eq and aeq interruption restore (git-fixes).\n- hisi_acc_vfio_pci: bugfix cache write-back issue (git-fixes).\n- hisi_acc_vfio_pci: bugfix the problem of uninstalling driver (git-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hv_sock: update outdated comment for renamed vsock_stream_recvmsg() (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- hwmon: (ltc4286) Add missing MODULE_IMPORT_NS(\"PMBUS\") (git-fixes).\n- hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt (git-fixes).\n- hwmon: (powerz) Fix use-after-free on USB disconnect (git-fixes).\n- hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i2c: tegra: Add HS mode support (bsc#1261550).\n- i2c: tegra: Add Tegra256 support (bsc#1261550).\n- i2c: tegra: Do not configure DMA if not supported (bsc#1261550).\n- i2c: tegra: Don't mark devices with pins as IRQ safe (stable-fixes).\n- i2c: tegra: Update Tegra256 timing parameters (bsc#1261550).\n- i2c: tegra: Use separate variables for fast and fastplus (bsc#1261550).\n- i3c: dw: Fix memory leak in dw_i3c_master_i3c_xfers() (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- iio: adc: ad7192: Revert \"properly check spi_get_device_match_data()\" (stable-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- iio: frequency: admv1013: add dev variable (stable-fixes).\n- iio: frequency: admv1013: fix NULL pointer dereference on str (git-fixes).\n- Input: bcm5974 - recover from failed mode switch (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request \"event\" (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- interconnect: debugfs: fix devm_kstrdup and kfree mismatch (git-fixes).\n- io_uring/timeout: check unused sqe fields (git-fixes).\n- iommu/amd: move wait_on_sem() out of spinlock (git-fixes bsc#1260593).\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations (git-fixes bsc#1260593).\n- iommu/vt-d: Remove LPIG from page group response descriptor (jsc#PED-16113).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- ipv6: rpl: reserve mac_len headroom when recompressed SRH grows (git-fixes).\n- KVM: arm64: Allow cacheable stage 2 mapping using VMA flags (git-fixes).\n- KVM: arm64: Assume non-PFNMAP/MIXEDMAP VMAs can be mapped cacheable (git-fixes).\n- KVM: arm64: Block cacheable PFNMAP mapping (git-fixes).\n- KVM: arm64: Consolidate idreg callbacks (git-fixes).\n- KVM: arm64: Discard PC update state on vcpu reset (git-fixes).\n- KVM: arm64: Finalize ID registers only once per VM (git-fixes).\n- KVM: arm64: Fix MTE flag initialization for protected VMs (git-fixes).\n- KVM: arm64: Fix page leak in user_mem_abort() (git-fixes).\n- KVM: arm64: Fix Trace Buffer trap polarity for protected VMs (git-fixes).\n- KVM: arm64: Fix Trace Buffer trapping for protected VMs (git-fixes).\n- KVM: arm64: Fix vma_shift staleness on nested hwpoison path (git-fixes).\n- KVM: arm64: Hide S1POE from guests when not supported by the host (git-fixes).\n- KVM: arm64: Limit clearing of ID_{AA64PFR0,PFR1}_EL1.GIC to userspace irqchip (git-fixes).\n- KVM: arm64: Make all 32bit ID registers fully writable (git-fixes).\n- KVM: arm64: nv: Add trap config for DBGWCR\u003c15\u003e_EL1 (git-fixes).\n- KVM: arm64: nv: Return correct RES0 bits for FGT registers (git-fixes).\n- KVM: arm64: pkvm: Fallback to level-3 mapping on host stage-2 fault (git-fixes).\n- KVM: arm64: Read PMUVer as unsigned (git-fixes).\n- KVM: arm64: Rename the device variable to s2_force_noncacheable (git-fixes).\n- KVM: arm64: Return early from trace helpers when KVM isn't available (git-fixes).\n- KVM: arm64: Set ID_{AA64PFR0,PFR1}_EL1.GIC when GICv3 is configured (git-fixes).\n- KVM: arm64: vgic-v3: Release reserved slot outside of lpi_xa's lock (git-fixes).\n- KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).\n- KVM: nSVM: Use vcpu-\u003earch.cr2 when updating vmcb12 on nested #VMEXIT (git-fixes).\n- KVM: nVMX: Add consistency check for TSC_MULTIPLIER=0 (git-fixes).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created (git-fixes).\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION (git-fixes).\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish (git-fixes).\n- KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock (git-fixes).\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU (git-fixes).\n- KVM: SVM: Disallow EFER.LMSLE when not supported by hardware (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Initialize AVIC VMCB fields if AVIC is enabled with in-kernel APIC (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Properly check RAX in the emulator for SVM instructions (git-fixes).\n- KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated (git-fixes).\n- KVM: TDX: Explicitly set user-return MSRs that *may* be clobbered by the TDX-Module (git-fixes).\n- KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter (git-fixes).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (git-fixes).\n- KVM: x86: Advertise EferLmsleUnsupported to userspace (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: X86: Fix array_index_nospec protection in __pv_send_ipi (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx283: Enter full standby when stopping streaming (git-fixes).\n- media: i2c: imx283: Fix hang when going from large to small resolution (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: core: Preserve OF node when ACPI handle is present (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mfd: stpmic1: Attempt system shutdown twice in case PMIC is confused (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net-shapers: don't free reply skb after genlmsg_reply() (git-fixes).\n- net/mlx5: Fix HCA caps leak on notifier init failure (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of \"old\" filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: hamradio: 6pack: fix uninit-value in sixpack_receive_buf (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: Move current_speed debugfs file to mana_init_port() (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: broadcom: Save PHY counters during suspend (git-fixes).\n- net: phy: DP83TC811: add reading of abilities (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: phy: fix a return path in get_phy_c45_ids() (git-fixes).\n- net: phy: qcom: at803x: Use the correct bit to disable extended next page (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-apple: drop invalid put of admin queue reference count (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: add NVME_QUIRK_DISABLE_WRITE_ZEROES for Kingston OM3SGP4 (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix admin queue leak on controller reset (git-fixes).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- openvswitch: vport: fix self-deadlock on release of tunnel ports (git-fixes).\n- panic/printk: replace other_cpu_in_panic() with panic_on_other_cpu() (bsc#1261149).\n- panic/printk: replace this_cpu_in_panic() with panic_on_this_cpu() (bsc#1261149).\n- panic: introduce helper functions for panic state (bsc#1261149).\n- panic: use angle-bracket include for panic.h (bsc#1261149).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI/ASPM: Fix pci_clear_and_set_config_dword() usage (git-fixes).\n- PCI/NPEM: Set LED_HW_PLUGGABLE for hotplug-capable ports (git-fixes).\n- PCI/TPH: Allow TPH enable for RCiEPs (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: dwc: rcar-gen4: Change EPC BAR alignment to 4K as per the documentation (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup (git-fixes).\n- PCI: epf-mhi: Return 0, not remaining timeout, when eDMA ops complete (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (bsc#1261648).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: qcom: Advertise Hotplug Slot Capability with no Command Completion support (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Free up Endpoint resources during remove() (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse \"nvidia,refclk-select\" (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- pinctrl: realtek: Fix function signature for config argument (git-fixes).\n- pinctrl: renesas: rzg2l: Fix save/restore of {IOLH,IEN,PUPD,SMT} registers (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86: asus-wmi: adjust screenpad power/brightness handling (git-fixes).\n- platform/x86: asus-wmi: fix screenpad brightness range (git-fixes).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- printk/nbcon/panic: Allow printk kthread to sleep when the system is in panic (bsc#1261149).\n- printk/nbcon: Block printk kthreads when any CPU is in an emergency context (bsc#1261149).\n- printk/nbcon: Release nbcon consoles ownership in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: Restore IRQ in atomic flush after each emitted record (bsc#1261149).\n- printk/nbcon: use panic_on_this_cpu() helper (bsc#1261149).\n- printk: Allow printk_trigger_flush() to flush all types (bsc#1262750).\n- printk: Allow to use the printk kthread immediately even for 1st nbcon (jsc#PED-7912).\n- printk: Avoid irq_work for printk_deferred() on suspend (bsc#1262750).\n- printk: Avoid scheduling irq_work on suspend (bsc#1262750).\n- printk: console_flush_one_record() code cleanup (bsc#1261149).\n- printk: Introduce console_flush_one_record (bsc#1261149).\n- printk: Use console_flush_one_record for legacy printer kthread (bsc#1261149).\n- pwm: imx-tpm: Count the number of enabled channels in probe (git-fixes).\n- qat: don't mess with -\u003ed_name (jsc#PED-14238).\n- r8152: fix incorrect register write to USB_UPHY_XTAL (git-fixes).\n- RDMA/irdma: Fix double free related to rereg_user_mr (git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- regulator: rk808: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Fix sram property parsing (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert \"ALSA: usb: Increase volume range that triggers a warning\" (git-fixes).\n- Revert \"serial: 8250: Revert \"drop lockdep annotation from serial8250_clear_IER()\"\" (bsc#1262480).\n- Revert \"serial: 8250: Switch to nbcon console\" (bsc#1262480).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259994).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259994).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259994).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: lpfc: Use the crc32c() function (bsc#1262019).\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues (git-fixes).\n- scsi: ses: Fix devices attaching to different hosts (git-fixes).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- scsi: ufs: ufs-pci: Add support for Intel Wildcat Lake (jsc#PED-13771).\n- selftests/bpf: Test cross-sign 64bits range refinement (git-fixes).\n- selftests/bpf: Test invariants on JSLT crossing sign (git-fixes).\n- selftests/bpf: test refining u32/s32 bounds when ranges cross min/max boundary (git-fixes).\n- selftests: net: build net/lib dependency in all target (bsc#1262245).\n- selinux: don't reserve xattr slot when we won't fill it (stable-fixes).\n- selinux: prune /sys/fs/selinux/disable (stable-fixes).\n- selinux: shrink critical section in sel_write_load() (stable-fixes).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- Set CONFIG_INTEL_TSX_MODE to follow upstream AUTO default (bsc#1263044).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- soc: qcom: ocmem: make the core clock optional (git-fixes).\n- soc: qcom: ocmem: register reasons for probe deferrals (git-fixes).\n- soc: qcom: ocmem: return -EPROBE_DEFER is ocmem is not available (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- soundwire: debugfs: initialize firmware_file to empty string (git-fixes).\n- spi: aspeed-smc: fix controller deregistration (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: bcm63xx: fix controller deregistration (git-fixes).\n- spi: bcmbca-hsspi: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: cadence: fix unclocked access on unbind (git-fixes).\n- spi: ch341: fix memory leaks on probe failures (git-fixes).\n- spi: coldfire-qspi: fix controller deregistration (git-fixes).\n- spi: dln2: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-espi: fix controller deregistration (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: fsl: fix controller deregistration (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: img-spfi: fix controller deregistration (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: lantiq-ssc: fix controller deregistration (git-fixes).\n- spi: meson-spicc: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix controller deregistration (git-fixes).\n- spi: mpc52xx: fix use-after-free on registration failure (git-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: fix memory leak in probe (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: mxic: fix controller deregistration (git-fixes).\n- spi: mxs: fix controller deregistration (git-fixes).\n- spi: npcm-pspi: fix controller deregistration (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix controller deregistration (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: pic32-sqi: fix controller deregistration (git-fixes).\n- spi: pic32: fix controller deregistration (git-fixes).\n- spi: pl022: fix controller deregistration (git-fixes).\n- spi: qup: fix controller deregistration (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rockchip: Read ISR, not IMR, to detect cs-inactive IRQ (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix controller deregistration (git-fixes).\n- spi: s3c64xx: fix NULL-deref on driver unbind (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: st-ssc4: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun6i: fix controller deregistration (git-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: ti-qspi: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix controller deregistration (git-fixes).\n- spi: topcliff-pch: fix use-after-free on unbind (git-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynq-qspi: fix controller deregistration (git-fixes).\n- spi: zynq-qspi: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tools/power/turbostat: Fix microcode patch level output for AMD/Hygon (git-fixes).\n- tools: hv: Fix cross-compilation (git-fixes).\n- tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public() (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: Fix auth session leak in tpm2_get_random() error path (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tpm: Use kfree_sensitive() to free auth session in tpm_dev_release() (git-fixes).\n- tty: serial: ip22zilog: Fix section mispatch warning (git-fixes).\n- udp: Force compute_score to always inline (bsc#1241259).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (git-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_hid: Add missing error code (git-fixes).\n- usb: gadget: f_hid: don't call cdev_init while cdev in use (git-fixes).\n- usb: gadget: f_hid: move list and spinlock inits from bind to alloc (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (git-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (git-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (git-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- vfio/pci: Lock upstream bridge for vfio_pci_core_disable() (git-fixes).\n- vfio/pds: Fix memory leak in pds_vfio_dirty_enable() (git-fixes).\n- vfio/pds: Fix missing detach_ioas op (git-fixes).\n- vfio/pds: replace bitmap_free with vfree (git-fixes).\n- vfio/type1: Fix error unwind in migration dirty bitmap allocation (git-fixes).\n- vfio: Fix unbalanced vfio_df_close call in no-iommu mode (git-fixes).\n- vfio: Prevent open_count decrement to negative (git-fixes).\n- virt: arm-cca-guest: fix error check for RSI_INCOMPLETE (git-fixes).\n- virt: sev-guest: Do not use host-controlled page order in cleanup path (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath10k: fix station lookup failure during disconnect (git-fixes).\n- wifi: ath11k: fix memory leaks in beacon template setup (git-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: ath12k: use lockdep_assert_in_rcu_read_lock() for RCU assertions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert \"Fix locking in error paths\" (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Place upper limit on station AID (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix AMPDU state handling in mt7925_tx_check_aggr (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7925: Fix incorrect MLO mode in firmware control (git-fixes).\n- wifi: mt76: mt7925: fix incorrect TLV length in CLC command (git-fixes).\n- wifi: mt76: mt7925: prevent NULL pointer dereference in mt7925_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mt76: mt7996: fix use-after-free bugs in mt7996_mac_dump_work() (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtl8xxxu: fix potential use of uninitialized value (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: Add additional USB IDs for RTL8812BU (bsc#1263135).\n- wifi: rtw88: Add BUFFALO WI-U3-866DHP to the USB ID list (bsc#1263135).\n- wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 (bsc#1263135).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw88: rtw8822bu VID/PID for BUFFALO WI-U2-866DM (bsc#1263135).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- x86/acpi/boot: Correct acpi_is_processor_usable() check again (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot/sev: Support memory acceptance in the EFI stub under SVSM (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Fix early boot failures on SEV-ES/SNP guests (git-fixes).\n- x86/mtrr: Check if fixed-range MTRRs exist in mtrr_save_fixed_ranges() (git-fixes).\n- x86/sev: Add missing RIP_REL_REF() invocations during sme_enable() (git-fixes).\n- x86/sev: Do not touch VMSA pages during SNP guest memory kdump (git-fixes).\n- x86/sev: Ensure SVSM reserved fields in a page validation entry are initialized to zero (git-fixes).\n- x86/sev: Fix operator precedence in GHCB_MSR_VMPL_REQ_LEVEL macro (git-fixes).\n- x86/sev: Improve handling of writes to intercepted TSC MSRs (git-fixes).\n- x86/sev: Make sure pages are not skipped during kdump (git-fixes).\n- x86/tsx: Get the tsx= command line parameter with early_param() (bsc#1250951 bsc#1263044).\n- x86/tsx: Make tsx_ctrl_state static (bsc#1250951 bsc#1263044).\n- x86/vmware: Parse MP tables for SEV-SNP enabled guests under VMware hypervisors (git-fixes).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n","status":"published","published":"2026-05-28T11:40:20Z","modified":"2026-06-02T18:24:31.043353389Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21886-1","title":"Security update for the Linux Kernel (Live Patch 7 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-29.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:40.80227677Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21887-1","title":"Security update for the Linux Kernel (Live Patch 8 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-30.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:34.159870995Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21888-1","title":"Security update for the Linux Kernel (Live Patch 9 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-31.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:40.776534648Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21889-1","title":"Security update for the Linux Kernel (Live Patch 10 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-32.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:40.761149559Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21890-1","title":"Security update for the Linux Kernel (Live Patch 11 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-34.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:34.368614823Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21891-1","title":"Security update for the Linux Kernel (Live Patch 13 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-36.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:34.155704072Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21892-1","title":"Security update for the Linux Kernel (Live Patch 14 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-38.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:40.734485716Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21893-1","title":"Security update for the Linux Kernel (Live Patch 16 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-39.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:24Z","modified":"2026-06-03T18:24:34.729659301Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21896-1","title":"Security update for the Linux Kernel (Live Patch 12 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-35.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:27:23Z","modified":"2026-06-03T18:24:42.153311151Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21900-1","title":"Security update for the Linux Kernel RT (Live Patch 8 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-31.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:51Z","modified":"2026-06-03T18:24:36.942845091Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21901-1","title":"Security update for the Linux Kernel RT (Live Patch 9 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-33.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:51Z","modified":"2026-06-03T18:24:42.237582944Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21902-1","title":"Security update for the Linux Kernel RT (Live Patch 10 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-34.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:51Z","modified":"2026-06-03T18:24:34.801354237Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21903-1","title":"Security update for the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-32.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:52Z","modified":"2026-06-03T18:24:35.533026748Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21904-1","title":"Security update for the Linux Kernel RT (Live Patch 12 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-36.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:52Z","modified":"2026-06-03T18:24:42.150269432Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21905-1","title":"Security update for the Linux Kernel RT (Live Patch 13 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-37.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:52Z","modified":"2026-06-03T18:24:42.228026567Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21906-1","title":"Security update for the Linux Kernel RT (Live Patch 14 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-38.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:52Z","modified":"2026-06-03T18:24:37.264537645Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:21907-1","title":"Security update for the Linux Kernel RT (Live Patch 15 for SUSE Linux Enterprise Micro 6.0)","description":"\nThis update for the SUSE Linux Enterprise Kernel 6.4.0-39.1 fixes various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-54518: AMD-SN-7052: CPU OP Cache Corruption (bsc#1264096).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259798).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260908).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260563).\n- CVE-2026-46300: FragNesia attack: another xfrm/esp based local root exploit (bsc#1265224).\n- CVE-2026-46333: ptrace: slightly saner 'get_dumpable()' logic (bsc#1265384).\n","status":"published","published":"2026-06-01T09:26:52Z","modified":"2026-06-03T18:24:37.003602511Z","updated_at":"2026-11-02T15:54:02.654057Z"}]},"sources_more":{"osv":52}}