{"id":"CVE-2025-38162","aliases":["AZL-64583","AZL-70645","BELL-CVE-2025-38162","CLSA-2026-1781344094","CLSA-2026-1783791447","DEBIAN-CVE-2025-38162","EUVD-2025-19782","GHSA-r97f-5wrg-fmv7","OESA-2026-1303","OESA-2026-1304","OESA-2026-1305","ROOT-OS-DEBIAN-11-CVE-2025-38162","ROOT-OS-DEBIAN-12-CVE-2025-38162","ROOT-OS-UBUNTU-2204-CVE-2025-38162","ROOT-OS-UBUNTU-2404-CVE-2025-38162","SUSE-SU-2025:02853-1","SUSE-SU-2025:02923-1","SUSE-SU-2025:02969-1","SUSE-SU-2025:02996-1","SUSE-SU-2025:02997-1","SUSE-SU-2025:03011-1","SUSE-SU-2025:03023-1","SUSE-SU-2025:20577-1","SUSE-SU-2025:20586-1","SUSE-SU-2025:20601-1","SUSE-SU-2025:20602-1","UBUNTU-CVE-2025-38162","USN-7769-1","USN-7769-2","USN-7769-3","USN-7770-1","USN-7771-1","USN-7789-1","USN-7789-2","USN-8028-1","USN-8028-2","USN-8028-3","USN-8028-4","USN-8028-5","USN-8028-6","USN-8028-7","USN-8028-8","USN-8031-1","USN-8031-2","USN-8031-3","USN-8052-1","USN-8052-2","USN-8074-1","USN-8074-2","USN-8126-1"],"status":"published","title":"netfilter: nft_set_pipapo: prevent overflow in lookup table allocation","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","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-10","score":0.00188,"percentile":0.08539,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-07-03T08:36:03Z","modified":"2026-11-10T12:36:15Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.126.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.167-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.41-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.125","6.12.34","6.15.3"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.170-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.35-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.12.35-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1046.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1051.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1046.53~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1047.50~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-100.100~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1044.44~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-100.100.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1046.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1043.44~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-100.100~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1041.42~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-100.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1046.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","fixed_in":["6.14.0-1013.13~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1046.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1046.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","fixed_in":["6.14.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1047.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","fixed_in":["6.14.0-1016.17~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1043.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1030.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1044.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-100.100.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1046.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1046.49.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","fixed_in":["6.14.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1043.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","fixed_in":["6.14.0-1013.13~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1047.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","fixed_in":["6.14.0-32.32.1~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1023.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1016.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2037.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1041.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","fixed_in":["6.14.0-1012.12~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1046.49+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1046.52+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-100.100+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1047.50+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.126.1-1"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"5.15.200.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.164-r0"},{"fixed":"6.1.167-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.89-r0"},{"fixed":"6.12.41-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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"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.els4"}]}],"bundled":94},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.6.0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.125"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.34"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.15.3"}]}]},{"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.35-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.35-1"}]}]},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.119.oe2403"}]}],"bundled":99},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.132.oe2403sp1"}]}],"bundled":99},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.132.oe2403sp2"}]}],"bundled":94},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.5.1"}]}],"bundled":260},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.13.1"}]}],"bundled":260},{"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.13.1"}]}],"bundled":260},{"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.13.1"}]}],"bundled":260},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.28.coco15sp6.1"}]}],"bundled":447},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-coco_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.28.coco15sp6.1"}]}],"bundled":447},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-source-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.28.coco15sp6.1"}]}],"bundled":447},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6","package":"kernel-syms-coco","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-15061.28.coco15sp6.1"}]}],"bundled":447},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.48.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1.150600.12.28.4"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.4"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1.150600.12.28.4"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.65.1"}]}],"bundled":238},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1.150700.17.9.4"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.3"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.4"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.11.1"}]}],"bundled":264},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.11.1"}]}],"bundled":265},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.11.1"}]}],"bundled":265},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.11.1"}]}],"bundled":265},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.5.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.49.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1.21.10"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1.21.10"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-32.1"}]}],"bundled":235},{"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:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~20.04.1","5.15.0-1103.110~20.04.1","5.15.0-1104.111~20.04.1","5.15.0-1105.112~20.04.1","5.15.0-1106.113~20.04.1","5.15.0-1108.115~20.04.1","5.15.0-1109.116~20.04.1","5.15.0-1111.118~20.04.1","5.15.0-1112.119~20.04.1","5.15.0-1114.121~20.04.1","5.15.0-1115.122~20.04.1","5.15.0-1116.123~20.04.1","5.15.0-1117.124~20.04.1","5.15.0-1119.126~20.04.1","5.15.0-1120.127~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1110.119~20.04.1","5.15.0-1111.120~20.04.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1123.132~20.04.1","5.15.0-1125.134~20.04.1","5.15.0-1126.135~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1","5.15.0-1081.90~20.04.1.1","5.15.0-1082.91~20.04.1.1","5.15.0-1086.95~20.04.1.1","5.15.0-1087.96~20.04.1.1","5.15.0-1088.97~20.04.1.1","5.15.0-1089.98~20.04.1.1","5.15.0-1091.100~20.04.1.1","5.15.0-1094.103~20.04.1.1","5.15.0-1096.105~20.04.1.1","5.15.0-1097.106~20.04.1.1","5.15.0-1098.107~20.04.1.1","5.15.0-1102.111~20.04.1.1","5.15.0-1103.112~20.04.1.1","5.15.0-1111.120~20.04.1.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.2","5.15.0-1118.127~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1120.129~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1124.133~20.04.1","5.15.0-1125.134~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1123.130","5.4.0-1125.132","5.4.0-1126.133"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1104.113~20.04.1","5.15.0-1106.115~20.04.1","5.15.0-1108.117~20.04.1","5.15.0-1109.118~20.04.1","5.15.0-1111.121~20.04.1","5.15.0-1112.122~20.04.1","5.15.0-1114.124~20.04.1","5.15.0-1118.128~20.04.1","5.15.0-1120.130~20.04.1","5.15.0-1121.131~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-176.186~20.04.1","5.15.0-177.187~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-185.195~20.04.1","5.15.0-186.196~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-198.208~20.04.1","5.15.0-202.212~20.04.1","5.15.0-203.213~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1","5.15.0-1097.100~20.04.1","5.15.0-1098.101~20.04.1","5.15.0-1099.102~20.04.1","5.15.0-1100.103~20.04.1","5.15.0-1102.105~20.04.1","5.15.0-1103.106~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.1","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1099.105~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1103.109~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1107.113~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1112.118~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1115.121~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-174.184~20.04.1","5.15.0-175.185~20.04.1","5.15.0-177.187~20.04.1","5.15.0-178.188~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-183.193~20.04.1","5.15.0-184.194~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-195.205~20.04.1","5.15.0-197.207~20.04.1","5.15.0-198.208~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~20.04.1","5.15.0-1055.55~20.04.1","5.15.0-1057.57~20.04.1","5.15.0-1058.58~20.04.1","5.15.0-1060.60~20.04.1","5.15.0-1061.61~20.04.1","5.15.0-1063.63~20.04.1","5.15.0-1064.66~20.04.1","5.15.0-1065.67~20.04.1","5.15.0-1066.68~20.04.1","5.15.0-1067.69~20.04.1","5.15.0-1068.70~20.04.1","5.15.0-1070.72~20.04.1","5.15.0-1071.73~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1102.108~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1116.122~20.04.1","5.15.0-1117.123~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1","5.15.0-1097.101~20.04.1","5.15.0-1098.102~20.04.1","5.15.0-1099.103~20.04.1","5.15.0-1100.104~20.04.1","5.15.0-1102.106~20.04.1","5.15.0-1103.107~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.2","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-176.186","5.15.0-177.187","5.15.0-179.189","5.15.0-181.191","5.15.0-185.195","5.15.0-186.196","5.15.0-187.197","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-198.208","5.15.0-202.212","5.15.0-203.213"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108","5.15.0-1103.110","5.15.0-1104.111","5.15.0-1105.112","5.15.0-1106.113","5.15.0-1108.115","5.15.0-1109.116","5.15.0-1111.118","5.15.0-1112.119","5.15.0-1113.120","5.15.0-1114.121","5.15.0-1115.122","5.15.0-1116.123","5.15.0-1117.124","5.15.0-1119.126","5.15.0-1120.127"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1109.118","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1123.132","5.15.0-1125.134","5.15.0-1126.135"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1","5.15.0-1109.118.1","5.15.0-1110.119.1","5.15.0-1111.120.1","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1120.129","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1124.133","5.15.0-1125.134"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.53~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1106.115","5.15.0-1108.117","5.15.0-1109.118","5.15.0-1111.121","5.15.0-1112.122","5.15.0-1114.124","5.15.0-1115.125","5.15.0-1117.127","5.15.0-1118.128","5.15.0-1120.130","5.15.0-1121.131"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50~22.04.2"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1104.110","5.15.0-1105.111","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1115.121","5.15.0-1116.122"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92","5.15.0-1086.94","5.15.0-1087.95","5.15.0-1088.96","5.15.0-1089.97","5.15.0-1091.99","5.15.0-1092.100","5.15.0-1094.102","5.15.0-1095.103","5.15.0-1096.104","5.15.0-1097.105","5.15.0-1098.106","5.15.0-1099.107","5.15.0-1100.108","5.15.0-1102.110","5.15.0-1103.111"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.109","5.15.0-1106.110","5.15.0-1107.111","5.15.0-1108.112","5.15.0-1109.113","5.15.0-1110.114","5.15.0-1111.115","5.15.0-1113.117","5.15.0-1114.118"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1098.104","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1103.109","5.15.0-1104.110","5.15.0-1106.112","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1114.120","5.15.0-1115.121"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98","5.15.0-1095.100","5.15.0-1096.101","5.15.0-1097.102","5.15.0-1098.103","5.15.0-1100.105","5.15.0-1101.106","5.15.0-1103.108","5.15.0-1104.109","5.15.0-1105.110","5.15.0-1106.111","5.15.0-1107.112","5.15.0-1108.113","5.15.0-1109.114","5.15.0-1111.116","5.15.0-1112.117"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-175.185","5.15.0-177.187","5.15.0-178.188","5.15.0-179.189","5.15.0-181.191","5.15.0-183.193","5.15.0-184.194","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-195.205","5.15.0-197.207","5.15.0-198.208"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97","5.15.0-1098.99","5.15.0-1099.100","5.15.0-1100.101","5.15.0-1101.102","5.15.0-1103.104","5.15.0-1104.105","5.15.0-1106.107","5.15.0-1107.108","5.15.0-1108.109","5.15.0-1109.110","5.15.0-1110.111","5.15.0-1111.112","5.15.0-1112.113","5.15.0-1114.115","5.15.0-1115.116"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1058.58","5.15.0-1060.60","5.15.0-1061.61","5.15.0-1063.63","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1068.70","5.15.0-1070.72","5.15.0-1071.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1054.54","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1059.59"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1103.109","5.15.0-1105.111","5.15.0-1106.112","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1114.120","5.15.0-1116.122","5.15.0-1117.123"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.108","5.15.0-1106.109","5.15.0-1108.111","5.15.0-1110.113"]},{"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-100.100~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73","5.15.0-1070.74","5.15.0-1074.78","5.15.0-1075.79","5.15.0-1076.80","5.15.0-1077.81","5.15.0-1078.82","5.15.0-1079.83","5.15.0-1080.84"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1095.97","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1094.96","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106","5.15.0-1105.107","5.15.0-1106.108","5.15.0-1107.109","5.15.0-1108.110","5.15.0-1109.111","5.15.0-1111.115","5.15.0-1112.116"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1107.116","5.15.0-1108.117","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1112.121","5.15.0-1113.122","5.15.0-1114.123","5.15.0-1115.124","5.15.0-1116.125","5.15.0-1118.127","5.15.0-1119.128"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1","5.15.0-1103.110+fips1","5.15.0-1104.111+fips1","5.15.0-1105.112+fips1","5.15.0-1106.113+fips1","5.15.0-1108.115+fips1","5.15.0-1109.116+fips1","5.15.0-1111.118+fips1","5.15.0-1112.119+fips1","5.15.0-1113.120+fips1","5.15.0-1114.121+fips1","5.15.0-1115.122+fips1","5.15.0-1116.123+fips1","5.15.0-1117.124+fips1","5.15.0-1119.126+fips1","5.15.0-1120.127+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1","5.15.0-1109.118+fips1","5.15.0-1110.119+fips1","5.15.0-1111.120+fips1","5.15.0-1114.123+fips1","5.15.0-1116.125+fips1","5.15.0-1117.126+fips1","5.15.0-1118.127+fips1","5.15.0-1119.128+fips1","5.15.0-1121.130+fips1","5.15.0-1122.131+fips1","5.15.0-1123.132+fips1","5.15.0-1125.134+fips1","5.15.0-1126.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1","5.15.0-173.183+fips1","5.15.0-174.184+fips1","5.15.0-176.186+fips1","5.15.0-177.187+fips1","5.15.0-179.189+fips1","5.15.0-181.191+fips1","5.15.0-185.195+fips1","5.15.0-186.196+fips1","5.15.0-190.200+fips1","5.15.0-191.201+fips1","5.15.0-194.204+fips1","5.15.0-198.208+fips1","5.15.0-202.212+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1","5.15.0-1105.114+fips1","5.15.0-1106.115+fips1","5.15.0-1108.117+fips1","5.15.0-1109.118+fips1","5.15.0-1111.121+fips1","5.15.0-1112.122+fips1","5.15.0-1114.124+fips1","5.15.0-1115.125+fips1","5.15.0-1116.126+fips1","5.15.0-1118.128+fips1","5.15.0-1120.130+fips1","5.15.0-1121.131+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1013.13~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52"}]}],"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"]},{"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-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.53"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51"]},{"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"},{"fixed":"6.14.0-1007.7"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50"}]}],"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"]},{"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"},{"fixed":"6.14.0-1016.17~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.48"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.33"}]}],"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"]},{"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-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-intel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1005.12","6.8.0-1006.13","6.8.0-1007.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1"]},{"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-1046.49"}]}],"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"]},{"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-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49.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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.20"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1012.12"}]}],"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"]},{"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-1043.44"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1013.13~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.51"}]}],"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"]},{"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"},{"fixed":"6.14.0-32.32.1~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.24"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.20"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2037.38"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1012.12~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50+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"]},{"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:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1016.17~24.04.1"}]}],"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"],"bundled":183},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1012.12~24.04.1"}]}],"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"],"bundled":183},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1013.13~24.04.1"}]}],"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"],"bundled":184},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-32.32~24.04.1"}]}],"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"],"bundled":184},{"source":"osv","ecosystem":"Ubuntu:25.04","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1012.12"}]}],"versions":["6.11.0-1004.4","6.12.0-1002.2","6.12.0-1004.4","6.14.0-1002.2","6.14.0-1003.3","6.14.0-1004.4","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10"],"bundled":184},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1012.12"}]}],"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"],"bundled":182},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1013.13~24.04.1"}]}],"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"],"bundled":184},{"source":"osv","ecosystem":"Ubuntu:25.04","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1014.14"}]}],"versions":["6.11.0-1004.4","6.14.0-1003.3","6.14.0-1004.4","6.14.0-1005.5","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1009.9","6.14.0-1010.10","6.14.0-1012.12","6.14.0-1013.13"],"bundled":184},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.51"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2037.38"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49+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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44~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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.33"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100~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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49.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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44~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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50~22.04.2"}]}],"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"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50+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"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50"}]}],"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"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.48"}]}],"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"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.24"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52"}]}],"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"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1"],"bundled":1179}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp (6ag1518-4ax00-4ac0)"}],"references":[{"url":"https://git.kernel.org/stable/c/91edc076439c9e2f34b176149f1c84a47a8ec32f","tags":["web"]},{"url":"https://git.kernel.org/stable/c/a9e757473561da93c6a4136f0e59aba91ec777fc","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/c1360ac8156c0a3f2385baef91d8d26fd9d39701","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/43fe1181f738295624696ae9ff611790edb65b5e","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/4c5c6aa9967dbe55bd017bb509885928d0f31206","tags":["Patch","web","report"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-082556.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-019113.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-457936.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-784472.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38162","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-r97f-5wrg-fmv7"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-38162","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1781344094.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53128","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56629","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21763","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38424","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38458","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38524","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23335","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23370","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23472","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31523","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31579","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31661","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46316","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1783791447.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-4454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49443","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52523","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52845","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53332","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53517","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53792","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50045","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21732","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-54505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71227","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23210","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31518","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43499","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38162.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-38162","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38489","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38714","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40311","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40314","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68184","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68218","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68295","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71151","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1304","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40058","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502853-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1204142","tags":["report"]},{"url":"https://bugzilla.suse.com/1219338","tags":["report"]},{"url":"https://bugzilla.suse.com/1225707","tags":["report"]},{"url":"https://bugzilla.suse.com/1228664","tags":["report"]},{"url":"https://bugzilla.suse.com/1230216","tags":["report"]},{"url":"https://bugzilla.suse.com/1233300","tags":["report"]},{"url":"https://bugzilla.suse.com/1235515","tags":["report"]},{"url":"https://bugzilla.suse.com/1235613","tags":["report"]},{"url":"https://bugzilla.suse.com/1235837","tags":["report"]},{"url":"https://bugzilla.suse.com/1236333","tags":["report"]},{"url":"https://bugzilla.suse.com/1236897","tags":["report"]},{"url":"https://bugzilla.suse.com/1238896","tags":["report"]},{"url":"https://bugzilla.suse.com/1239061","tags":["report"]},{"url":"https://bugzilla.suse.com/1240323","tags":["report"]},{"url":"https://bugzilla.suse.com/1240696","tags":["report"]},{"url":"https://bugzilla.suse.com/1240885","tags":["report"]},{"url":"https://bugzilla.suse.com/1240966","tags":["report"]},{"url":"https://bugzilla.suse.com/1240998","tags":["report"]},{"url":"https://bugzilla.suse.com/1241166","tags":["report"]},{"url":"https://bugzilla.suse.com/1241200","tags":["report"]},{"url":"https://bugzilla.suse.com/1241345","tags":["report"]},{"url":"https://bugzilla.suse.com/1242086","tags":["report"]},{"url":"https://bugzilla.suse.com/1242414","tags":["report"]},{"url":"https://bugzilla.suse.com/1242837","tags":["report"]},{"url":"https://bugzilla.suse.com/1242960","tags":["report"]},{"url":"https://bugzilla.suse.com/1242965","tags":["report"]},{"url":"https://bugzilla.suse.com/1242993","tags":["report"]},{"url":"https://bugzilla.suse.com/1243042","tags":["report"]},{"url":"https://bugzilla.suse.com/1243068","tags":["report"]},{"url":"https://bugzilla.suse.com/1243100","tags":["report"]},{"url":"https://bugzilla.suse.com/1243479","tags":["report"]},{"url":"https://bugzilla.suse.com/1243669","tags":["report"]},{"url":"https://bugzilla.suse.com/1243678","tags":["report"]},{"url":"https://bugzilla.suse.com/1243806","tags":["report"]},{"url":"https://bugzilla.suse.com/1244309","tags":["report"]},{"url":"https://bugzilla.suse.com/1244457","tags":["report"]},{"url":"https://bugzilla.suse.com/1244735","tags":["report"]},{"url":"https://bugzilla.suse.com/1244749","tags":["report"]},{"url":"https://bugzilla.suse.com/1244750","tags":["report"]},{"url":"https://bugzilla.suse.com/1244792","tags":["report"]},{"url":"https://bugzilla.suse.com/1244801","tags":["report"]},{"url":"https://bugzilla.suse.com/1245084","tags":["report"]},{"url":"https://bugzilla.suse.com/1245151","tags":["report"]},{"url":"https://bugzilla.suse.com/1245201","tags":["report"]},{"url":"https://bugzilla.suse.com/1245202","tags":["report"]},{"url":"https://bugzilla.suse.com/1245216","tags":["report"]},{"url":"https://bugzilla.suse.com/1245260","tags":["report"]},{"url":"https://bugzilla.suse.com/1245431","tags":["report"]},{"url":"https://bugzilla.suse.com/1245440","tags":["report"]},{"url":"https://bugzilla.suse.com/1245457","tags":["report"]},{"url":"https://bugzilla.suse.com/1245498","tags":["report"]},{"url":"https://bugzilla.suse.com/1245499","tags":["report"]},{"url":"https://bugzilla.suse.com/1245504","tags":["report"]},{"url":"https://bugzilla.suse.com/1245506","tags":["report"]},{"url":"https://bugzilla.suse.com/1245508","tags":["report"]},{"url":"https://bugzilla.suse.com/1245510","tags":["report"]},{"url":"https://bugzilla.suse.com/1245540","tags":["report"]},{"url":"https://bugzilla.suse.com/1245598","tags":["report"]},{"url":"https://bugzilla.suse.com/1245599","tags":["report"]},{"url":"https://bugzilla.suse.com/1245621","tags":["report"]},{"url":"https://bugzilla.suse.com/1245646","tags":["report"]},{"url":"https://bugzilla.suse.com/1245647","tags":["report"]},{"url":"https://bugzilla.suse.com/1245649","tags":["report"]},{"url":"https://bugzilla.suse.com/1245650","tags":["report"]},{"url":"https://bugzilla.suse.com/1245654","tags":["report"]},{"url":"https://bugzilla.suse.com/1245658","tags":["report"]},{"url":"https://bugzilla.suse.com/1245660","tags":["report"]},{"url":"https://bugzilla.suse.com/1245664","tags":["report"]},{"url":"https://bugzilla.suse.com/1245665","tags":["report"]},{"url":"https://bugzilla.suse.com/1245666","tags":["report"]},{"url":"https://bugzilla.suse.com/1245668","tags":["report"]},{"url":"https://bugzilla.suse.com/1245669","tags":["report"]},{"url":"https://bugzilla.suse.com/1245670","tags":["report"]},{"url":"https://bugzilla.suse.com/1245671","tags":["report"]},{"url":"https://bugzilla.suse.com/1245675","tags":["report"]},{"url":"https://bugzilla.suse.com/1245676","tags":["report"]},{"url":"https://bugzilla.suse.com/1245677","tags":["report"]},{"url":"https://bugzilla.suse.com/1245679","tags":["report"]},{"url":"https://bugzilla.suse.com/1245682","tags":["report"]},{"url":"https://bugzilla.suse.com/1245683","tags":["report"]},{"url":"https://bugzilla.suse.com/1245684","tags":["report"]},{"url":"https://bugzilla.suse.com/1245686","tags":["report"]},{"url":"https://bugzilla.suse.com/1245688","tags":["report"]},{"url":"https://bugzilla.suse.com/1245689","tags":["report"]},{"url":"https://bugzilla.suse.com/1245690","tags":["report"]},{"url":"https://bugzilla.suse.com/1245691","tags":["report"]},{"url":"https://bugzilla.suse.com/1245695","tags":["report"]},{"url":"https://bugzilla.suse.com/1245705","tags":["report"]},{"url":"https://bugzilla.suse.com/1245708","tags":["report"]},{"url":"https://bugzilla.suse.com/1245711","tags":["report"]},{"url":"https://bugzilla.suse.com/1245713","tags":["report"]},{"url":"https://bugzilla.suse.com/1245714","tags":["report"]},{"url":"https://bugzilla.suse.com/1245719","tags":["report"]},{"url":"https://bugzilla.suse.com/1245723","tags":["report"]},{"url":"https://bugzilla.suse.com/1245729","tags":["report"]},{"url":"https://bugzilla.suse.com/1245730","tags":["report"]},{"url":"https://bugzilla.suse.com/1245731","tags":["report"]},{"url":"https://bugzilla.suse.com/1245735","tags":["report"]},{"url":"https://bugzilla.suse.com/1245737","tags":["report"]},{"url":"https://bugzilla.suse.com/1245744","tags":["report"]},{"url":"https://bugzilla.suse.com/1245745","tags":["report"]},{"url":"https://bugzilla.suse.com/1245746","tags":["report"]},{"url":"https://bugzilla.suse.com/1245747","tags":["report"]},{"url":"https://bugzilla.suse.com/1245748","tags":["report"]},{"url":"https://bugzilla.suse.com/1245749","tags":["report"]},{"url":"https://bugzilla.suse.com/1245750","tags":["report"]},{"url":"https://bugzilla.suse.com/1245751","tags":["report"]},{"url":"https://bugzilla.suse.com/1245752","tags":["report"]},{"url":"https://bugzilla.suse.com/1245757","tags":["report"]},{"url":"https://bugzilla.suse.com/1245758","tags":["report"]},{"url":"https://bugzilla.suse.com/1245765","tags":["report"]},{"url":"https://bugzilla.suse.com/1245768","tags":["report"]},{"url":"https://bugzilla.suse.com/1245769","tags":["report"]},{"url":"https://bugzilla.suse.com/1245777","tags":["report"]},{"url":"https://bugzilla.suse.com/1245781","tags":["report"]},{"url":"https://bugzilla.suse.com/1245789","tags":["report"]},{"url":"https://bugzilla.suse.com/1245812","tags":["report"]},{"url":"https://bugzilla.suse.com/1245937","tags":["report"]},{"url":"https://bugzilla.suse.com/1245945","tags":["report"]},{"url":"https://bugzilla.suse.com/1245951","tags":["report"]},{"url":"https://bugzilla.suse.com/1245952","tags":["report"]},{"url":"https://bugzilla.suse.com/1245954","tags":["report"]},{"url":"https://bugzilla.suse.com/1245955","tags":["report"]},{"url":"https://bugzilla.suse.com/1245957","tags":["report"]},{"url":"https://bugzilla.suse.com/1245966","tags":["report"]},{"url":"https://bugzilla.suse.com/1245970","tags":["report"]},{"url":"https://bugzilla.suse.com/1245976","tags":["report"]},{"url":"https://bugzilla.suse.com/1245980","tags":["report"]},{"url":"https://bugzilla.suse.com/1245983","tags":["report"]},{"url":"https://bugzilla.suse.com/1245986","tags":["report"]},{"url":"https://bugzilla.suse.com/1246000","tags":["report"]},{"url":"https://bugzilla.suse.com/1246002","tags":["report"]},{"url":"https://bugzilla.suse.com/1246006","tags":["report"]},{"url":"https://bugzilla.suse.com/1246008","tags":["report"]},{"url":"https://bugzilla.suse.com/1246020","tags":["report"]},{"url":"https://bugzilla.suse.com/1246023","tags":["report"]},{"url":"https://bugzilla.suse.com/1246029","tags":["report"]},{"url":"https://bugzilla.suse.com/1246031","tags":["report"]},{"url":"https://bugzilla.suse.com/1246037","tags":["report"]},{"url":"https://bugzilla.suse.com/1246041","tags":["report"]},{"url":"https://bugzilla.suse.com/1246042","tags":["report"]},{"url":"https://bugzilla.suse.com/1246044","tags":["report"]},{"url":"https://bugzilla.suse.com/1246045","tags":["report"]},{"url":"https://bugzilla.suse.com/1246047","tags":["report"]},{"url":"https://bugzilla.suse.com/1246049","tags":["report"]},{"url":"https://bugzilla.suse.com/1246050","tags":["report"]},{"url":"https://bugzilla.suse.com/1246055","tags":["report"]},{"url":"https://bugzilla.suse.com/1246073","tags":["report"]},{"url":"https://bugzilla.suse.com/1246093","tags":["report"]},{"url":"https://bugzilla.suse.com/1246098","tags":["report"]},{"url":"https://bugzilla.suse.com/1246109","tags":["report"]},{"url":"https://bugzilla.suse.com/1246113","tags":["report"]},{"url":"https://bugzilla.suse.com/1246122","tags":["report"]},{"url":"https://bugzilla.suse.com/1246125","tags":["report"]},{"url":"https://bugzilla.suse.com/1246134","tags":["report"]},{"url":"https://bugzilla.suse.com/1246171","tags":["report"]},{"url":"https://bugzilla.suse.com/1246173","tags":["report"]},{"url":"https://bugzilla.suse.com/1246178","tags":["report"]},{"url":"https://bugzilla.suse.com/1246179","tags":["report"]},{"url":"https://bugzilla.suse.com/1246182","tags":["report"]},{"url":"https://bugzilla.suse.com/1246183","tags":["report"]},{"url":"https://bugzilla.suse.com/1246186","tags":["report"]},{"url":"https://bugzilla.suse.com/1246188","tags":["report"]},{"url":"https://bugzilla.suse.com/1246195","tags":["report"]},{"url":"https://bugzilla.suse.com/1246203","tags":["report"]},{"url":"https://bugzilla.suse.com/1246212","tags":["report"]},{"url":"https://bugzilla.suse.com/1246217","tags":["report"]},{"url":"https://bugzilla.suse.com/1246220","tags":["report"]},{"url":"https://bugzilla.suse.com/1246236","tags":["report"]},{"url":"https://bugzilla.suse.com/1246240","tags":["report"]},{"url":"https://bugzilla.suse.com/1246243","tags":["report"]},{"url":"https://bugzilla.suse.com/1246244","tags":["report"]},{"url":"https://bugzilla.suse.com/1246246","tags":["report"]},{"url":"https://bugzilla.suse.com/1246249","tags":["report"]},{"url":"https://bugzilla.suse.com/1246250","tags":["report"]},{"url":"https://bugzilla.suse.com/1246253","tags":["report"]},{"url":"https://bugzilla.suse.com/1246258","tags":["report"]},{"url":"https://bugzilla.suse.com/1246262","tags":["report"]},{"url":"https://bugzilla.suse.com/1246264","tags":["report"]},{"url":"https://bugzilla.suse.com/1246266","tags":["report"]},{"url":"https://bugzilla.suse.com/1246268","tags":["report"]},{"url":"https://bugzilla.suse.com/1246273","tags":["report"]},{"url":"https://bugzilla.suse.com/1246283","tags":["report"]},{"url":"https://bugzilla.suse.com/1246285","tags":["report"]},{"url":"https://bugzilla.suse.com/1246286","tags":["report"]},{"url":"https://bugzilla.suse.com/1246287","tags":["report"]},{"url":"https://bugzilla.suse.com/1246290","tags":["report"]},{"url":"https://bugzilla.suse.com/1246292","tags":["report"]},{"url":"https://bugzilla.suse.com/1246293","tags":["report"]},{"url":"https://bugzilla.suse.com/1246295","tags":["report"]},{"url":"https://bugzilla.suse.com/1246297","tags":["report"]},{"url":"https://bugzilla.suse.com/1246333","tags":["report"]},{"url":"https://bugzilla.suse.com/1246334","tags":["report"]},{"url":"https://bugzilla.suse.com/1246337","tags":["report"]},{"url":"https://bugzilla.suse.com/1246342","tags":["report"]},{"url":"https://bugzilla.suse.com/1246349","tags":["report"]},{"url":"https://bugzilla.suse.com/1246354","tags":["report"]},{"url":"https://bugzilla.suse.com/1246358","tags":["report"]},{"url":"https://bugzilla.suse.com/1246361","tags":["report"]},{"url":"https://bugzilla.suse.com/1246364","tags":["report"]},{"url":"https://bugzilla.suse.com/1246370","tags":["report"]},{"url":"https://bugzilla.suse.com/1246375","tags":["report"]},{"url":"https://bugzilla.suse.com/1246384","tags":["report"]},{"url":"https://bugzilla.suse.com/1246385","tags":["report"]},{"url":"https://bugzilla.suse.com/1246386","tags":["report"]},{"url":"https://bugzilla.suse.com/1246387","tags":["report"]},{"url":"https://bugzilla.suse.com/1246438","tags":["report"]},{"url":"https://bugzilla.suse.com/1246443","tags":["report"]},{"url":"https://bugzilla.suse.com/1246449","tags":["report"]},{"url":"https://bugzilla.suse.com/1246453","tags":["report"]},{"url":"https://bugzilla.suse.com/1246473","tags":["report"]},{"url":"https://bugzilla.suse.com/1246490","tags":["report"]},{"url":"https://bugzilla.suse.com/1246506","tags":["report"]},{"url":"https://bugzilla.suse.com/1246547","tags":["report"]},{"url":"https://bugzilla.suse.com/1246644","tags":["report"]},{"url":"https://bugzilla.suse.com/1246777","tags":["report"]},{"url":"https://bugzilla.suse.com/1246781","tags":["report"]},{"url":"https://bugzilla.suse.com/1246870","tags":["report"]},{"url":"https://bugzilla.suse.com/1246879","tags":["report"]},{"url":"https://bugzilla.suse.com/1246911","tags":["report"]},{"url":"https://bugzilla.suse.com/1247018","tags":["report"]},{"url":"https://bugzilla.suse.com/1247021","tags":["report"]},{"url":"https://bugzilla.suse.com/1247023","tags":["report"]},{"url":"https://bugzilla.suse.com/1247028","tags":["report"]},{"url":"https://bugzilla.suse.com/1247031","tags":["report"]},{"url":"https://bugzilla.suse.com/1247033","tags":["report"]},{"url":"https://bugzilla.suse.com/1247035","tags":["report"]},{"url":"https://bugzilla.suse.com/1247061","tags":["report"]},{"url":"https://bugzilla.suse.com/1247062","tags":["report"]},{"url":"https://bugzilla.suse.com/1247064","tags":["report"]},{"url":"https://bugzilla.suse.com/1247079","tags":["report"]},{"url":"https://bugzilla.suse.com/1247089","tags":["report"]},{"url":"https://bugzilla.suse.com/1247091","tags":["report"]},{"url":"https://bugzilla.suse.com/1247097","tags":["report"]},{"url":"https://bugzilla.suse.com/1247098","tags":["report"]},{"url":"https://bugzilla.suse.com/1247101","tags":["report"]},{"url":"https://bugzilla.suse.com/1247103","tags":["report"]},{"url":"https://bugzilla.suse.com/1247104","tags":["report"]},{"url":"https://bugzilla.suse.com/1247113","tags":["report"]},{"url":"https://bugzilla.suse.com/1247118","tags":["report"]},{"url":"https://bugzilla.suse.com/1247123","tags":["report"]},{"url":"https://bugzilla.suse.com/1247125","tags":["report"]},{"url":"https://bugzilla.suse.com/1247128","tags":["report"]},{"url":"https://bugzilla.suse.com/1247132","tags":["report"]},{"url":"https://bugzilla.suse.com/1247138","tags":["report"]},{"url":"https://bugzilla.suse.com/1247141","tags":["report"]},{"url":"https://bugzilla.suse.com/1247143","tags":["report"]},{"url":"https://bugzilla.suse.com/1247145","tags":["report"]},{"url":"https://bugzilla.suse.com/1247146","tags":["report"]},{"url":"https://bugzilla.suse.com/1247147","tags":["report"]},{"url":"https://bugzilla.suse.com/1247149","tags":["report"]},{"url":"https://bugzilla.suse.com/1247150","tags":["report"]},{"url":"https://bugzilla.suse.com/1247151","tags":["report"]},{"url":"https://bugzilla.suse.com/1247152","tags":["report"]},{"url":"https://bugzilla.suse.com/1247153","tags":["report"]},{"url":"https://bugzilla.suse.com/1247154","tags":["report"]},{"url":"https://bugzilla.suse.com/1247156","tags":["report"]},{"url":"https://bugzilla.suse.com/1247160","tags":["report"]},{"url":"https://bugzilla.suse.com/1247164","tags":["report"]},{"url":"https://bugzilla.suse.com/1247169","tags":["report"]},{"url":"https://bugzilla.suse.com/1247170","tags":["report"]},{"url":"https://bugzilla.suse.com/1247171","tags":["report"]},{"url":"https://bugzilla.suse.com/1247172","tags":["report"]},{"url":"https://bugzilla.suse.com/1247174","tags":["report"]},{"url":"https://bugzilla.suse.com/1247176","tags":["report"]},{"url":"https://bugzilla.suse.com/1247177","tags":["report"]},{"url":"https://bugzilla.suse.com/1247178","tags":["report"]},{"url":"https://bugzilla.suse.com/1247181","tags":["report"]},{"url":"https://bugzilla.suse.com/1247209","tags":["report"]},{"url":"https://bugzilla.suse.com/1247210","tags":["report"]},{"url":"https://bugzilla.suse.com/1247227","tags":["report"]},{"url":"https://bugzilla.suse.com/1247233","tags":["report"]},{"url":"https://bugzilla.suse.com/1247234","tags":["report"]},{"url":"https://bugzilla.suse.com/1247236","tags":["report"]},{"url":"https://bugzilla.suse.com/1247238","tags":["report"]},{"url":"https://bugzilla.suse.com/1247241","tags":["report"]},{"url":"https://bugzilla.suse.com/1247251","tags":["report"]},{"url":"https://bugzilla.suse.com/1247252","tags":["report"]},{"url":"https://bugzilla.suse.com/1247253","tags":["report"]},{"url":"https://bugzilla.suse.com/1247255","tags":["report"]},{"url":"https://bugzilla.suse.com/1247265","tags":["report"]},{"url":"https://bugzilla.suse.com/1247271","tags":["report"]},{"url":"https://bugzilla.suse.com/1247273","tags":["report"]},{"url":"https://bugzilla.suse.com/1247274","tags":["report"]},{"url":"https://bugzilla.suse.com/1247276","tags":["report"]},{"url":"https://bugzilla.suse.com/1247277","tags":["report"]},{"url":"https://bugzilla.suse.com/1247278","tags":["report"]},{"url":"https://bugzilla.suse.com/1247279","tags":["report"]},{"url":"https://bugzilla.suse.com/1247282","tags":["report"]},{"url":"https://bugzilla.suse.com/1247284","tags":["report"]},{"url":"https://bugzilla.suse.com/1247285","tags":["report"]},{"url":"https://bugzilla.suse.com/1247288","tags":["report"]},{"url":"https://bugzilla.suse.com/1247289","tags":["report"]},{"url":"https://bugzilla.suse.com/1247293","tags":["report"]},{"url":"https://bugzilla.suse.com/1247308","tags":["report"]},{"url":"https://bugzilla.suse.com/1247311","tags":["report"]},{"url":"https://bugzilla.suse.com/1247314","tags":["report"]},{"url":"https://bugzilla.suse.com/1247317","tags":["report"]},{"url":"https://bugzilla.suse.com/1247347","tags":["report"]},{"url":"https://bugzilla.suse.com/1247348","tags":["report"]},{"url":"https://bugzilla.suse.com/1247349","tags":["report"]},{"url":"https://bugzilla.suse.com/1247374","tags":["report"]},{"url":"https://bugzilla.suse.com/1247437","tags":["report"]},{"url":"https://bugzilla.suse.com/1247450","tags":["report"]},{"url":"https://bugzilla.suse.com/1247712","tags":["report"]},{"url":"https://bugzilla.suse.com/1247831","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-44963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38498","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502923-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1139073","tags":["report"]},{"url":"https://bugzilla.suse.com/1210025","tags":["report"]},{"url":"https://bugzilla.suse.com/1211226","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1218184","tags":["report"]},{"url":"https://bugzilla.suse.com/1220112","tags":["report"]},{"url":"https://bugzilla.suse.com/1223008","tags":["report"]},{"url":"https://bugzilla.suse.com/1226498","tags":["report"]},{"url":"https://bugzilla.suse.com/1228557","tags":["report"]},{"url":"https://bugzilla.suse.com/1228854","tags":["report"]},{"url":"https://bugzilla.suse.com/1229491","tags":["report"]},{"url":"https://bugzilla.suse.com/1232504","tags":["report"]},{"url":"https://bugzilla.suse.com/1232882","tags":["report"]},{"url":"https://bugzilla.suse.com/1235490","tags":["report"]},{"url":"https://bugzilla.suse.com/1235728","tags":["report"]},{"url":"https://bugzilla.suse.com/1235968","tags":["report"]},{"url":"https://bugzilla.suse.com/1236208","tags":["report"]},{"url":"https://bugzilla.suse.com/1237312","tags":["report"]},{"url":"https://bugzilla.suse.com/1237913","tags":["report"]},{"url":"https://bugzilla.suse.com/1238212","tags":["report"]},{"url":"https://bugzilla.suse.com/1238859","tags":["report"]},{"url":"https://bugzilla.suse.com/1238982","tags":["report"]},{"url":"https://bugzilla.suse.com/1239470","tags":["report"]},{"url":"https://bugzilla.suse.com/1239925","tags":["report"]},{"url":"https://bugzilla.suse.com/1240180","tags":["report"]},{"url":"https://bugzilla.suse.com/1240577","tags":["report"]},{"url":"https://bugzilla.suse.com/1240610","tags":["report"]},{"url":"https://bugzilla.suse.com/1240686","tags":["report"]},{"url":"https://bugzilla.suse.com/1240723","tags":["report"]},{"url":"https://bugzilla.suse.com/1240814","tags":["report"]},{"url":"https://bugzilla.suse.com/1240823","tags":["report"]},{"url":"https://bugzilla.suse.com/1240866","tags":["report"]},{"url":"https://bugzilla.suse.com/1241278","tags":["report"]},{"url":"https://bugzilla.suse.com/1241340","tags":["report"]},{"url":"https://bugzilla.suse.com/1241414","tags":["report"]},{"url":"https://bugzilla.suse.com/1241457","tags":["report"]},{"url":"https://bugzilla.suse.com/1241492","tags":["report"]},{"url":"https://bugzilla.suse.com/1241519","tags":["report"]},{"url":"https://bugzilla.suse.com/1241537","tags":["report"]},{"url":"https://bugzilla.suse.com/1241538","tags":["report"]},{"url":"https://bugzilla.suse.com/1241544","tags":["report"]},{"url":"https://bugzilla.suse.com/1241572","tags":["report"]},{"url":"https://bugzilla.suse.com/1241576","tags":["report"]},{"url":"https://bugzilla.suse.com/1241590","tags":["report"]},{"url":"https://bugzilla.suse.com/1241592","tags":["report"]},{"url":"https://bugzilla.suse.com/1241595","tags":["report"]},{"url":"https://bugzilla.suse.com/1241617","tags":["report"]},{"url":"https://bugzilla.suse.com/1241625","tags":["report"]},{"url":"https://bugzilla.suse.com/1241635","tags":["report"]},{"url":"https://bugzilla.suse.com/1241644","tags":["report"]},{"url":"https://bugzilla.suse.com/1241654","tags":["report"]},{"url":"https://bugzilla.suse.com/1242035","tags":["report"]},{"url":"https://bugzilla.suse.com/1242044","tags":["report"]},{"url":"https://bugzilla.suse.com/1242163","tags":["report"]},{"url":"https://bugzilla.suse.com/1242343","tags":["report"]},{"url":"https://bugzilla.suse.com/1242501","tags":["report"]},{"url":"https://bugzilla.suse.com/1242504","tags":["report"]},{"url":"https://bugzilla.suse.com/1242512","tags":["report"]},{"url":"https://bugzilla.suse.com/1242514","tags":["report"]},{"url":"https://bugzilla.suse.com/1242515","tags":["report"]},{"url":"https://bugzilla.suse.com/1242520","tags":["report"]},{"url":"https://bugzilla.suse.com/1242521","tags":["report"]},{"url":"https://bugzilla.suse.com/1242524","tags":["report"]},{"url":"https://bugzilla.suse.com/1242529","tags":["report"]},{"url":"https://bugzilla.suse.com/1242530","tags":["report"]},{"url":"https://bugzilla.suse.com/1242531","tags":["report"]},{"url":"https://bugzilla.suse.com/1242532","tags":["report"]},{"url":"https://bugzilla.suse.com/1242556","tags":["report"]},{"url":"https://bugzilla.suse.com/1242559","tags":["report"]},{"url":"https://bugzilla.suse.com/1242563","tags":["report"]},{"url":"https://bugzilla.suse.com/1242564","tags":["report"]},{"url":"https://bugzilla.suse.com/1242565","tags":["report"]},{"url":"https://bugzilla.suse.com/1242566","tags":["report"]},{"url":"https://bugzilla.suse.com/1242567","tags":["report"]},{"url":"https://bugzilla.suse.com/1242568","tags":["report"]},{"url":"https://bugzilla.suse.com/1242569","tags":["report"]},{"url":"https://bugzilla.suse.com/1242573","tags":["report"]},{"url":"https://bugzilla.suse.com/1242574","tags":["report"]},{"url":"https://bugzilla.suse.com/1242575","tags":["report"]},{"url":"https://bugzilla.suse.com/1242578","tags":["report"]},{"url":"https://bugzilla.suse.com/1242584","tags":["report"]},{"url":"https://bugzilla.suse.com/1242587","tags":["report"]},{"url":"https://bugzilla.suse.com/1242591","tags":["report"]},{"url":"https://bugzilla.suse.com/1242709","tags":["report"]},{"url":"https://bugzilla.suse.com/1242725","tags":["report"]},{"url":"https://bugzilla.suse.com/1242727","tags":["report"]},{"url":"https://bugzilla.suse.com/1242758","tags":["report"]},{"url":"https://bugzilla.suse.com/1242760","tags":["report"]},{"url":"https://bugzilla.suse.com/1242761","tags":["report"]},{"url":"https://bugzilla.suse.com/1242764","tags":["report"]},{"url":"https://bugzilla.suse.com/1242766","tags":["report"]},{"url":"https://bugzilla.suse.com/1242770","tags":["report"]},{"url":"https://bugzilla.suse.com/1242781","tags":["report"]},{"url":"https://bugzilla.suse.com/1242782","tags":["report"]},{"url":"https://bugzilla.suse.com/1242785","tags":["report"]},{"url":"https://bugzilla.suse.com/1242792","tags":["report"]},{"url":"https://bugzilla.suse.com/1242846","tags":["report"]},{"url":"https://bugzilla.suse.com/1242849","tags":["report"]},{"url":"https://bugzilla.suse.com/1242850","tags":["report"]},{"url":"https://bugzilla.suse.com/1242871","tags":["report"]},{"url":"https://bugzilla.suse.com/1242873","tags":["report"]},{"url":"https://bugzilla.suse.com/1242906","tags":["report"]},{"url":"https://bugzilla.suse.com/1242907","tags":["report"]},{"url":"https://bugzilla.suse.com/1242908","tags":["report"]},{"url":"https://bugzilla.suse.com/1242930","tags":["report"]},{"url":"https://bugzilla.suse.com/1242940","tags":["report"]},{"url":"https://bugzilla.suse.com/1242945","tags":["report"]},{"url":"https://bugzilla.suse.com/1242946","tags":["report"]},{"url":"https://bugzilla.suse.com/1242948","tags":["report"]},{"url":"https://bugzilla.suse.com/1242949","tags":["report"]},{"url":"https://bugzilla.suse.com/1242953","tags":["report"]},{"url":"https://bugzilla.suse.com/1242954","tags":["report"]},{"url":"https://bugzilla.suse.com/1242955","tags":["report"]},{"url":"https://bugzilla.suse.com/1242957","tags":["report"]},{"url":"https://bugzilla.suse.com/1242959","tags":["report"]},{"url":"https://bugzilla.suse.com/1242961","tags":["report"]},{"url":"https://bugzilla.suse.com/1242973","tags":["report"]},{"url":"https://bugzilla.suse.com/1242974","tags":["report"]},{"url":"https://bugzilla.suse.com/1242977","tags":["report"]},{"url":"https://bugzilla.suse.com/1242982","tags":["report"]},{"url":"https://bugzilla.suse.com/1242990","tags":["report"]},{"url":"https://bugzilla.suse.com/1243000","tags":["report"]},{"url":"https://bugzilla.suse.com/1243006","tags":["report"]},{"url":"https://bugzilla.suse.com/1243011","tags":["report"]},{"url":"https://bugzilla.suse.com/1243015","tags":["report"]},{"url":"https://bugzilla.suse.com/1243049","tags":["report"]},{"url":"https://bugzilla.suse.com/1243051","tags":["report"]},{"url":"https://bugzilla.suse.com/1243060","tags":["report"]},{"url":"https://bugzilla.suse.com/1243074","tags":["report"]},{"url":"https://bugzilla.suse.com/1243076","tags":["report"]},{"url":"https://bugzilla.suse.com/1243082","tags":["report"]},{"url":"https://bugzilla.suse.com/1243330","tags":["report"]},{"url":"https://bugzilla.suse.com/1243342","tags":["report"]},{"url":"https://bugzilla.suse.com/1243456","tags":["report"]},{"url":"https://bugzilla.suse.com/1243467","tags":["report"]},{"url":"https://bugzilla.suse.com/1243469","tags":["report"]},{"url":"https://bugzilla.suse.com/1243470","tags":["report"]},{"url":"https://bugzilla.suse.com/1243471","tags":["report"]},{"url":"https://bugzilla.suse.com/1243472","tags":["report"]},{"url":"https://bugzilla.suse.com/1243473","tags":["report"]},{"url":"https://bugzilla.suse.com/1243475","tags":["report"]},{"url":"https://bugzilla.suse.com/1243476","tags":["report"]},{"url":"https://bugzilla.suse.com/1243480","tags":["report"]},{"url":"https://bugzilla.suse.com/1243506","tags":["report"]},{"url":"https://bugzilla.suse.com/1243509","tags":["report"]},{"url":"https://bugzilla.suse.com/1243511","tags":["report"]},{"url":"https://bugzilla.suse.com/1243515","tags":["report"]},{"url":"https://bugzilla.suse.com/1243516","tags":["report"]},{"url":"https://bugzilla.suse.com/1243517","tags":["report"]},{"url":"https://bugzilla.suse.com/1243522","tags":["report"]},{"url":"https://bugzilla.suse.com/1243523","tags":["report"]},{"url":"https://bugzilla.suse.com/1243524","tags":["report"]},{"url":"https://bugzilla.suse.com/1243528","tags":["report"]},{"url":"https://bugzilla.suse.com/1243529","tags":["report"]},{"url":"https://bugzilla.suse.com/1243530","tags":["report"]},{"url":"https://bugzilla.suse.com/1243534","tags":["report"]},{"url":"https://bugzilla.suse.com/1243536","tags":["report"]},{"url":"https://bugzilla.suse.com/1243537","tags":["report"]},{"url":"https://bugzilla.suse.com/1243538","tags":["report"]},{"url":"https://bugzilla.suse.com/1243540","tags":["report"]},{"url":"https://bugzilla.suse.com/1243542","tags":["report"]},{"url":"https://bugzilla.suse.com/1243543","tags":["report"]},{"url":"https://bugzilla.suse.com/1243544","tags":["report"]},{"url":"https://bugzilla.suse.com/1243545","tags":["report"]},{"url":"https://bugzilla.suse.com/1243551","tags":["report"]},{"url":"https://bugzilla.suse.com/1243559","tags":["report"]},{"url":"https://bugzilla.suse.com/1243560","tags":["report"]},{"url":"https://bugzilla.suse.com/1243562","tags":["report"]},{"url":"https://bugzilla.suse.com/1243567","tags":["report"]},{"url":"https://bugzilla.suse.com/1243571","tags":["report"]},{"url":"https://bugzilla.suse.com/1243572","tags":["report"]},{"url":"https://bugzilla.suse.com/1243573","tags":["report"]},{"url":"https://bugzilla.suse.com/1243574","tags":["report"]},{"url":"https://bugzilla.suse.com/1243575","tags":["report"]},{"url":"https://bugzilla.suse.com/1243589","tags":["report"]},{"url":"https://bugzilla.suse.com/1243620","tags":["report"]},{"url":"https://bugzilla.suse.com/1243621","tags":["report"]},{"url":"https://bugzilla.suse.com/1243624","tags":["report"]},{"url":"https://bugzilla.suse.com/1243625","tags":["report"]},{"url":"https://bugzilla.suse.com/1243626","tags":["report"]},{"url":"https://bugzilla.suse.com/1243627","tags":["report"]},{"url":"https://bugzilla.suse.com/1243628","tags":["report"]},{"url":"https://bugzilla.suse.com/1243649","tags":["report"]},{"url":"https://bugzilla.suse.com/1243659","tags":["report"]},{"url":"https://bugzilla.suse.com/1243660","tags":["report"]},{"url":"https://bugzilla.suse.com/1243664","tags":["report"]},{"url":"https://bugzilla.suse.com/1243698","tags":["report"]},{"url":"https://bugzilla.suse.com/1243774","tags":["report"]},{"url":"https://bugzilla.suse.com/1243782","tags":["report"]},{"url":"https://bugzilla.suse.com/1243823","tags":["report"]},{"url":"https://bugzilla.suse.com/1243827","tags":["report"]},{"url":"https://bugzilla.suse.com/1243832","tags":["report"]},{"url":"https://bugzilla.suse.com/1243836","tags":["report"]},{"url":"https://bugzilla.suse.com/1243847","tags":["report"]},{"url":"https://bugzilla.suse.com/1244100","tags":["report"]},{"url":"https://bugzilla.suse.com/1244145","tags":["report"]},{"url":"https://bugzilla.suse.com/1244172","tags":["report"]},{"url":"https://bugzilla.suse.com/1244176","tags":["report"]},{"url":"https://bugzilla.suse.com/1244229","tags":["report"]},{"url":"https://bugzilla.suse.com/1244234","tags":["report"]},{"url":"https://bugzilla.suse.com/1244241","tags":["report"]},{"url":"https://bugzilla.suse.com/1244261","tags":["report"]},{"url":"https://bugzilla.suse.com/1244274","tags":["report"]},{"url":"https://bugzilla.suse.com/1244275","tags":["report"]},{"url":"https://bugzilla.suse.com/1244277","tags":["report"]},{"url":"https://bugzilla.suse.com/1244313","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1244626","tags":["report"]},{"url":"https://bugzilla.suse.com/1244725","tags":["report"]},{"url":"https://bugzilla.suse.com/1244727","tags":["report"]},{"url":"https://bugzilla.suse.com/1244729","tags":["report"]},{"url":"https://bugzilla.suse.com/1244731","tags":["report"]},{"url":"https://bugzilla.suse.com/1244732","tags":["report"]},{"url":"https://bugzilla.suse.com/1244736","tags":["report"]},{"url":"https://bugzilla.suse.com/1244737","tags":["report"]},{"url":"https://bugzilla.suse.com/1244738","tags":["report"]},{"url":"https://bugzilla.suse.com/1244739","tags":["report"]},{"url":"https://bugzilla.suse.com/1244743","tags":["report"]},{"url":"https://bugzilla.suse.com/1244746","tags":["report"]},{"url":"https://bugzilla.suse.com/1244759","tags":["report"]},{"url":"https://bugzilla.suse.com/1244789","tags":["report"]},{"url":"https://bugzilla.suse.com/1244862","tags":["report"]},{"url":"https://bugzilla.suse.com/1244906","tags":["report"]},{"url":"https://bugzilla.suse.com/1244938","tags":["report"]},{"url":"https://bugzilla.suse.com/1244995","tags":["report"]},{"url":"https://bugzilla.suse.com/1244996","tags":["report"]},{"url":"https://bugzilla.suse.com/1244999","tags":["report"]},{"url":"https://bugzilla.suse.com/1245001","tags":["report"]},{"url":"https://bugzilla.suse.com/1245003","tags":["report"]},{"url":"https://bugzilla.suse.com/1245004","tags":["report"]},{"url":"https://bugzilla.suse.com/1245025","tags":["report"]},{"url":"https://bugzilla.suse.com/1245042","tags":["report"]},{"url":"https://bugzilla.suse.com/1245046","tags":["report"]},{"url":"https://bugzilla.suse.com/1245078","tags":["report"]},{"url":"https://bugzilla.suse.com/1245081","tags":["report"]},{"url":"https://bugzilla.suse.com/1245082","tags":["report"]},{"url":"https://bugzilla.suse.com/1245083","tags":["report"]},{"url":"https://bugzilla.suse.com/1245155","tags":["report"]},{"url":"https://bugzilla.suse.com/1245183","tags":["report"]},{"url":"https://bugzilla.suse.com/1245193","tags":["report"]},{"url":"https://bugzilla.suse.com/1245210","tags":["report"]},{"url":"https://bugzilla.suse.com/1245217","tags":["report"]},{"url":"https://bugzilla.suse.com/1245225","tags":["report"]},{"url":"https://bugzilla.suse.com/1245226","tags":["report"]},{"url":"https://bugzilla.suse.com/1245228","tags":["report"]},{"url":"https://bugzilla.suse.com/1245455","tags":["report"]},{"url":"https://bugzilla.suse.com/1247243","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-43869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-57982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37796","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37875","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40014","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502969-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502996-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202502997-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1227082","tags":["report"]},{"url":"https://bugzilla.suse.com/1246695","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-39298","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503011-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1232089","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49996","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503023-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520577-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520586-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520601-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520602-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-38162","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-38162","tags":["report"]},{"url":"https://git.kernel.org/linus/4c5c6aa9967dbe55bd017bb509885928d0f31206","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7769-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7770-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7771-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7769-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7769-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7789-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7789-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8052-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-7","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-8","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8052-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8074-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8074-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8126-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-38003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-38162","title":"netfilter: nft_set_pipapo: prevent overflow in lookup table allocation","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T08:36:03.731Z","modified":"2026-11-10T12:36:15.252Z","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"}],"updated_at":"2026-11-10T13:38:44.039016Z"}],"euvd":[{"id":"EUVD-2025-19782","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T08:36:03Z","modified":"2026-11-10T12:36:15Z","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-10T13:21:00.505372Z"}],"ghsa":[{"id":"GHSA-r97f-5wrg-fmv7","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo:...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:30:35Z","modified":"2026-10-15T03:35:54Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:13:33.329835Z"}],"nvd":[{"id":"CVE-2025-38162","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:15:31.617Z","modified":"2026-11-10T13:17:45.887Z","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"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"updated_at":"2026-11-10T16:19:44.5931Z"}],"osv":[{"id":"BELL-CVE-2025-38162","status":"published","published":"2025-07-03T19:47:54.271084Z","modified":"2026-06-25T07:15:28.895735332Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:21.741325Z"},{"id":"CVE-2025-38162","title":"netfilter: nft_set_pipapo: prevent overflow in lookup table allocation","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T08:36:03.731Z","modified":"2026-10-28T02:30:50.939251255Z","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:48.703031Z"},{"id":"DEBIAN-CVE-2025-38162","description":"In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_set_pipapo: prevent overflow in lookup table allocation  When calculating the lookup table size, ensure the following multiplication does not overflow:  - desc-\u003efield_len[] maximum value is U8_MAX multiplied by   NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case. - NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case. - sizeof(unsigned long), from sizeof(*f-\u003elt), lt in   struct nft_pipapo_field.  Then, use check_mul_overflow() to multiply by bucket size and then use check_add_overflow() to the alignment for avx2 (if needed). Finally, add lt_size_check_overflow() helper and use it to consolidate this.  While at it, replace leftover allocation using the GFP_KERNEL to GFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:15:31.617Z","modified":"2026-10-16T09:47:23.619835301Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:46.222864Z"},{"id":"OESA-2026-1303","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\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: eir: Fix possible crashes on eir_create_adv_data\n\neir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER\nwithout checking if that would fit.(CVE-2025-38303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [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:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again\n\nCommit 7ded842b356d (\u0026quot;s390/bpf: Fix bpf_plt pointer arithmetic\u0026quot;) has\naccidentally removed the critical piece of commit c730fce7c70c\n(\u0026quot;s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL\u0026quot;), causing\nintermittent kernel panics in e.g. perf\u0026apos;s on_switch() prog to reappear.\n\nRestore the fix and add a comment.(CVE-2025-38489)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Avoid stack buffer overflow from kernel cmdline\n\nWhile the kernel command line is considered trusted in most environments,\navoid writing 1 byte past the end of \u0026quot;acpiid\u0026quot; if the \u0026quot;str\u0026quot; argument is\nmaximum length.(CVE-2025-38676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - flush misc workqueue during device shutdown\n\nRepeated loading and unloading of a device specific QAT driver, for\nexample qat_4xxx, in a tight loop can lead to a crash due to a\nuse-after-free scenario. This occurs when a power management (PM)\ninterrupt triggers just before the device-specific driver (e.g.,\nqat_4xxx.ko) is unloaded, while the core driver (intel_qat.ko) remains\nloaded.\n\nSince the driver uses a shared workqueue (`qat_misc_wq`) across all\ndevices and owned by intel_qat.ko, a deferred routine from the\ndevice-specific driver may still be pending in the queue. If this\nroutine executes after the driver is unloaded, it can dereference freed\nmemory, resulting in a page fault and kernel crash like the following:\n\n    BUG: unable to handle page fault for address: ffa000002e50a01c\n    #PF: supervisor read access in kernel mode\n    RIP: 0010:pm_bh_handler+0x1d2/0x250 [intel_qat]\n    Call Trace:\n      pm_bh_handler+0x1d2/0x250 [intel_qat]\n      process_one_work+0x171/0x340\n      worker_thread+0x277/0x3a0\n      kthread+0xf0/0x120\n      ret_from_fork+0x2d/0x50\n\nTo prevent this, flush the misc workqueue during device shutdown to\nensure that all pending work items are completed before the driver is\nunloaded.\n\nNote: This approach may slightly increase shutdown latency if the\nworkqueue contains jobs from other devices, but it ensures correctness\nand stability.(CVE-2025-39721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect -\u0026gt;defer_qs_iw_pending from data race\n\nOn kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is\ninvoked within an interrupts-disabled region of code [1], it will invoke\nrcu_read_unlock_special(), which uses an irq-work handler to force the\nsystem to notice when the RCU read-side critical section actually ends.\nThat end won\u0026apos;t happen until interrupts are enabled at the soonest.\n\nIn some kernels, such as those booted with rcutree.use_softirq=y, the\nirq-work handler is used unconditionally.\n\nThe per-CPU rcu_data structure\u0026apos;s -\u0026gt;defer_qs_iw_pending field is\nupdated by the irq-work handler and is both read and updated by\nrcu_read_unlock_special().  This resulted in the following KCSAN splat:\n\n------------------------------------------------------------------------\n\nBUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special\n\nread to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8:\n rcu_read_unlock_special+0x175/0x260\n __rcu_read_unlock+0x92/0xa0\n rt_spin_unlock+0x9b/0xc0\n __local_bh_enable+0x10d/0x170\n __local_bh_enable_ip+0xfb/0x150\n rcu_do_batch+0x595/0xc40\n rcu_cpu_kthread+0x4e9/0x830\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nwrite to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8:\n rcu_preempt_deferred_qs_handler+0x1e/0x30\n irq_work_single+0xaf/0x160\n run_irq_workd+0x91/0xc0\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nno locks held by irq_work/8/88.\nirq event stamp: 200272\nhardirqs last  enabled at (200272): [\u0026lt;ffffffffb0f56121\u0026gt;] finish_task_switch+0x131/0x320\nhardirqs last disabled at (200271): [\u0026lt;ffffffffb25c7859\u0026gt;] __schedule+0x129/0xd70\nsoftirqs last  enabled at (0): [\u0026lt;ffffffffb0ee093f\u0026gt;] copy_process+0x4df/0x1cc0\nsoftirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n\n------------------------------------------------------------------------\n\nThe problem is that irq-work handlers run with interrupts enabled, which\nmeans that rcu_preempt_deferred_qs_handler() could be interrupted,\nand that interrupt handler might contain an RCU read-side critical\nsection, which might invoke rcu_read_unlock_special().  In the strict\nKCSAN mode of operation used by RCU, this constitutes a data race on\nthe -\u0026gt;defer_qs_iw_pending field.\n\nThis commit therefore disables interrupts across the portion of the\nrcu_preempt_deferred_qs_handler() that updates the -\u0026gt;defer_qs_iw_pending\nfield.  This suffices because this handler is not a fast path.(CVE-2025-39749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 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+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: prevent NULL pointer dereference in UTF16 conversion\n\nThere can be a NULL pointer dereference bug here. NULL is passed to\n__cifs_sfu_make_node without checks, which passes it unchecked to\ncifs_strndup_to_utf16, which in turn passes it to\ncifs_local_to_utf16_bytes where \u0026apos;*from\u0026apos; is dereferenced, causing a crash.\n\nThis patch adds a check for NULL \u0026apos;src\u0026apos; in cifs_strndup_to_utf16 and\nreturns NULL early to prevent dereferencing NULL pointer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE(CVE-2025-39838)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix null-deref in agg_dequeue\n\nTo prevent a potential crash in agg_dequeue (net/sched/sch_qfq.c)\nwhen cl-\u0026gt;qdisc-\u0026gt;ops-\u0026gt;peek(cl-\u0026gt;qdisc) returns NULL, we check the return\nvalue before using it, similar to the existing approach in sch_hfsc.c.\n\nTo avoid code duplication, the following changes are made:\n\n1. Changed qdisc_warn_nonwc(include/net/pkt_sched.h) into a static\ninline function.\n\n2. Moved qdisc_peek_len from net/sched/sch_hfsc.c to\ninclude/net/pkt_sched.h so that sch_qfq can reuse it.\n\n3. Applied qdisc_peek_len in agg_dequeue to avoid crashing.(CVE-2025-40083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfs: Don\u0026apos;t leak disconnected dentries on umount\n\nWhen user calls open_by_handle_at() on some inode that is not cached, we\nwill create disconnected dentry for it. If such dentry is a directory,\nexportfs_decode_fh_raw() will then try to connect this dentry to the\ndentry tree through reconnect_path(). It may happen for various reasons\n(such as corrupted fs or race with rename) that the call to\nlookup_one_unlocked() in reconnect_one() will fail to find the dentry we\nare trying to reconnect and instead create a new dentry under the\nparent. Now this dentry will not be marked as disconnected although the\nparent still may well be disconnected (at least in case this\ninconsistency happened because the fs is corrupted and .. doesn\u0026apos;t point\nto the real parent directory). This creates inconsistency in\ndisconnected flags but AFAICS it was mostly harmless. At least until\ncommit f1ee616214cb (\u0026quot;VFS: don\u0026apos;t keep disconnected dentries on d_anon\u0026quot;)\nwhich removed adding of most disconnected dentries to sb-\u0026gt;s_anon list.\nThus after this commit cleanup of disconnected dentries implicitely\nrelies on the fact that dput() will immediately reclaim such dentries.\nHowever when some leaf dentry isn\u0026apos;t marked as disconnected, as in the\nscenario described above, the reclaim doesn\u0026apos;t happen and the dentries\nare \u0026quot;leaked\u0026quot;. Memory reclaim can eventually reclaim them but otherwise\nthey stay in memory and if umount comes first, we hit infamous \u0026quot;Busy\ninodes after unmount\u0026quot; bug. Make sure all dentries created under a\ndisconnected parent are marked as disconnected as well.(CVE-2025-40105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.496570777Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1304","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\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: eir: Fix possible crashes on eir_create_adv_data\n\neir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER\nwithout checking if that would fit.(CVE-2025-38303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [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:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again\n\nCommit 7ded842b356d (\u0026quot;s390/bpf: Fix bpf_plt pointer arithmetic\u0026quot;) has\naccidentally removed the critical piece of commit c730fce7c70c\n(\u0026quot;s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL\u0026quot;), causing\nintermittent kernel panics in e.g. perf\u0026apos;s on_switch() prog to reappear.\n\nRestore the fix and add a comment.(CVE-2025-38489)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Avoid stack buffer overflow from kernel cmdline\n\nWhile the kernel command line is considered trusted in most environments,\navoid writing 1 byte past the end of \u0026quot;acpiid\u0026quot; if the \u0026quot;str\u0026quot; argument is\nmaximum length.(CVE-2025-38676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - flush misc workqueue during device shutdown\n\nRepeated loading and unloading of a device specific QAT driver, for\nexample qat_4xxx, in a tight loop can lead to a crash due to a\nuse-after-free scenario. This occurs when a power management (PM)\ninterrupt triggers just before the device-specific driver (e.g.,\nqat_4xxx.ko) is unloaded, while the core driver (intel_qat.ko) remains\nloaded.\n\nSince the driver uses a shared workqueue (`qat_misc_wq`) across all\ndevices and owned by intel_qat.ko, a deferred routine from the\ndevice-specific driver may still be pending in the queue. If this\nroutine executes after the driver is unloaded, it can dereference freed\nmemory, resulting in a page fault and kernel crash like the following:\n\n    BUG: unable to handle page fault for address: ffa000002e50a01c\n    #PF: supervisor read access in kernel mode\n    RIP: 0010:pm_bh_handler+0x1d2/0x250 [intel_qat]\n    Call Trace:\n      pm_bh_handler+0x1d2/0x250 [intel_qat]\n      process_one_work+0x171/0x340\n      worker_thread+0x277/0x3a0\n      kthread+0xf0/0x120\n      ret_from_fork+0x2d/0x50\n\nTo prevent this, flush the misc workqueue during device shutdown to\nensure that all pending work items are completed before the driver is\nunloaded.\n\nNote: This approach may slightly increase shutdown latency if the\nworkqueue contains jobs from other devices, but it ensures correctness\nand stability.(CVE-2025-39721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect -\u0026gt;defer_qs_iw_pending from data race\n\nOn kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is\ninvoked within an interrupts-disabled region of code [1], it will invoke\nrcu_read_unlock_special(), which uses an irq-work handler to force the\nsystem to notice when the RCU read-side critical section actually ends.\nThat end won\u0026apos;t happen until interrupts are enabled at the soonest.\n\nIn some kernels, such as those booted with rcutree.use_softirq=y, the\nirq-work handler is used unconditionally.\n\nThe per-CPU rcu_data structure\u0026apos;s -\u0026gt;defer_qs_iw_pending field is\nupdated by the irq-work handler and is both read and updated by\nrcu_read_unlock_special().  This resulted in the following KCSAN splat:\n\n------------------------------------------------------------------------\n\nBUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special\n\nread to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8:\n rcu_read_unlock_special+0x175/0x260\n __rcu_read_unlock+0x92/0xa0\n rt_spin_unlock+0x9b/0xc0\n __local_bh_enable+0x10d/0x170\n __local_bh_enable_ip+0xfb/0x150\n rcu_do_batch+0x595/0xc40\n rcu_cpu_kthread+0x4e9/0x830\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nwrite to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8:\n rcu_preempt_deferred_qs_handler+0x1e/0x30\n irq_work_single+0xaf/0x160\n run_irq_workd+0x91/0xc0\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nno locks held by irq_work/8/88.\nirq event stamp: 200272\nhardirqs last  enabled at (200272): [\u0026lt;ffffffffb0f56121\u0026gt;] finish_task_switch+0x131/0x320\nhardirqs last disabled at (200271): [\u0026lt;ffffffffb25c7859\u0026gt;] __schedule+0x129/0xd70\nsoftirqs last  enabled at (0): [\u0026lt;ffffffffb0ee093f\u0026gt;] copy_process+0x4df/0x1cc0\nsoftirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n\n------------------------------------------------------------------------\n\nThe problem is that irq-work handlers run with interrupts enabled, which\nmeans that rcu_preempt_deferred_qs_handler() could be interrupted,\nand that interrupt handler might contain an RCU read-side critical\nsection, which might invoke rcu_read_unlock_special().  In the strict\nKCSAN mode of operation used by RCU, this constitutes a data race on\nthe -\u0026gt;defer_qs_iw_pending field.\n\nThis commit therefore disables interrupts across the portion of the\nrcu_preempt_deferred_qs_handler() that updates the -\u0026gt;defer_qs_iw_pending\nfield.  This suffices because this handler is not a fast path.(CVE-2025-39749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 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+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: prevent NULL pointer dereference in UTF16 conversion\n\nThere can be a NULL pointer dereference bug here. NULL is passed to\n__cifs_sfu_make_node without checks, which passes it unchecked to\ncifs_strndup_to_utf16, which in turn passes it to\ncifs_local_to_utf16_bytes where \u0026apos;*from\u0026apos; is dereferenced, causing a crash.\n\nThis patch adds a check for NULL \u0026apos;src\u0026apos; in cifs_strndup_to_utf16 and\nreturns NULL early to prevent dereferencing NULL pointer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE(CVE-2025-39838)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix null-deref in agg_dequeue\n\nTo prevent a potential crash in agg_dequeue (net/sched/sch_qfq.c)\nwhen cl-\u0026gt;qdisc-\u0026gt;ops-\u0026gt;peek(cl-\u0026gt;qdisc) returns NULL, we check the return\nvalue before using it, similar to the existing approach in sch_hfsc.c.\n\nTo avoid code duplication, the following changes are made:\n\n1. Changed qdisc_warn_nonwc(include/net/pkt_sched.h) into a static\ninline function.\n\n2. Moved qdisc_peek_len from net/sched/sch_hfsc.c to\ninclude/net/pkt_sched.h so that sch_qfq can reuse it.\n\n3. Applied qdisc_peek_len in agg_dequeue to avoid crashing.(CVE-2025-40083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfs: Don\u0026apos;t leak disconnected dentries on umount\n\nWhen user calls open_by_handle_at() on some inode that is not cached, we\nwill create disconnected dentry for it. If such dentry is a directory,\nexportfs_decode_fh_raw() will then try to connect this dentry to the\ndentry tree through reconnect_path(). It may happen for various reasons\n(such as corrupted fs or race with rename) that the call to\nlookup_one_unlocked() in reconnect_one() will fail to find the dentry we\nare trying to reconnect and instead create a new dentry under the\nparent. Now this dentry will not be marked as disconnected although the\nparent still may well be disconnected (at least in case this\ninconsistency happened because the fs is corrupted and .. doesn\u0026apos;t point\nto the real parent directory). This creates inconsistency in\ndisconnected flags but AFAICS it was mostly harmless. At least until\ncommit f1ee616214cb (\u0026quot;VFS: don\u0026apos;t keep disconnected dentries on d_anon\u0026quot;)\nwhich removed adding of most disconnected dentries to sb-\u0026gt;s_anon list.\nThus after this commit cleanup of disconnected dentries implicitely\nrelies on the fact that dput() will immediately reclaim such dentries.\nHowever when some leaf dentry isn\u0026apos;t marked as disconnected, as in the\nscenario described above, the reclaim doesn\u0026apos;t happen and the dentries\nare \u0026quot;leaked\u0026quot;. Memory reclaim can eventually reclaim them but otherwise\nthey stay in memory and if umount comes first, we hit infamous \u0026quot;Busy\ninodes after unmount\u0026quot; bug. Make sure all dentries created under a\ndisconnected parent are marked as disconnected as well.(CVE-2025-40105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.449379768Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1305","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\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [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:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Abort __tc_modify_qdisc if parent class does not exist\n\nLion\u0026apos;s patch [1] revealed an ancient bug in the qdisc API.\nWhenever a user creates/modifies a qdisc specifying as a parent another\nqdisc, the qdisc API will, during grafting, detect that the user is\nnot trying to attach to a class and reject. However grafting is\nperformed after qdisc_create (and thus the qdiscs\u0026apos; init callback) is\nexecuted. In qdiscs that eventually call qdisc_tree_reduce_backlog\nduring init or change (such as fq, hhf, choke, etc), an issue\narises. For example, executing the following commands:\n\nsudo tc qdisc add dev lo root handle a: htb default 2\nsudo tc qdisc add dev lo parent a: handle beef fq\n\nQdiscs such as fq, hhf, choke, etc unconditionally invoke\nqdisc_tree_reduce_backlog() in their control path init() or change() which\nthen causes a failure to find the child class; however, that does not stop\nthe unconditional invocation of the assumed child qdisc\u0026apos;s qlen_notify with\na null class. All these qdiscs make the assumption that class is non-null.\n\nThe solution is ensure that qdisc_leaf() which looks up the parent\nclass, and is invoked prior to qdisc_create(), should return failure on\nnot finding the class.\nIn this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the\nparentid doesn\u0026apos;t correspond to a class, so that we can detect it\nearlier on and abort before qdisc_create is called.\n\n[1] https://lore.kernel.org/netdev/(CVE-2025-38457)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 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+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: tuner: xc5000: Fix use-after-free in xc5000_release\n\nThe original code uses cancel_delayed_work() in xc5000_release(), which\ndoes not guarantee that the delayed work item timer_sleep has fully\ncompleted if it was already running. This leads to use-after-free scenarios\nwhere xc5000_release() may free the xc5000_priv while timer_sleep is still\nactive and attempts to dereference the xc5000_priv.\n\nA typical race condition is illustrated below:\n\nCPU 0 (release thread)                 | CPU 1 (delayed work callback)\nxc5000_release()                       | xc5000_do_timer_sleep()\n  cancel_delayed_work()                |\n  hybrid_tuner_release_state(priv)     |\n    kfree(priv)                        |\n                                       |   priv = container_of() // UAF\n\nReplace cancel_delayed_work() with cancel_delayed_work_sync() to ensure\nthat the timer_sleep is properly canceled before the xc5000_priv memory\nis deallocated.\n\nA deadlock concern was considered: xc5000_release() is called in a process\ncontext and is not holding any locks that the timer_sleep work item might\nalso need. Therefore, the use of the _sync() variant is safe here.\n\nThis bug was initially identified through static analysis.\n\n[hverkuil: fix typo in Subject: tunner -\u0026gt; tuner](CVE-2025-39994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Disallow dirty tracking if incoherent page walk\n\nDirty page tracking relies on the IOMMU atomically updating the dirty bit\nin the paging-structure entry. For this operation to succeed, the paging-\nstructure memory must be coherent between the IOMMU and the CPU. In\nanother word, if the iommu page walk is incoherent, dirty page tracking\ndoesn\u0026apos;t work.\n\nThe Intel VT-d specification, Section 3.10 \u0026quot;Snoop Behavior\u0026quot; states:\n\n\u0026quot;Remapping hardware encountering the need to atomically update A/EA/D bits\n in a paging-structure entry that is not snooped will result in a non-\n recoverable fault.\u0026quot;\n\nTo prevent an IOMMU from being incorrectly configured for dirty page\ntracking when it is operating in an incoherent mode, mark SSADS as\nsupported only when both ecap_slads and ecap_smpwc are supported.(CVE-2025-40058)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.443986305Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2025-38162","title":"CVE-2025-38162 in linux - Patched by Root","description":"Root has patched CVE-2025-38162 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:19:37.702550301Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:29.356832Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2025-38162","title":"CVE-2025-38162 in linux - Patched by Root","description":"Root has patched CVE-2025-38162 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:09.52038234Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:31.251695Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2025-38162","title":"CVE-2025-38162 in linux - Patched by Root","description":"Root has patched CVE-2025-38162 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:15:15.339802458Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-06T14:57:21.420606Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-38162","title":"CVE-2025-38162 in linux - Patched by Root","description":"Root has patched CVE-2025-38162 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:18:03.21860152Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-06T16:59:12.581242Z"},{"id":"UBUNTU-CVE-2025-38162","description":"In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation When calculating the lookup table size, ensure the following multiplication does not overflow: - desc-\u003efield_len[] maximum value is U8_MAX multiplied by   NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case. - NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case. - sizeof(unsigned long), from sizeof(*f-\u003elt), lt in   struct nft_pipapo_field. Then, use check_mul_overflow() to multiply by bucket size and then use check_add_overflow() to the alignment for avx2 (if needed). Finally, add lt_size_check_overflow() helper and use it to consolidate this. While at it, replace leftover allocation using the GFP_KERNEL to GFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:15:00Z","modified":"2026-11-10T02:49:59.14093599Z","cvss":[{"version":"4.0","score":8.5,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"},{"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-10T03:18:29.918261Z"},{"id":"AZL-64583","title":"CVE-2025-38162 affecting package kernel for versions less than 6.6.126.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:15:31Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:23.66471Z"},{"id":"AZL-70645","title":"CVE-2025-38162 affecting package kernel 5.15.200.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u003efield_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u003ebb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u003elt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().","status":"published","published":"2025-07-03T09:15:31Z","modified":"2026-04-21T04:36:26.804122Z","updated_at":"2026-11-02T15:28:08.907584Z"},{"id":"CLSA-2026-1781344094","title":"kernel: Fix of 93 CVEs","description":"- irqchip: Fix refcount leak in platform_irqchip_probe {CVE-2023-53610}\n- IB/hfi1: Fix a memleak in init_credit_return {CVE-2024-26839}\n- RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() {CVE-2026-23335}\n- wifi: brcmfmac: validate bsscfg indices in IF events {CVE-2026-43110}\n- wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc() {CVE-2025-71100}\n- RDMA/core: always drop device refcount in ib_del_sub_device_and_put() {CVE-2025-71157}\n- drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table {CVE-2024-58052}\n- ionic: Fix netdev notifier unregister on failure {CVE-2024-56715}\n- uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind {CVE-2024-46739}\n- netfilter: xt_tcpmss: check remaining length before reading optlen {CVE-2026-43190}\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments {CVE-2025-38391}\n- crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init {CVE-2023-52616}\n- eventpoll: defer struct eventpoll free to RCU grace period {CVE-2026-43074}\n- wifi: brcmsmac: Fix dma_free_coherent() size {CVE-2026-31661}\n- SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf {CVE-2025-71120}\n- netfilter: nf_conntrack_expect: skip expectations in other netns via proc {CVE-2026-31496}\n- platform/x86: dell-wmi-sysman: Don't hex dump plaintext password data {CVE-2026-23370}\n- crypto: bcm - add error check in the ahash_hmac_init function {CVE-2024-56681}\n- nvme-pci: ensure we're polling a polled queue {CVE-2026-31523}\n- mmc: vub300: fix NULL-deref on disconnect {CVE-2026-31651}\n- kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup() {CVE-2023-52936}\n- ipmi: ipmb: Add check devm_kasprintf() returned value {CVE-2024-58051}\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() {CVE-2026-23021}\n- ASoC: amd: fix memory leak in acp3x pdm dma ops {CVE-2026-23190}\n- udp: Deal with race between UDP socket address change and rehash {CVE-2024-57974}\n- team: avoid NETDEV_CHANGEMTU event when unregistering slave {CVE-2026-43234}\n- tcp: secure_seq: add back ports to TS offset {CVE-2026-23247}\n- udp: Fix wildcard bind conflict check when using hash2 {CVE-2026-31503}\n- netfilter: nft_set_pipapo: prevent overflow in lookup table allocation {CVE-2025-38162}\n- rxrpc: Fix recv-recv race of completed call {CVE-2025-38524}\n- netfilter: nf_tables: reject duplicate device on updates {CVE-2025-38678}\n- nf_tables: nft_dynset: fix possible stateful expression memleak in error path {CVE-2026-23399}\n- crypto: af_alg - limit RX SG extraction by receive buffer budget {CVE-2026-31677}\n- xfrm: account XFRMA_IF_ID in aevent size calculation {CVE-2026-43107}\n- KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop {CVE-2025-21839}\n- perf: Fix sample vs do_exit() {CVE-2025-38424}\n- netfilter: nf_tables: avoid chain re-validation if possible {CVE-2025-71160}\n- ksm: use range-walk function to jump over holes in scan_get_next_rmap_item {CVE-2025-68211}\n- net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime {CVE-2025-38470}\n- net: add proper RCU protection to /proc/net/ptype {CVE-2026-23255}\n- ALSA: ctxfi: Check the error for index mapping {CVE-2026-31777}\n- rseq: Fix segfault on registration when rseq_cs is non-zero {CVE-2025-38067}\n- RDMA/core: Don't expose hw_counters outside of init net namespace {CVE-2025-22089}\n- net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv {CVE-2026-22996}\n- Input: synaptics - fix crash when enabling pass-through port {CVE-2025-21746}\n- wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit {CVE-2026-31579}\n- ptp: remove ptp-\u003en_vclocks check logic in ptp_vclock_in_use() {CVE-2025-38305}\n- driver core: fix potential NULL pointer dereference in dev_uevent() {CVE-2025-37800}\n- dm: fix NULL pointer dereference in __dm_suspend() {CVE-2025-40134}\n- net: let net.core.dev_weight always be non-zero {CVE-2025-21806}\n- exec: don't WARN for racy path_noexec check {CVE-2024-50010}\n- tracing: Fix potential deadlock in cpu hotplug with osnoise {CVE-2026-31480}\n- wifi: mac80211: Discard Beacon frames to non-broadcast address {CVE-2025-71127}\n- xfs: factor out xfs_attr3_node_entry_remove\n- ACPI: battery: Fix possible crash when unregistering a battery hook {CVE-2024-49955}\n- serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN {CVE-2026-23472}\n- drm/amdgpu: Limit BO list entry count to prevent resource exhaustion {CVE-2026-23468}\n- i2c: designware: use casting of u64 in clock multiplication to avoid overflow {CVE-2022-49749}\n- afs: Fix lock recursion {CVE-2024-53090}\n- HID: wacom: fix when get product name maybe null pointer {CVE-2024-56629}\n- vsock/virtio: cap TX credit to local buffer size {CVE-2026-23086}\n- vsock/virtio: fix potential underflow in virtio_transport_get_credit() {CVE-2026-23069}\n- bpf: Reject narrower access to pointer ctx fields {CVE-2025-38591}\n- sched/task_stack: fix object_is_on_stack() for KASAN tagged pointers {CVE-2024-53128}\n- atm: clip: Fix NULL pointer dereference in vcc_sendmsg() {CVE-2025-38458}\n- tracing: Fix null pointer dereference in tracing_err_log_open() {CVE-2023-53167}\n- bpf: Do not include stack ptr register in precision backtracking bookkeeping {CVE-2025-38279}\n- ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() {CVE-2026-23304}\n- net: annotate data-races around sk-\u003esk_{data_ready,write_space} {CVE-2026-23302}\n- net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop {CVE-2026-23300}\n- net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled {CVE-2026-23293}\n- net: usb: pegasus: validate USB endpoints {CVE-2026-23290}\n- rxrpc: Fix missing locking causing hanging calls {CVE-2024-50294}\n- cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path {CVE-2026-43328}\n- mm/page_alloc: clear page-\u003eprivate in free_pages_prepare() {CVE-2026-43303}\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message {CVE-2026-23307}\n- drm/amd/display: Increase block_sequence array size {CVE-2025-38080}\n- smb: client: Don't log plaintext credentials in cifs_set_cifscreds {CVE-2026-23303}\n- ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths {CVE-2026-43066}\n- atm: lec: fix null-ptr-deref in lec_arp_clear_vccs {CVE-2026-23286}\n- smb: client: validate the whole DACL before rewriting it in cifsacl {CVE-2026-31709}\n- KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry {CVE-2026-46316}\n- block: Remove queue freezing from several sysfs store callbacks {CVE-2025-71117}\n- mptcp: fallback earlier on simult connection {CVE-2025-71088}\n- mm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters() {CVE-2025-39916}\n- neighbour: use RCU protection in __neigh_notify() {CVE-2025-21763}\n- kernel: be more careful about dup_mmap() failures and uprobe registering {CVE-2025-21709}\n- bridge: mcast: Fix use-after-free during router port configuration {CVE-2025-38248}\n- mptcp: fix slab-use-after-free in __inet_lookup_established {CVE-2026-31669}\n- xfrm: hold dev ref until after transport_finish NF_HOOK {CVE-2026-31663}\n- xfrm: hold device only for the asynchronous decryption {CVE-2026-31663}\n- xfrm_user: fix info leak in build_mapping() {CVE-2026-43089}\n- netfilter: nfnetlink_log: initialize nfgenmsg in NLMSG_DONE terminator {CVE-2026-43085}\n- l2tp: Drop large packets with UDP encap {CVE-2026-43080}\n- perf/x86/intel/uncore: Skip discovery table for offline dies {CVE-2026-43079}\n- KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION {CVE-2026-31590}","status":"published","published":"2026-10-21T00:28:59Z","modified":"2026-10-26T09:43:10.320754695Z","updated_at":"2026-11-02T15:43:45.445699Z"},{"id":"CLSA-2026-1783791447","title":"kernel: Fix of 307 CVEs","description":"- gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully {CVE-2022-48660}\n- ipv4: check for NULL idev in ip_route_use_hint() {CVE-2024-36008}\n- KEYS: trusted: Do not use WARN when encode fails {CVE-2024-36975}\n- Fix userfaultfd_api to return EINVAL as expected {CVE-2024-41027}\n- xhci: Fix null pointer dereference when host dies {CVE-2023-52898}\n- sctp: sysctl: auth_enable: avoid using current-\u003ensproxy {CVE-2025-21638}\n- blk-mq: fix IO hang from sbitmap wakeup race {CVE-2024-26671}\n- net: openvswitch: fix flow memory leak in ovs_flow_cmd_new {CVE-2023-52977}\n- gpiolib: fix memory leak in gpiochip_setup_dev() {CVE-2022-48975}\n- HID: betop: check shape of output reports {CVE-2023-53015}\n- mm/swapfile: add cond_resched() in get_swap_pages() {CVE-2023-52932}\n- HV: hv_balloon: fix memory leak with using debugfs_lookup() {CVE-2023-52937}\n- drm/i915: Fix a memory leak with reused mmap_offset {CVE-2023-53002}\n- ptdma: pt_core_execute_cmd() should use spinlock {CVE-2023-53013}\n- RDMA/core: Fix ib block iterator counter overflow {CVE-2023-53026}\n- Bluetooth: hci_conn: Fix memory leaks {CVE-2023-53018}\n- scsi: target: pscsi: Fix bio_put() for error case {CVE-2024-26760}\n- sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() {CVE-2026-23038}\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() {CVE-2025-40194}\n- ALSA: hda/cs8409: Fix possible NULL dereference {CVE-2024-50160}\n- nbd: don't allow reconnect after disconnect {CVE-2025-21731}\n- openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}\n- ext4: detect invalid INLINE_DATA + EXTENTS flag combination {CVE-2025-40167}\n- ext4: xattr: fix null pointer deref in ext4_raw_inode() {CVE-2025-68820}\n- net: fix memory leak in skb_segment_list for GRO packets {CVE-2026-22979}\n- wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode {CVE-2025-40321}\n- ipvs: fix ipv4 null-ptr-deref in route error path {CVE-2025-68813}\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping {CVE-2025-40121}\n- i40e: Fix macvlan leak by synchronizing access to mac_filter_hash {CVE-2024-50041}\n- net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() {CVE-2024-50000}\n- bpf: Fix reference count leak in bpf_prog_test_run_xdp() {CVE-2026-22994}\n- xsk: check IFF_UP earlier in Tx path {CVE-2023-53240}\n- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers {CVE-2024-41038}\n- virtgpu: don't reset on shutdown {CVE-2025-38064}\n- xen/netfront: fix crash when removing device {CVE-2022-48969}\n- mptcp: do not fallback when OoO is present {CVE-2024-50185}\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler {CVE-2025-39925}\n- netfilter: nf_tables: remove redundant chain validation on register store {CVE-2025-71160}\n- xfs: fix use-after-free in xattr node block inactivation {CVE-2026-43053}\n- ext4: fix racy may inline data check in dio write {CVE-2023-52786}\n- drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini {CVE-2023-52738}\n- macsec: fix UAF bug for real_dev {CVE-2022-49390}\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation {CVE-2024-42259}\n- mm/shmem: disable PMD-sized page cache if needed {CVE-2024-42241}\n- driver: iio: add missing checks on iio_info's callback access {CVE-2024-46715}\n- udmabuf: fix memory leak on last export_udmabuf() error path {CVE-2024-56712}\n- ALSA: control: Avoid WARN() for symlink errors {CVE-2024-56657}\n- mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM {CVE-2024-56611}\n- eth: bnxt: always recalculate features after XDP clearing, fix null-deref {CVE-2025-21682}\n- net: annotate data-races around sk-\u003esk_{data_ready,write_space} {CVE-2026-23302}\n- udmabuf: change folios array from kmalloc to kvmalloc {CVE-2024-56544}\n- RDMA/mlx5: Move events notifier registration to be after device registration {CVE-2024-53224}\n- dlm: fix possible lkb_resource null dereference {CVE-2024-47809}\n- ACPI: battery: Fix possible crash when unregistering a battery hook {CVE-2024-49955}\n- ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params {CVE-2024-58012}\n- tpm: Change to kvalloc() in eventlog/acpi.c {CVE-2024-58005}\n- net_sched: sch_sfq: move the limit validation {CVE-2025-37752}\n- usb: xhci: Fix NULL pointer dereference on certain command aborts {CVE-2024-57981}\n- mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() {CVE-2025-21861}\n- bpf: avoid holding freeze_mutex during mmap operation {CVE-2025-21853}\n- acct: perform last write from workqueue {CVE-2025-21846}\n- netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() {CVE-2025-21959}\n- ipvlan: ensure network headers are in skb linear part {CVE-2025-21891}\n- wifi: iwlwifi: mvm: fix 6 GHz scan construction {CVE-2024-53055}\n- signal: restore the override_rlimit logic {CVE-2024-50271}\n- thermal: core: Reference count the zone in thermal_zone_get_by_id() {CVE-2024-50028}\n- block: fix potential invalid pointer dereference in blk_add_partition {CVE-2024-47705}\n- userfaultfd: fix checks for huge PMDs {CVE-2024-46787}\n- mptcp: pm: only mark 'subflow' endp as available {CVE-2024-45010}\n- mptcp: pm: re-using ID of unused flushed subflows {CVE-2024-45010}\n- eth: bnxt: fix truesize for mb-xdp-pass case {CVE-2025-21961}\n- driver core: fix potential NULL pointer dereference in dev_uevent() {CVE-2025-37800}\n- virtio_net: Fix napi_skb_cache_put warning {CVE-2024-43835}\n- cgroup: fix race between task migration and iteration {CVE-2026-43439}\n- bpf: Fix wrong reg type conversion in release_reference() {CVE-2022-49873}\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error {CVE-2025-21732}\n- serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN {CVE-2026-23472}\n- drm/amdgpu: Limit BO list entry count to prevent resource exhaustion {CVE-2026-23468}\n- net: add proper RCU protection to /proc/net/ptype {CVE-2026-23255}\n- tcp: secure_seq: add back ports to TS offset {CVE-2026-23247}\n- RDMA/mlx5: Fix a WARN during dereg_mr for DM type {CVE-2025-21888}\n- list: fix a data-race around ep-\u003erdllist {CVE-2022-49443}\n- can: isotp: sanitize CAN ID checks in isotp_bind() {CVE-2022-49269}\n- rxrpc: Fix recv-recv race of completed call {CVE-2025-38524}\n- sched/rt: Fix race in push_rt_task {CVE-2025-38234}\n- NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}\n- virtio: break and reset virtio devices on device_shutdown() {CVE-2025-38064}\n- block: fix resource leak in blk_register_queue() error path {CVE-2025-37980}\n- xsk: Fix race condition in AF_XDP generic RX path {CVE-2025-37920}\n- mm/vmscan: don't try to reclaim hwpoison folio {CVE-2025-37834}\n- nouveau: offload fence uevents work to workqueue {CVE-2024-26719}\n- bpf: Fix kmemleak warning for percpu hashmap {CVE-2025-37807}\n- x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault() {CVE-2024-26906}\n- x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h {CVE-2024-26906}\n- net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket {CVE-2024-42246}\n- quota: Fix potential NULL pointer dereference {CVE-2024-26878}\n- arp: Prevent overflow in arp_req_get(). {CVE-2024-26733}\n- ALSA: Fix deadlocks with kctl removals at disconnection {CVE-2024-38600}\n- wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values {CVE-2024-42114}\n- Bluetooth: hci_core: cancel all works upon hci_unregister_dev() {CVE-2024-41063}\n- fsnotify: clear PARENT_WATCHED flags lazily {CVE-2024-47660}\n- mm: use memalloc_nofs_save() in page_cache_ra_order() {CVE-2024-36882}\n- mm/memory-failure: fix deadlock when hugetlb_optimize_vmemmap is enabled {CVE-2024-26987}\n- net: esp: fix bad handling of pages from page_pool {CVE-2024-26953}\n- virtio/vsock: Fix accept_queue memory leak {CVE-2024-53119}\n- netfilter: nft_payload: sanitize offset and length before calling skb_checksum() {CVE-2024-50251}\n- fs/proc: fix softlockup in __read_vmcore (part 2) {CVE-2025-21694}\n- drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability {CVE-2024-53051}\n- net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. {CVE-2025-23143}\n- x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() {CVE-2025-22090}\n- net: decrease cached dst counters in dst_release {CVE-2025-22057}\n- nfsd: put dl_stid if fail to queue dl_recall {CVE-2025-22025}\n- nfsd: make nfsd4_run_cb a bool return function {CVE-2025-22025}\n- usb: gadget: core: flush gadget workqueue after device removal {CVE-2025-21838}\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 {CVE-2025-21831}\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use {CVE-2024-58079}\n- usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm() {CVE-2023-52877}\n- ext4: filesystems without casefold feature cannot be mounted with siphash {CVE-2024-49968}\n- padata: use integer wrap around to prevent deadlock on seq_nr overflow {CVE-2024-47739}\n- bpf, lsm: Add check for BPF LSM return value {CVE-2024-47703}\n- sched/smt: Fix unbalance sched_smt_present dec/inc {CVE-2024-44958}\n- xen-netfront: Fix NULL sring after live migration {CVE-2022-48969}\n- dlm: prevent NPD when writing a positive value to event_done {CVE-2025-23131}\n- udp: Deal with race between UDP socket address change and rehash {CVE-2024-57974}\n- bpf: sync_linked_regs() must preserve subreg_def {CVE-2024-53125}\n- mptcp: handle consistently DSS corruption {CVE-2024-50185}\n- null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' {CVE-2024-36478}\n- net: tunnels: annotate lockless accesses to dev-\u003eneeded_headroom {CVE-2023-53109}\n- net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled {CVE-2025-38039}\n- uprobes: Reject the shared zeropage in uprobe_write_opcode() {CVE-2025-21881}\n- mm: slub: avoid wake up kswapd in set_track_prepare {CVE-2025-39843}\n- mm/smaps: fix race between smaps_hugetlb_range and migration {CVE-2025-39754}\n- bpf: Reject narrower access to pointer ctx fields {CVE-2025-38591}\n- net: clear the dst when changing skb protocol {CVE-2025-38192}\n- backlight: led_bl: Hold led_access lock when calling led_sysfs_disable() {CVE-2025-23144}\n- RDMA/core: Don't expose hw_counters outside of init net namespace {CVE-2025-22089}\n- can: j1939: implement NETDEV_UNREGISTER notification handler {CVE-2025-39925}\n- net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF. {CVE-2025-22111}\n- vxlan: Fix NPD when refreshing an FDB entry with a nexthop object {CVE-2025-39851}\n- loop: Avoid updating block size under exclusive owner {CVE-2025-38709}\n- wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() {CVE-2025-38643}\n- net_sched: sch_sfq: reject invalid perturb period {CVE-2025-38193}\n- net: phy: mscc: Fix memory leak when using one step timestamping {CVE-2025-38148}\n- espintcp: remove encap socket caching to avoid reference leak {CVE-2025-38097}\n- rseq: Fix segfault on registration when rseq_cs is non-zero {CVE-2025-38067}\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs {CVE-2025-38040}\n- usb: typec: ucsi: displayport: Fix deadlock {CVE-2025-37967}\n- ipvs: fix uninit-value for saddr in do_output_route4 {CVE-2025-37961}\n- ksm: use range-walk function to jump over holes in scan_get_next_rmap_item {CVE-2025-68211}\n- bpf: Scrub packet on bpf_redirect_peer {CVE-2025-37959}\n- tracing: Verify event formats that have \"%*p..\" {CVE-2025-37938}\n- iommu/amd/pgtbl: Fix possible race while increase page table level {CVE-2025-39961}\n- net/mlx5e: Harden uplink netdev access against device unbind {CVE-2025-39947}\n- dm-stripe: fix a possible integer overflow {CVE-2025-39940}\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer {CVE-2025-39937}\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode {CVE-2025-38665}\n- net/mlx5e: Fix crash on profile change rollback failure {CVE-2026-23000}\n- netfilter: nft_set_pipapo: prevent overflow in lookup table allocation {CVE-2025-38162}\n- tracing: Add recursion protection in kernel stack trace recording {CVE-2026-23138}\n- rxrpc: Fix recvmsg() unconditional requeue {CVE-2026-23066}\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts {CVE-2026-22997}\n- net: can: j1939: recover socket queue on CAN bus error during BAM transmission {CVE-2026-22997}\n- dm-verity: disable recursive forward error correction {CVE-2025-71161}\n- netfilter: nf_tables: avoid chain re-validation if possible {CVE-2025-71160}\n- KEYS: trusted: Fix a memory leak in tpm2_load_cmd {CVE-2025-71147}\n- vsock/virtio: fix potential underflow in virtio_transport_get_credit() {CVE-2026-23069}\n- net: fix segmentation of forwarding fraglist GRO {CVE-2026-23154}\n- ice: Don't process extts if PTP is disabled {CVE-2024-42107}\n- drm/i915/dpt: Make DPT object unshrinkable {CVE-2024-40924}\n- drm/i915/dpt: Treat the DPT BO as a framebuffer {CVE-2024-40924}\n- bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx {CVE-2024-53091}\n- pipe: wakeup wr_wait after setting max_usage {CVE-2023-52672}\n- bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails {CVE-2023-53103}\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check {CVE-2024-57993}\n- drm/amdkfd: debugfs hang_hws skip GPU with MES {CVE-2025-37853}\n- leds: mlxreg: Use devm_mutex_init() for mutex initialization {CVE-2024-42129}\n- drm/amd/display: fix a Null pointer dereference vulnerability {CVE-2025-39705}\n- gfs2: Validate i_depth for exhash directories {CVE-2025-38710}\n- drm/scheduler: signal scheduled fence when kill job {CVE-2025-38436}\n- drm/amdgpu: Add basic validation for RAS header {CVE-2025-38426}\n- mptcp: fix NULL pointer in can_accept_new_subflow {CVE-2025-23145}\n- bpf: bpf_sk_storage: Fix invalid wait context lockdep report {CVE-2023-53857}\n- nvme-core: fix memory leak in dhchap_secret_store {CVE-2023-53852}\n- virtio_net: Fix error unwinding of XDP initialization {CVE-2023-53499}\n- nvme-core: fix memory leak in dhchap_ctrl_secret {CVE-2023-53792}\n- ceph: fix race condition validating r_parent before applying state {CVE-2025-39927}\n- x86/MCE: Always save CS register on AMD Zen IF Poison errors {CVE-2023-53438}\n- genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask() {CVE-2023-53332}\n- nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net {CVE-2023-54276}\n- blk-cgroup: Fix NULL deref caused by blkg_policy_data being installed before init {CVE-2023-54271}\n- net/mlx5e: TC, Fix internal port memory leak {CVE-2023-53999}\n- tipc: do not update mtu if msg_max is too small in mtu negotiation {CVE-2023-53517}\n- tipc: add tipc_bearer_min_mtu to calculate min mtu {CVE-2023-53517}\n- tun: Fix memory leak for detached NAPI queue. {CVE-2023-53685}\n- net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize {CVE-2023-53667}\n- start_kernel: Add __no_stack_protector function attribute {CVE-2023-53491}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- sched/psi: use kernfs polling functions for PSI trigger polling {CVE-2023-54019}\n- cxl/pmem: Fix nvdimm registration races {CVE-2023-54323}\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock {CVE-2025-68223}\n- dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() {CVE-2026-23004}\n- wifi: mac80211: don't WARN for connections on invalid channels {CVE-2025-71227}\n- md: suspend array while updating raid_disks via sysfs {CVE-2025-71225}\n- net: stmmac: fix the crash issue for zero copy XDP_TX action {CVE-2025-71095}\n- drm/ttm: Don't leak a resource on eviction error {CVE-2023-54254}\n- firmware: arm_sdei: Fix sleep from invalid context BUG {CVE-2023-54160}\n- iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter {CVE-2023-54057}\n- net: usb: asix: validate PHY address before use {CVE-2025-71094}\n- tty: fix deadlock caused by calling printk() under tty_port-\u003elock {CVE-2022-49441}\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE {CVE-2026-23401}\n- blktrace: fix __this_cpu_read/write in preemptible context {CVE-2026-23374}\n- x86/CPU: Fix FPDSS on Zen1 {CVE-2025-54505}\n- ice: Fix PTP NULL pointer dereference during VSI rebuild {CVE-2026-23210}\n- mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() {CVE-2026-23169}\n- gfs2: No more self recovery {CVE-2025-38659}\n- tracing: kprobe: Fix memory leak in test_gen_kprobe/kretprobe_cmd() {CVE-2022-49891}\n- tracing: kprobe: Fix potential null-ptr-deref on trace_array in kprobe_event_gen_test_exit() {CVE-2022-49796}\n- tracing: kprobe: Fix potential null-ptr-deref on trace_event_file in kprobe_event_gen_test_exit() {CVE-2022-49797}\n- netlink: Bounds-check struct nlmsgerr creation {CVE-2022-49766}\n- bpf: Prevent bpf program recursion for raw tracepoint probes {CVE-2022-49764}\n- i2c: designware: use casting of u64 in clock multiplication to avoid overflow {CVE-2022-49749}\n- futex: Clear stale exiting pointer in futex_lock_pi() retry path {CVE-2026-31555}\n- ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() {CVE-2026-31531}\n- netfilter: ctnetlink: use netlink policy range checks {CVE-2026-31495}\n- tracing: Fix potential deadlock in cpu hotplug with osnoise {CVE-2026-31480}\n- esp: fix skb leak with espintcp and async crypto {CVE-2026-31518}\n- xfs: factor out xfs_attr3_leaf_init {CVE-2026-43053}\n- xfs: factor out xfs_attr3_node_entry_remove {CVE-2026-43053}\n- ALSA: ctxfi: Check the error for index mapping {CVE-2026-31777}\n- bridge: br_nd_send: validate ND option lengths {CVE-2026-31752}\n- rtnetlink: add missing netlink_ns_capable() check for peer netns {CVE-2026-31692}\n- crypto: af_alg - limit RX SG extraction by receive buffer budget {CVE-2026-31677}\n- APEI/GHES: ensure that won't go past CPER allocated record {CVE-2026-43277}\n- ceph: supply snapshot context in ceph_zero_partial_object() {CVE-2026-43273}\n- team: avoid NETDEV_CHANGEMTU event when unregistering slave {CVE-2026-43234}\n- wifi: rtw88: 8822b: Avoid WARNING in rtw8822b_config_trx_mode() {CVE-2025-71297}\n- EFI/CPER: don't go past the ARM processor CPER record buffer {CVE-2026-43266}\n- net: bridge: switchdev: Skip MDB replays of deferred events on offload {CVE-2024-26837}\n- can: mcp251xfd: fix infinite loop when xmit fails {CVE-2024-41088}\n- ipvlan: Make the addrs_lock be per port {CVE-2026-23103}\n- netem: fix return value if duplicate enqueue fails {CVE-2024-45016}\n- USB: serial: mos7840: fix crash on resume {CVE-2024-42244}\n- crypto: null - Use spin lock instead of mutex {CVE-2025-37808}\n- RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly {CVE-2025-71096}\n- bpf: Fix overrunning reservations in ringbuf {CVE-2024-41009}\n- bpf: Fix bpf_sk_select_reuseport() memory leak {CVE-2025-21683}\n- drm/i915: Fix request ref counting during error capture \u0026 debugfs dump {CVE-2023-52981}\n- netfilter: conntrack: fix wrong ct-\u003etimeout value {CVE-2023-53635}\n- drop_monitor: replace spin_lock by raw_spin_lock {CVE-2024-40980}\n- net: bonding: fix NULL deref in bond_debug_rlb_hash_show {CVE-2026-31546}\n- serial: protect uart_port_dtr_rts() in uart_shutdown() too {CVE-2024-50058}\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable. {CVE-2026-31551}\n- ipv6: Fix signed integer overflow in __ip6_append_data {CVE-2022-49728}\n- selinux: avoid dereference of garbage after mount failure {CVE-2024-35904}\n- fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name {CVE-2024-49934}\n- tracing: Do not let histogram values have some modifiers {CVE-2023-53093}\n- ice: Add netif_device_attach/detach into PF reset flow {CVE-2024-46770}\n- bpf: Fix deadlock between rcu_tasks_trace and event_mutex. {CVE-2025-37884}\n- fbmon: prevent division by zero in fb_videomode_from_videomode() {CVE-2024-35922}\n- drm/amdgpu: Fix the null pointer dereference to ras_manager {CVE-2024-43908}\n- tracing: Ensure visibility when inserting an element into tracing_map {CVE-2024-26645}\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func {CVE-2024-47720}\n- phy: mdio: fix memory leak {CVE-2021-47416}\n- ipv4: Fix reference count leak when using error routes with nexthop objects {CVE-2025-71097}\n- NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() {CVE-2024-50046}\n- packet: annotate data-races around ignore_outgoing {CVE-2024-26862}\n- md: fix resync softlockup when bitmap size is less than array size {CVE-2024-38598}\n- wireguard: receive: annotate data-race around receiving_counter.counter {CVE-2024-26861}\n- netfs: Only call folio_start_fscache() one time for each folio {CVE-2023-52582}\n- usb: xhci: tegra: fix sleep in atomic call {CVE-2023-53475}\n- ACPI: PAD: fix crash in exit_round_robin() {CVE-2024-49935}\n- locking/rtmutex: Skip remove_waiter() when waiter is not enqueued {CVE-2026-43499}\n- rtmutex: Use waiter::task instead of current in remove_waiter() {CVE-2026-43499}\n- netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() {CVE-2024-50256}\n- Bluetooth: ISO: Fix multiple init when debugfs is disabled {CVE-2024-50077}\n- hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio {CVE-2025-21931}\n- RDMA/core: Silence oversized kvmalloc() warning {CVE-2025-37867}\n- tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() {CVE-2024-26663}\n- net: let net.core.dev_weight always be non-zero {CVE-2025-21806}\n- net: mdio: fix unbalanced fwnode reference count in mdio_device_release() {CVE-2022-48961}\n- eth: alx: take rtnl_lock on resume {CVE-2022-50498}\n- ata: libata-transport: fix error handling in ata_tlink_add() {CVE-2022-49824}\n- ata: libata-transport: fix error handling in ata_tport_add() {CVE-2022-49825}\n- netfilter: br_netfilter: fix panic with metadata_dst skb {CVE-2024-50045}\n- net: fix NULL pointer in skb_segment_list {CVE-2023-52991}\n- hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove {CVE-2024-26698}\n- scsi: qla2xxx: validate nvme_local_port correctly {CVE-2024-42286}\n- rcu/rcuscale: Stop kfree_scale_thread thread(s) after unloading rcuscale {CVE-2023-53291}\n- wifi: mac80211: Discard Beacon frames to non-broadcast address {CVE-2025-71127}\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() {CVE-2024-46755}\n- sctp: sysctl: cookie_hmac_alg: avoid using current-\u003ensproxy {CVE-2025-21640}\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes {CVE-2024-41089}\n- tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING {CVE-2023-52845}\n- bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets {CVE-2023-52523}\n- Bluetooth: Fix not cleanup led when bt_init fails {CVE-2022-48971}\n- netfilter: nf_conntrack_h323: Add protection for bmp length out of range {CVE-2024-26851}\n- ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() {CVE-2024-53680}\n- ppp_async: limit MRU to 64K {CVE-2024-26675}\n- USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages {CVE-2024-40904}\n- ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work {CVE-2024-26631}\n- xfrm: fix one more kernel-infoleak in algo dumping {CVE-2024-50110}\n- xdp: fix invalid wait context of page_pool_destroy() {CVE-2024-43834}\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check {CVE-2024-45000}\n- mac802154: check local interfaces before deleting sdata list {CVE-2024-57948}\n- usbnet: gl620a: fix endpoint checking in genelink_bind() {CVE-2025-21877}\n- IB/core: Fix ib_cache_setup_one error flow cleanup {CVE-2024-47693}\n- can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate {CVE-2021-4454}\n- vfs: fix race between evice_inodes() and find_inode()\u0026iput() {CVE-2024-47679}\n- scsi: storvsc: Fix handling of virtual Fibre Channel timeouts {CVE-2023-53245}\n- iavf: fix off-by-one issues in iavf_config_rss_reg() {CVE-2025-71087}\n- cachefiles: fix memory leak in cachefiles_add_cache() {CVE-2024-26840}\n- ext4: fix access to uninitialised lock in fc replay path {CVE-2024-50014}\n- net: hns3: fix kernel crash when 1588 is sent on HIP08 devices {CVE-2025-21649}\n- ftrace: Fix regression with module command in stack_trace_filter {CVE-2024-56569}\n- ipv6: sr: fix invalid unregister error path {CVE-2024-38612}\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests {CVE-2026-43493}\n- netfilter: flowtable: strictly check for maximum number of actions {CVE-2026-43329}\n- ipv6: icmp: clear skb2-\u003ecb[] in ip6_err_gen_icmpv6_unreach() {CVE-2026-43038}","status":"published","published":"2026-10-21T12:13:51Z","modified":"2026-10-26T09:43:27.885610959Z","updated_at":"2026-11-02T15:43:46.151924Z"},{"id":"SUSE-SU-2025:02853-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-42134: virtio-pci: Check if is_avq is NULL (bsc#1228664 bsc#1247831).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38047: x86/fred: Fix system hang during S4 resume with FRED enabled (bsc#1245084).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38256: io_uring/rsrc: fix folio unpinning (bsc#1246188).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38453: kABI: io_uring: msg_ring ensure io_kiocb freeing is deferred (bsc#1247234).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38475: smc: Fix various oops due to inet_sock type confusion (bsc#1247308).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- Enable SMC_LO (a.k.a SMC-D) (jsc#PED-13248).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- Logitech C-270 even more broken (stable-fixes).\n- Re-enable qmi_wwan for arm64 (bsc#1246113)\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'drm/nouveau: check ioctl command codes better' (git-fixes).\n- Revert 'drm/xe/xe2: Enable Indirect Ring State support for Xe2' (git-fixes).\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- Update config files. config/x86_64/default config/arm64/default CONFIG_INTEGRITY_MACHINE_KEYRING=y +CONFIG_INTEGRITY_CA_MACHINE_KEYRING=y +CONFIG_INTEGRITY_CA_MACHINE_KEYRING_MAX=y +CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=y (bsc#1243678)\n- accel/ivpu: Remove copy engine support (stable-fixes).\n- acpi: LPSS: Remove AudioDSP related ID (git-fixes).\n- acpi: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- acpi: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- acpica: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- alsa: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- alsa: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- alsa: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- alsa: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- alsa: hda/realtek: Fix mute LED mask on HP OMEN 16 laptop (git-fixes).\n- alsa: hda/tegra: Add Tegra264 support (stable-fixes).\n- alsa: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- alsa: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- alsa: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- alsa: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- alsa: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- alsa: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- alsa: scarlett2: Add retry on -EPROTO from scarlett2_usb_tx() (git-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- asoc: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- asoc: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- asoc: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- asoc: amd: yc: update quirk data for HP Victus (stable-fixes).\n- asoc: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- asoc: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- asoc: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- asoc: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- asoc: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- asoc: fsl_sai: Force a software reset when starting in consumer mode (git-fixes).\n- asoc: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- asoc: mediatek: use reserved memory or enable buffer pre-allocation (git-fixes).\n- asoc: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- asoc: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- bluetooth: HCI: Set extended advertising data synchronously (git-fixes).\n- bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type (git-fixes).\n- bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_core: add missing braces when using macro parameters (git-fixes).\n- bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- bnxt_en: Fix double invocation of bnxt_ulp_stop()/bnxt_ulp_start() (git-fixes).\n- bonding: Correctly support GSO ESP offload (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: hkdf - skip TVs with unapproved salt lengths in FIPS mode (bsc#1241200 bsc#1246134).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dax: add a sysfs knob to control memmap_on_memory behavior (bsc#1235515,jsc#PED-12731).\n- devlink: Add support for u64 parameters (jsc#PED-12745).\n- devlink: avoid param type value translations (jsc#PED-12745).\n- devlink: define enum for attr types of dynamic attributes  (jsc#PED-12745).\n- devlink: define enum for attr types of dynamic attributes (jsc#PED-12745).\n- devlink: introduce devlink_nl_put_u64() (jsc#PED-12745).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- documentatiion/ABI: add ABI documentation for sys-bus-dax (bsc#1235515,jsc#PED-12731).\n- documentation: ACPI: Fix parent device references (git-fixes).\n- documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- dpll: Add basic Microchip ZL3073x support (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set frequency on pins  (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set frequency on pins (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set priority on input pins  (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set priority on input pins (jsc#PED-12745).\n- dpll: zl3073x: Fetch invariants during probe (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin selection in manual mode  (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin selection in manual mode (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin state setting in automatic  mode (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin state setting in automatic mode (jsc#PED-12745).\n- dpll: zl3073x: Read DPLL types and pin properties from system  firmware (jsc#PED-12745).\n- dpll: zl3073x: Read DPLL types and pin properties from system firmware (jsc#PED-12745).\n- dpll: zl3073x: Register DPLL devices and pins (jsc#PED-12745).\n- drm/amd/display: Check dce_hwseq before dereferencing it (stable-fixes).\n- drm/amd/display: Correct non-OLED pre_T11_delay (stable-fixes).\n- drm/amd/display: Disable CRTC degamma LUT for DCN401 (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/display: Fix RMCM programming seq errors (stable-fixes).\n- drm/amd/display: Fix mpv playback corruption on weston (stable-fixes).\n- drm/amd/display: Free memory allocation (stable-fixes).\n- drm/amd/display: fix initial backlight brightness calculation (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/discovery: use specific ip_discovery.bin for legacy asics (stable-fixes).\n- drm/amdgpu/gfx10: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu/gfx9.4.3: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx9: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/ip_discovery: add missing ip_discovery fw (stable-fixes).\n- drm/amdgpu: Add kicker device detection (stable-fixes).\n- drm/amdgpu: Fix SDMA UTC_L1 handling during start/stop sequences (stable-fixes).\n- drm/amdgpu: Increase reset counter only on success (stable-fixes).\n- drm/amdgpu: Initialize data to NULL in imu_v12_0_program_rlc_ram() (git-fixes).\n- drm/amdgpu: Remove nbiov7.9 replay count reporting (git-fixes).\n- drm/amdgpu: Reset the clear flag in buddy during resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdgpu: seq64 memory unmap uses uninterruptible lock (stable-fixes).\n- drm/amdkfd: Do not call mmput from MMU notifier callback (git-fixes).\n- drm/amdkfd: Fix instruction hazard in gfx12 trap handler (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/amdkfd: remove gfx 12 trap handler page size cap (stable-fixes).\n- drm/bridge: aux-hpd-bridge: fix assignment of the of_node (git-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/connector: hdmi: Evaluate limited range after computing format (git-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/display: Fix dma_fence_wait_timeout() return value handling (git-fixes).\n- drm/i915/dsi: Fix off by one in BXT_MIPI_TRANS_VTOTAL (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/imagination: Fix kernel crash when hard resetting the GPU (git-fixes).\n- drm/mediatek: Add wait_event_timeout when disabling plane (git-fixes).\n- drm/mediatek: only announce AFBC if really supported (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/nouveau: check ioctl command codes better (git-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/panthor: Add missing explicit padding in drm_panthor_gpu_info (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/v3d: Disable interrupts before resetting the GPU (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- drm/xe/bmg: fix compressed VRAM handling (git-fixes).\n- drm/xe/guc: Dead CT helper (stable-fixes).\n- drm/xe/guc: Explicitly exit CT safe mode on unwind (git-fixes).\n- drm/xe/guc_submit: add back fix (git-fixes).\n- drm/xe/mocs: Initialize MOCS index early (stable-fixes).\n- drm/xe/pf: Clear all LMTT pages on alloc (git-fixes).\n- drm/xe/pf: Move VFs reprovisioning to worker (stable-fixes).\n- drm/xe/pf: Prepare to stop SR-IOV support prior GT reset (git-fixes).\n- drm/xe/pf: Sanitize VF scratch registers on FLR (stable-fixes).\n- drm/xe/pm: Correct comment of xe_pm_set_vram_threshold() (git-fixes).\n- drm/xe/uapi: Correct sync type definition in comments (git-fixes).\n- drm/xe/vf: Disable CSC support on VF (git-fixes).\n- drm/xe: Allocate PF queue size on pow2 boundary (git-fixes).\n- drm/xe: Allow bo mapping on multiple ggtts (stable-fixes).\n- drm/xe: Fix DSB buffer coherency (stable-fixes).\n- drm/xe: Fix build without debugfs (git-fixes).\n- drm/xe: Fix early wedge on GuC load failure (git-fixes).\n- drm/xe: Fix taking invalid lock on wedge (stable-fixes).\n- drm/xe: Move DSB l2 flush to a more sensible place (git-fixes).\n- drm/xe: Replace double space with single space after comma (stable-fixes).\n- drm/xe: add interface to request physical alignment for buffer objects (stable-fixes).\n- drm/xe: move DPT l2 flush to a more sensible place (git-fixes).\n- dt-bindings: dpll: Add DPLL device and pin (jsc#PED-12745).\n- dt-bindings: dpll: Add support for Microchip Azurite chip family  (jsc#PED-12745).\n- dt-bindings: dpll: Add support for Microchip Azurite chip family (jsc#PED-12745).\n- e1000: Move cancel_work_sync to avoid deadlock (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hid: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- hid: core: do not bypass hid_hw_raw_request (stable-fixes).\n- hid: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- hid: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- hid: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- hid: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ib/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- ice, irdma: fix an off by one in error handling code (bsc#1247712).\n- ice, irdma: move interrupts code to irdma (bsc#1247712).\n- ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712).\n- ice: count combined queues using Rx/Tx count (bsc#1247712).\n- ice: devlink PF MSI-X max and min parameter (bsc#1247712).\n- ice: enable_rdma devlink param (bsc#1247712).\n- ice: fix eswitch code memory leak in reset scenario (git-fixes).\n- ice: get rid of num_lan_msix field (bsc#1247712).\n- ice: init flow director before RDMA (bsc#1247712).\n- ice: remove splitting MSI-X between features (bsc#1247712).\n- ice: simplify VF MSI-X managing (bsc#1247712).\n- ice: treat dyn_allowed only as suggestion (bsc#1247712).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- input: iqs7222 - explicitly define number of external channels (git-fixes).\n- input: xpad - adjust error handling for disconnect (git-fixes).\n- input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- io_uring/timeout: fix multishot updates (bsc#1247021).\n- io_uring: fix potential page leak in io_sqe_buffer_register() (git-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/tegra241-cmdqv: Read SMMU IDR1.CMDQS instead of hardcoding (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- irdma: free iwdev-\u003erf after removing MSI-X (bsc#1247712).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI fix after KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- kABI fixes for struct memory_block changes  (bsc#1235515,jsc#PED-12731).\n- kABI fixes for struct memory_block changes (bsc#1235515,jsc#PED-12731).\n- kABI workaround for fw_attributes_class_get() (stable-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kabi/severities: ignore two unused/dropped symbols from MEI\n- kabi: Hide adding of u64 to devlink_param_type (jsc#PED-12745).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- kvm: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ipu6: isys: Use correct pads for xlate_streams() (git-fixes).\n- media: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: verisilicon: Fix AV1 decoder clock frequency (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- mei: vsc: Destroy mutex after freeing the IRQ (git-fixes).\n- mei: vsc: Do not re-init VSC from mei_vsc_hw_reset() on stop (git-fixes).\n- mei: vsc: Drop unused vsc_tp_request_irq() and vsc_tp_free_irq() (stable-fixes).\n- mei: vsc: Event notifier fixes (git-fixes).\n- mei: vsc: Fix 'BUG: Invalid wait context' lockdep error (git-fixes).\n- mei: vsc: Run event callback from a workqueue (git-fixes).\n- mei: vsc: Unset the event callback on remove and probe errors (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mm/memory_hotplug: allow architecture to override memmap on  memory support check (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow architecture to override memmap on memory support check (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow memmap on memory hotplug request to  fallback (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow memmap on memory hotplug request to fallback (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: embed vmem_altmap details in memory block  (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: embed vmem_altmap details in memory block (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: export mhp_supports_memmap_on_memory() (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval (git-fixes).\n- mm/memory_hotplug: replace an open-coded kmemdup() in (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE  kconfig (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: split memmap_on_memory requests across memblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: support memmap_on_memory when memmap is  not aligned to pageblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: support memmap_on_memory when memmap is not aligned to pageblocks (bsc#1235515,jsc#PED-12731).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/mlx5: HWS, fix missing ip_version handling in definer (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net/smc: Fix lookup of netdev by using ib_device_get_netdev() (git-fixes bsc#1246217).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netlink: fix policy dump for int with validation callback  (jsc#PED-12745).\n- netlink: fix policy dump for int with validation callback (jsc#PED-12745).\n- netlink: specs: devlink: replace underscores with dashes in  names (jsc#PED-12745).\n- netlink: specs: devlink: replace underscores with dashes in names (jsc#PED-12745).\n- netlink: specs: nfsd: replace underscores with dashes in names (git-fixes).\n- netlink: specs: tc: replace underscores with dashes in names (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfs: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- nfs: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- nfs: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- nfs: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- nfsd: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsv4.2: another fix for listxattr (git-fixes).\n- nfsv4.2: fix listxattr to return selinux security label (git-fixes).\n- nfsv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- nfsv4: Always set NLINK even if the server does not support it (git-fixes).\n- nfsv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- pci/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- pci: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- pci: endpoint: Fix configfs group list head handling (git-fixes).\n- pci: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- pci: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- pci: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- pci: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- pci: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: Fix initialization order for firmware_attributes_class (git-fixes).\n- platform/x86: dell-sysman: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: firmware_attributes_class: Move include linux/device/class.h (stable-fixes).\n- platform/x86: firmware_attributes_class: Simplify API (stable-fixes).\n- platform/x86: hp-bioscfg: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: hp-bioscfg: Fix class device unregistration (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: make fw_attr_class constant (stable-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- pm / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO add (bsc#1243042 ltc#212167).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- pwm: rockchip: Round period/duty down on apply, up on get (git-fixes).\n- rdma/core: Rate limit GID cache warning messages (git-fixes)\n- rdma/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- rdma/hns: Drop GFP_NOWARN (git-fixes)\n- rdma/hns: Fix -Wframe-larger-than issue (git-fixes)\n- rdma/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- rdma/hns: Fix accessing uninitialized resources (git-fixes)\n- rdma/hns: Fix double destruction of rsv_qp (git-fixes)\n- rdma/hns: Get message length of ack_req from FW (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- rdma/mlx5: Fix CC counters query for MPV (git-fixes)\n- rdma/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- rdma/mlx5: Fix UMR modifying of mkey page size (git-fixes)\n- rdma/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- rdma/mlx5: Fix vport loopback for MPV device (git-fixes)\n- rdma/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- rdma/mlx5: reduce stack usage in mlx5_ib_ufile_hw_cleanup (git-fixes)\n- rdma/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- rdma/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- rdma/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: core: fix NULL dereference on unbind due to stale coupling data (stable-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1246644).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (git-fixes).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (git-fixes).\n- scsi: fnic: Set appropriate logging level for log message (bsc#1246644).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- smb3: send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- sprintf.h requires stdarg.h (git-fixes).\n- sprintf.h: mask additional include (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- staging: vchiq_arm: Make vchiq_shutdown never fail (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- supported.conf: Mark ZL3073X modules supported\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thermal: trip: Use READ_ONCE() for lockless access to trip properties (git-fixes).\n- thermal: trip: Use common set of trip type names (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: Abort suspend on soft disconnect failure (git-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- usb: serial: option: add Foxconn T99W640 (stable-fixes).\n- usb: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).    \n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: cfg80211/mac80211: correctly parse S1G beacon optional elements (git-fixes).\n- wifi: cfg80211: fix S1G beacon head validation in nl80211 (git-fixes).\n- wifi: cfg80211: remove scan request n_channels counted_by (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Create separate links for VLAN interfaces (stable-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: Write cnt before copying in ieee80211_copy_rnr_beacon() (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: finish link init before RCU publish (git-fixes).\n- wifi: mac80211: fix non-transmitted BSSID profile search (git-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: nl80211: Set num_sub_specs before looping through sub_specs (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rt2x00: fix remove callback type mismatch (git-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/CPU/AMD: Add more models to X86_FEATURE_ZEN5 (bsc#1246449).\n- x86/CPU/AMD: Improve the erratum 1386 workaround (git-fixes).\n- x86/CPU/AMD: Terminate the erratum_1386_microcode array (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/cpu: Avoid running off the end of an AMD erratum table (git-fixes).\n- x86/cpu: Expose only stepping min/max interface (git-fixes).\n- x86/cpu: Introduce new microcode matching helper (git-fixes).\n- x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id' (git-fixes).\n- x86/cpu: Replace PEBS use of 'x86_cpu_desc' use with 'x86_cpu_id' (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/mtrr: Rename mtrr_overwrite_state() to guest_force_mtrr_state() (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-18T16:01:54Z","modified":"2026-02-04T03:35:26.548367Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:02923-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Confidential Computing kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition (bsc#1139073).\n- CVE-2023-52888: media: mediatek: vcodec: Only free buffer VA that is not NULL (bsc#1228557).\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-49568: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg (bsc#1235728).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2024-57982: xfrm: state: fix out-of-bounds read during lookup (bsc#1237913).\n- CVE-2024-58053: rxrpc: Fix handling of received connection abort (bsc#1238982).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38490: net: libwx: remove duplicate page_pool_put_full_page() (bsc#1247243).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n- CVE-2025-21720: xfrm: delete intermediate secpath entry in packet offload mode (bsc#1238859).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21854: selftest/bpf: Add vsock test for sockmap rejecting unconnected (bsc#1239470).\n- CVE-2025-21868: kABI workaround for adding an header (bsc#1240180).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show() (bsc#1240610).\n- CVE-2025-21899: tracing: Fix bad hist from corrupting named_triggers list (bsc#1240577).\n- CVE-2025-21920: vlan: enforce underlying device type (bsc#1240686).\n- CVE-2025-21938: mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr (bsc#1240723).\n- CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() (bsc#1240814).\n- CVE-2025-21997: xsk: fix an integer overflow in xp_create_and_assign_umem() (bsc#1240823).\n- CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching (bsc#1241544).\n- CVE-2025-22090: mm: (un)track_pfn_copy() fix + doc improvements (bsc#1241537).\n- CVE-2025-22111: kABI fix for net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF (bsc#1241572).\n- CVE-2025-22113: ext4: define ext4_journal_destroy wrapper (bsc#1241617).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics (bsc#1242163).\n- CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).\n- CVE-2025-37756: net: tls: explicitly disallow disconnect (bsc#1242515).\n- CVE-2025-37757: tipc: fix memory leak in tipc_link_xmit (bsc#1242521).\n- CVE-2025-37786: net: dsa: free routing table on probe failure (bsc#1242725).\n- CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent() (bsc#1242849).\n- CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer() (bsc#1242850).\n- CVE-2025-37811: usb: chipidea: ci_hdrc_imx: fix usbmisc handling (bsc#1242907).\n- CVE-2025-37844: cifs: avoid NULL pointer dereference in dbg call (bsc#1242946).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37859: page_pool: avoid infinite loop to schedule delayed worker (bsc#1243051).\n- CVE-2025-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields (bsc#1242982).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37865: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported (bsc#1242954).\n- CVE-2025-37874: net: ngbe: fix memory leak in ngbe_probe() error path (bsc#1242940).\n- CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex (bsc#1243060).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37909: net: lan743x: Fix memleak issue when GSO enabled (bsc#1243467).\n- CVE-2025-37917: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37921: vxlan: vnifilter: Fix unlocked deletion of default FDB entry (bsc#1243480).\n- CVE-2025-37923: tracing: Fix oob write in trace_seq_to_buffer() (bsc#1243551).\n- CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (bsc#1243620).\n- CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot (bsc#1243628).\n- CVE-2025-37936: perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value (bsc#1243537).\n- CVE-2025-37938: tracing: Verify event formats that have '%*p..' (bsc#1243544).\n- CVE-2025-37945: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY (bsc#1243538).\n- CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks (bsc#1243664).\n- CVE-2025-37961: ipvs: fix uninit-value for saddr in do_output_route4 (bsc#1243523).\n- CVE-2025-37967: usb: typec: ucsi: displayport: Fix deadlock (bsc#1243572).\n- CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access (bsc#1243571).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-37987: pds_core: Prevent possible adminq overflow/stuck condition (bsc#1243542).\n- CVE-2025-37992: net_sched: Flush gso_skb list too during -\u003echange() (bsc#1243698).\n- CVE-2025-37995: module: ensure that kobject_put() is safe for module type kobjects (bsc#1243827).\n- CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).\n- CVE-2025-37998: openvswitch: Fix unsafe attribute parsing in output_userspace() (bsc#1243836).\n- CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).\n- CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).\n- CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).\n- CVE-2025-38018: net/tls: fix kernel panic when alloc_page failed (bsc#1244999).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38053: idpf: fix null-ptr-deref in idpf_features_check (bsc#1244746).\n- CVE-2025-38057: espintcp: fix skb leaks (bsc#1244862).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38060: bpf: abort verification if env-\u003ecur_state-\u003eloop_entry != NULL (bsc#1245155).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38072: libnvdimm/labels: Fix divide error in nd_label_data_init() (bsc#1244743).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used (git-fixes).\n- ACPI: HED: Always initialize before evged (stable-fixes).\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: OSI: Stop advertising support for '3.0 _SCP Extensions' (git-fixes).\n- ACPI: PNP: Add Intel OC Watchdog IDs to non-PNP device list (stable-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: battery: negate current when discharging (stable-fixes).\n- ACPI: bus: Bail out if acpi_kobj registration fails (stable-fixes).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Avoid sequence overread in call to strncmp() (stable-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ACPICA: Utilities: Fix spelling mistake 'Incremement' -\u003e 'Increment' (git-fixes).\n- ACPICA: exserial: do not forget to handle FFixedHW opregions for reading (git-fixes).\n- ACPICA: fix acpi operand cache leak in dswstate.c (stable-fixes).\n- ACPICA: fix acpi parse and parseext cache leaks (stable-fixes).\n- ACPICA: utilities: Fix overflow check in vsnprintf() (stable-fixes).\n- ALSA: hda/intel: Add Thinkpad E15 to PM deny list (stable-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/realtek: Add quirk for HP Spectre x360 15-df1xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14ASP10 (stable-fixes).\n- ALSA: hda/realtek: Enable PC beep passthrough for HP EliteBook 855 G7 (stable-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X507UAR (git-fixes).\n- ALSA: hda/realtek: Fix built-in mic on ASUS VivoBook X513EA (git-fixes).\n- ALSA: hda/realtek: enable headset mic on Latitude 5420 Rugged (stable-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: pcm: Fix race of buffer access at PCM OSS layer (stable-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ALSA: seq: Improve data consistency at polling (stable-fixes).\n- ALSA: usb-audio: Accept multiple protocols in GTBs (stable-fixes).\n- ALSA: usb-audio: Add Pioneer DJ DJM-V10 support (stable-fixes).\n- ALSA: usb-audio: Add a quirk for Lenovo Thinkpad Thunderbolt 3 dock (stable-fixes).\n- ALSA: usb-audio: Add implicit feedback quirk for RODE AI-1 (stable-fixes).\n- ALSA: usb-audio: Add name for HP Engage Go dock (stable-fixes).\n- ALSA: usb-audio: Check shutdown at endpoint_set_interface() (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer deref in snd_usb_power_domain_set() (git-fixes).\n- ALSA: usb-audio: Fix duplicated name in MIDI substream names (stable-fixes).\n- ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() (git-fixes).\n- ALSA: usb-audio: Rename ALSA kcontrol PCM and PCM1 for the KTMicro sound card (stable-fixes).\n- ALSA: usb-audio: Rename Pioneer mixer channel controls (git-fixes).\n- ALSA: usb-audio: Set MIDI1 flag appropriately for GTB MIDI 1.0 entry (stable-fixes).\n- ALSA: usb-audio: Skip setting clock selector for single connections (stable-fixes).\n- ALSA: usb-audio: Support multiple control interfaces (stable-fixes).\n- ALSA: usb-audio: Support read-only clock selector control (stable-fixes).\n- ALSA: usb-audio: enable support for Presonus Studio 1824c within 1810c file (stable-fixes).\n- ALSA: usb-audio: mixer: Remove temporary string use in parse_clock_source_unit (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- ice, irdma: fix an off by one in error handling code (bsc#1247712).\n- ice, irdma: move interrupts code to irdma (bsc#1247712).\n- ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712).\n- ice: count combined queues using Rx/Tx count (bsc#1247712).\n- ice: devlink PF MSI-X max and min parameter (bsc#1247712).\n- ice: enable_rdma devlink param (bsc#1247712).\n- ice: get rid of num_lan_msix field (bsc#1247712).\n- ice: init flow director before RDMA (bsc#1247712).\n- ice: remove splitting MSI-X between features (bsc#1247712).\n- ice: simplify VF MSI-X managing (bsc#1247712).\n- ice: treat dyn_allowed only as suggestion (bsc#1247712).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- irdma: free iwdev-\u003erf after removing MSI-X (bsc#1247712).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb: client: fix parsing of device numbers (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- sunrpc: fix handling of server side tls alerts (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- ASoC: Intel: avs: Fix deadlock when the failing IPC is SET_D0IX (git-fixes).\n- ASoC: Intel: avs: Verify content returned by parse_int_array() (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Add DMI quirk for Acer Aspire SW3-013 (stable-fixes).\n- ASoC: SOF: ipc4-pcm: Adjust pipeline_list-\u003epipelines allocation type (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for Lenovo Yoga Pro 7 14ASP9 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: apple: mca: Constrain channels according to TDM mask (git-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: hda: Fix RPM usage count underflow (git-fixes).\n- ASoC: codecs: pcm3168a: Allow for 24-bit in provider mode (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: imx-card: Adjust over allocation of memory in imx_card_parse_of() (stable-fixes).\n- ASoC: mediatek: mt6359: Add stub for mt6359_accdet_enable_jack_detect (stable-fixes).\n- ASoC: mediatek: mt8188: Add reference for dmic clocks (stable-fixes).\n- ASoC: mediatek: mt8188: Treat DMIC_GAINx_CUR as non-volatile (stable-fixes).\n- ASoC: meson: meson-card-utils: use of_property_present() for DT parsing (git-fixes).\n- ASoC: ops: Enforce platform maximum on initial value (stable-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: qcom: sdm845: Add error handling in sdm845_slim_snd_hw_params() (git-fixes).\n- ASoC: qcom: sm8250: explicitly set format in sm8250_be_hw_params_fixup() (stable-fixes).\n- ASoC: rt722-sdca: Add some missing readable registers (stable-fixes).\n- ASoC: soc-dai: check return value at snd_soc_dai_set_tdm_slot() (stable-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ASoC: sun4i-codec: support hp-det-gpios property (stable-fixes).\n- ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG (stable-fixes).\n- ASoC: tas2764: Enable main IRQs (git-fixes).\n- ASoC: tas2764: Mark SW_RESET as volatile (stable-fixes).\n- ASoC: tas2764: Power up/down amp on mute ops (stable-fixes).\n- ASoC: tas2764: Reinit cache on part reset (git-fixes).\n- ASoC: tas2770: Power cycle amp on ISENSE/VSENSE change (stable-fixes).\n- ASoC: tegra210_ahub: Add check to of_device_get_match_data() (stable-fixes).\n- Bluetooth: Fix NULL pointer deference on eir_get_service_data (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: L2CAP: Fix not responding with L2CAP_CR_LE_ENCRYPTION (git-fixes).\n- Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: Fix sparse errors (git-fixes).\n- Bluetooth: MGMT: Remove unused mgmt_pending_find_data (stable-fixes).\n- Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: Remove pending ACL connection attempts (stable-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix UAF Write in __hci_acl_create_connection_sync (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_conn: Only do ACL connections sequentially (stable-fixes).\n- Bluetooth: hci_core: fix list_for_each_entry_rcu usage (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Fix not using key encryption size when its known (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_qca: move the SoC type check to the right place (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Fix broadcast/PA when using an existing instance (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentation/rtla: Fix duplicate text about timerlat tracer (git-fixes).\n- Documentation/rtla: Fix typo in common_timerlat_description.rst (git-fixes).\n- Documentation/rtla: Fix typo in rtla-timerlat.rst (git-fixes).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: fix typo in root= kernel parameter description (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: lenovo: Restrict F7/9/11 mode to compact keyboards only (git-fixes).\n- HID: quirks: Add ADATA XPG alpha wireless mouse support (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- HID: usbkbd: Fix the bit shift number for LED_KANA (stable-fixes).\n- HID: wacom: fix kobject reference count leak (git-fixes).\n- HID: wacom: fix memory leak on kobject creation failure (git-fixes).\n- HID: wacom: fix memory leak on sysfs attribute creation failure (git-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: gpio-keys - fix possible concurrent access in gpio_keys_irq_timer() (git-fixes).\n- Input: ims-pcu - check record size in ims_pcu_flash_firmware() (git-fixes).\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: sparcspkr - avoid unannotated fall-through (stable-fixes).\n- Input: xpad - add more controllers (stable-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- KVM: SVM: Remove the need to trigger an UNBLOCK event on AP creation (git-fixes).\n- KVM: powerpc: Enable commented out BUILD_BUG_ON() assertion (bsc#1215199).\n- KVM: s390: rename PROT_NONE to PROT_TYPE_DUMMY (git-fixes bsc#1245225).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- MyBS: Correctly generate build flags for non-multibuild package limit (bsc# 1244241)\n- MyBS: Do not build kernel-obs-qa with limit_packages\n- MyBS: Simplify qa_expr generation\n- NFC: nci: uart: Set tty-\u003edisc_data only in success path (git-fixes).\n- NFS: Do not allow waiting for exiting tasks (git-fixes).\n- NFSD: Insulate nfsd4_encode_read_plus() from page boundaries in the encode buffer (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: Check for delegation validity in nfs_start_delegation_return_locked() (git-fixes).\n- NFSv4: Treat ENETUNREACH errors as fatal for state recovery (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/DPC: Initialize aer_err_info before using it (git-fixes).\n- PCI/DPC: Log Error Source ID only when valid (git-fixes).\n- PCI/DPC: Use defines with DPC reason fields (git-fixes).\n- PCI/MSI: Size device MSI domain with the maximum number of vectors (git-fixes).\n- PCI/PM: Set up runtime PM even for devices without PCI PM (git-fixes).\n- PCI: Explicitly put devices into D0 when initializing (git-fixes).\n- PCI: Fix lock symmetry in pci_slot_unlock() (git-fixes).\n- PCI: Fix old_size lower bound in calculate_iosize() too (stable-fixes).\n- PCI: apple: Set only available ports up (git-fixes).\n- PCI: apple: Use gpiod_set_value_cansleep in probe flow (git-fixes).\n- PCI: brcmstb: Add a softdep to MIP MSI-X driver (stable-fixes).\n- PCI: brcmstb: Expand inbound window size up to 64GB (stable-fixes).\n- PCI: cadence-ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: cadence: Fix runtime atomic count underflow (git-fixes).\n- PCI: dw-rockchip: Fix PHY function call sequence in rockchip_pcie_phy_deinit() (git-fixes).\n- PCI: dw-rockchip: Remove PCIE_L0S_ENTRY check from rockchip_pcie_link_up() (git-fixes).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: dwc: ep: Correct PBA offset in .set_msix() callback (git-fixes).\n- PCI: dwc: ep: Ensure proper iteration over outbound map windows (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- PCI: vmd: Disable MSI remapping bypass under Xen (stable-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- PM: runtime: fix denying of auto suspend in pm_suspend_timer_fn() (stable-fixes).\n- PM: sleep: Fix power.is_suspended cleanup for direct-complete devices (git-fixes).\n- PM: sleep: Print PM debug messages during hibernation (git-fixes).\n- PM: wakeup: Delete space in the end of string shown by pm_show_wakelocks() (git-fixes).\n- RDMA/core: Fix best page size finding when it can cross SG entries (git-fixes)\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/uverbs: Propagate errors from rdma_lookup_get_uobject() (git-fixes)\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Remove compress-vmlinux.sh\n- Remove host-memcpy-hack.h \n- Remove try-disable-staging-driver \n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'ALSA: usb-audio: Skip setting clock selector for single connections' (stable-fixes).\n- Revert 'arm64: dts: allwinner: h6: Use RSB for AXP805 PMIC (git-fixes)\n- Revert 'bus: ti-sysc: Probe for l4_wkup and l4_cfg interconnect devices first' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/amdgpu: do not allow userspace to create a doorbell BO' (stable-fixes).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'kABI: ipv6: save dontfrag in cork (git-fixes).'\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'wifi: mt76: mt7996: fill txd by host driver' (stable-fixes).\n- SUNRPC: Do not allow waiting for exiting tasks (git-fixes).\n- SUNRPC: Prevent hang on NFS mount with xprtsec=[m]tls (git-fixes).\n- SUNRPC: rpc_clnt_set_transport() must not change the autobind setting (git-fixes).\n- SUNRPC: rpcbind should never reset the port to the value '0' (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- USB: serial: pl2303: add new chip PL2303GC-Q20 and PL2303GT-2AB (stable-fixes).\n- VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify (git-fixes).\n- accel/qaic: Mask out SR-IOV PCI resources (stable-fixes).\n- acpi-cpufreq: Fix nominal_freq units to KHz in get_max_boost_ratio() (git-fixes).\n- add bug reference to existing hv_storvsc change (bsc#1245455).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- arm64: dts: marvell: uDPU: define pinctrl state for alarm LEDs (git-fixes)\n- ata: libata-eh: Do not use ATAPI DMA for a device limited to PIO mode (stable-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 (stable-fixes).\n- ath10k: snoc: fix unbalanced IRQ enable in crash recovery (git-fixes).\n- backlight: pm8941: Add NULL check in wled_configure() (git-fixes).\n- bnxt: properly flush XDP redirect lists (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Force uprobe bpf program to always return 0 (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- bs-upload-kernel: Pass limit_packages also on multibuild\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix fsync of files with no hard links not persisting deletion (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid data space release when truncating block in NOCOW mode (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix qgroup reservation leak on failure to allocate ordered extent (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: fix wrong start offset for delalloc space release during mmap write (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: remove end_no_trans label from btrfs_log_inode_parent() (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: simplify condition for logging new dentries at btrfs_log_inode_parent() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device (git-fixes).\n- bus: fsl-mc: fix GET/SET_TAILDROP command ids (git-fixes).\n- bus: fsl-mc: fix double-free on mc_dev (git-fixes).\n- bus: fsl-mc: increase MC_CMD_COMPLETION_TIMEOUT_MS value (stable-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- bus: mhi: host: Fix conflict between power_up and SYSERR (git-fixes).\n- calipso: Fix null-ptr-deref in calipso_req_{set,del}attr() (git-fixes).\n- can: c_can: Use of_property_present() to test existence of DT property (stable-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- can: tcan4x5x: fix power regulator retrieval during probe (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- ceph: Fix incorrect flush end position calculation (git-fixes).\n- ceph: allocate sparse_ext map only for sparse reads (git-fixes).\n- ceph: fix memory leaks in __ceph_sync_read() (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cgroup/cpuset: Fix race between newly created partition and dying one (bsc#1241166).\n- cifs: change tcon status when need_reconnect is set on it (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Fix brown-bag boolean thinko in (git-fixes)\n- clocksource: Make watchdog and suspend-timing multiplication (git-fixes)\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: lrw - Only add ecb if it is not already there (git-fixes).\n- crypto: lzo - Fix compression buffer overrun (stable-fixes).\n- crypto: marvell/cesa - Avoid empty transfer descriptor (git-fixes).\n- crypto: marvell/cesa - Do not chain submitted requests (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: marvell/cesa - Handle zero-length skcipher requests (git-fixes).\n- crypto: octeontx2 - suppress auth failure screaming due to negative tests (stable-fixes).\n- crypto: qat - add shutdown handler to qat_420xx (git-fixes).\n- crypto: qat - add shutdown handler to qat_4xxx (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: skcipher - Zap type in crypto_alloc_sync_skcipher (stable-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- crypto: sun8i-ce - move fallback ahash_request to the end of the struct (git-fixes).\n- crypto: sun8i-ce-cipher - fix error handling in sun8i_ce_cipher_prepare() (git-fixes).\n- crypto: sun8i-ss - do not use sg_dma_len before calling DMA functions (git-fixes).\n- crypto: xts - Only add ecb if it is not already there (git-fixes).\n- devlink: Fix referring to hw_addr attribute during state validation (git-fixes).\n- devlink: fix port dump cmd type (git-fixes).\n- dlm: mask sk_shutdown value (bsc#1228854).\n- dlm: use SHUT_RDWR for SCTP shutdown (bsc#1228854).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: idxd: cdev: Fix uninitialized use of sva in idxd_cdev_open (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: ti: Add NULL check in udma_probe() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- drivers/rapidio/rio_cm.c: prevent possible heap overwrite (stable-fixes).\n- drm/amd/display/dm: drop hw_support check in amdgpu_dm_i2c_xfer() (stable-fixes).\n- drm/amd/display: Add null pointer check for get_first_active_display() (git-fixes).\n- drm/amd/display: Do not try AUX transactions on disconnected link (stable-fixes).\n- drm/amd/display: Fix incorrect DPCD configs while Replay/PSR switch (stable-fixes).\n- drm/amd/display: Guard against setting dispclk low for dcn31x (stable-fixes).\n- drm/amd/display: Increase block_sequence array size (stable-fixes).\n- drm/amd/display: Initial psr_version with correct setting (stable-fixes).\n- drm/amd/display: Skip checking FRL_MODE bit for PCON BW determination (stable-fixes).\n- drm/amd/display: Update CR AUX RD interval interpretation (stable-fixes).\n- drm/amd/display: fix link_set_dpms_off multi-display MST corner case (stable-fixes).\n- drm/amd/display: remove minimum Dispclk and apply oem panel timing (stable-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: Do not program AGP BAR regs under SRIOV in gfxhub_v1_0.c (stable-fixes).\n- drm/amdgpu: Set snoop bit for SDMA for MI series (stable-fixes).\n- drm/amdgpu: Update SRIOV video codec caps (stable-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdgpu: enlarge the VBIOS binary size limit (stable-fixes).\n- drm/amdgpu: reset psp-\u003ecmd to NULL after releasing the buffer (stable-fixes).\n- drm/amdgpu: switch job hw_fence to amdgpu_fence (git-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/amdkfd: KFD release_work possible circular locking (stable-fixes).\n- drm/amdkfd: Set per-process flags only once cik/vi (stable-fixes).\n- drm/ast: Find VBIOS mode from regular display size (stable-fixes).\n- drm/ast: Fix comment on modeset lock (git-fixes).\n- drm/atomic: clarify the rules around drm_atomic_state-\u003eallow_modeset (stable-fixes).\n- drm/bridge: cdns-dsi: Check return value when getting default PHY config (git-fixes).\n- drm/bridge: cdns-dsi: Fix connecting to next bridge (git-fixes).\n- drm/bridge: cdns-dsi: Fix phy de-init and flag it so (git-fixes).\n- drm/bridge: cdns-dsi: Fix the clock variable for mode_valid() (git-fixes).\n- drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready (git-fixes).\n- drm/bridge: lt9611uxc: Fix an error handling path in lt9611uxc_probe() (git-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/etnaviv: Protect the scheduler's pending list with its lock (git-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 (git-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/i915: fix build error some more (git-fixes).\n- drm/mediatek: Fix kobject put for component sub-drivers (git-fixes).\n- drm/mediatek: mtk_dpi: Add checks for reg_h_fre_con existence (stable-fixes).\n- drm/mediatek: mtk_drm_drv: Fix kobject put for mtk_mutex device ptr (git-fixes).\n- drm/mediatek: mtk_drm_drv: Unbind secondary mmsys components on err (git-fixes).\n- drm/msm/disp: Correct porch timing for SDM845 (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm/dsi/dsi_phy_10nm: Fix missing initial VCO rate (git-fixes).\n- drm/msm/gpu: Fix crash when throttling GPU immediately during boot (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/nouveau/bl: increase buffer size to avoid truncate warning (git-fixes).\n- drm/panel-edp: Add Starry 116KHD024006 (stable-fixes).\n- drm/panel: samsung-sofef00: Drop s6e3fc2x01 support (git-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/rockchip: vop2: Add uv swap for cluster window (stable-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/ssd130x: fix ssd132x_clear_screen() columns (git-fixes).\n- drm/tegra: Assign plane type before registration (git-fixes).\n- drm/tegra: Fix a possible null pointer dereference (git-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/tegra: rgb: Fix the unbound reference count (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/udl: Unregister device before cleaning up on disconnect (git-fixes).\n- drm/v3d: Add clock handling (stable-fixes).\n- drm/vc4: tests: Use return instead of assert (git-fixes).\n- drm/vkms: Adjust vkms_state-\u003eactive_planes allocation type (git-fixes).\n- drm/vmwgfx: Add seqno waiter for sync_files (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- drm: Add valid clones check (stable-fixes).\n- drm: bridge: adv7511: fill stream capabilities (stable-fixes).\n- drm: rcar-du: Fix memory leak in rcar_du_vsps_init() (git-fixes).\n- e1000e: set fixed clock frequency indication for Nahum 11 and Nahum 13 (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbcon: Make sure modelist not set on unregistered console (stable-fixes).\n- fbcon: Use correct erase colour for clearing in fbcon (stable-fixes).\n- fbdev/efifb: Remove PM for parent device (bsc#1244261).\n- fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var (git-fixes).\n- fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod() (git-fixes).\n- fbdev: core: tileblit: Implement missing margin clearing for tileblit (stable-fixes).\n- fbdev: fsl-diu-fb: add missing device_remove_file() (stable-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- fgraph: Still initialize idle shadow stacks when starting (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES (git-fixes).\n- firmware: arm_ffa: Reject higher major version as incompatible (stable-fixes).\n- firmware: arm_ffa: Set dma_mask for ffa devices (stable-fixes).\n- firmware: arm_scmi: Relax duplicate name constraint across protocol ids (stable-fixes).\n- firmware: psci: Fix refcount leak in psci_dt_init (git-fixes).\n- fpga: altera-cvp: Increase credit timeout (stable-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/nfs/read: fix double-unlock bug in nfs_return_empty_folio() (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf3: only get IRQ for device instance 0 (git-fixes).\n- gpio: pca953x: Simplify code with cleanup helpers (stable-fixes).\n- gpio: pca953x: Split pca953x_restore_context() and pca953x_save_context() (stable-fixes).\n- gpio: pca953x: fix IRQ storm on system wake up (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: Revert 'Do not WARN on gpiod_put() for optional GPIO' (stable-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- gve: Fix RX_BUFFERS_POSTED stat to report per-queue fill_cnt (git-fixes).\n- gve: add missing NULL check for gve_alloc_pending_packet() in TX DQO (git-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hwmon: (asus-ec-sensors) check sensor index in read_string() (git-fixes).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (dell-smm) Increment the number of fans (stable-fixes).\n- hwmon: (ftsteutates) Fix TOCTOU race in fts_read() (git-fixes).\n- hwmon: (gpio-fan) Add missing mutex locks (stable-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (nct6775): Actually make use of the HWMON_NCT6775 symbol namespace (git-fixes).\n- hwmon: (occ) Rework attribute registration for stack usage (git-fixes).\n- hwmon: (occ) fix unaligned accesses (git-fixes).\n- hwmon: (peci/dimmtemp) Do not provide fake thresholds data (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwmon: (xgene-hwmon) use appropriate type for the latency value (stable-fixes).\n- hwmon: corsair-psu: add USB id of HX1200i Series 2023 psu (git-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: designware: Invoke runtime suspend on quick slave re-registration (stable-fixes).\n- i2c: npcm: Add clock toggle recovery (stable-fixes).\n- i2c: pxa: fix call balance of i2c-\u003eclk handling routines (stable-fixes).\n- i2c: qup: Vote for interconnect bandwidth to DRAM (stable-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: robotfuzz-osif: disable zero-length read messages (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: tegra: check msg length in SMBUS block read (bsc#1242086)\n- i2c: tiny-usb: disable zero-length read messages (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- i3c: master: svc: Fix implicit fallthrough in svc_i3c_master_ibi_work() (git-fixes).\n- i3c: master: svc: Fix missing STOP for master request (stable-fixes).\n- i3c: master: svc: Flush FIFO before sending Dynamic Address Assignment(DAA) (stable-fixes).\n- i40e: retry VFLR handling if there is ongoing VF reset (git-fixes).\n- i40e: return false from i40e_reset_vf if reset is in progress (git-fixes).\n- ice: Fix LACP bonds without SRIOV environment (git-fixes).\n- ice: create new Tx scheduler nodes for new queues only (git-fixes).\n- ice: fix Tx scheduler error handling in XDP callback (git-fixes).\n- ice: fix rebuilding the Tx scheduler tree for large queue counts (git-fixes).\n- ice: fix vf-\u003enum_mac count with port representors (git-fixes).\n- ieee802154: ca8210: Use proper setters and getters for bitwise types (stable-fixes).\n- iio: accel: fxls8962af: Fix temperature scan element sign (git-fixes).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7124: Fix 3dB filter frequency reading (git-fixes).\n- iio: adc: ad7606_spi: fix reg write value mask (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: filter: admv8818: Support frequencies \u003e= 2^32 (git-fixes).\n- iio: filter: admv8818: fix band 4, state 15 (git-fixes).\n- iio: filter: admv8818: fix integer overflow (git-fixes).\n- iio: filter: admv8818: fix range calculation (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: imu: inv_icm42600: Fix temperature calculation (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- ima: Suspend PCR extends and log appends when rebooting (bsc#1210025 ltc#196650).\n- ima: process_measurement() needlessly takes inode_lock() on MAY_READ (stable-fixes).\n- intel_th: avoid using deprecated page-\u003emapping, index fields (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- iommu: Protect against overflow in iommu_pgsize() (git-fixes).\n- iommu: Skip PASID validation for devices without PASID capability (bsc#1244100)\n- iommu: Validate the PASID in iommu_attach_device_pasid() (bsc#1244100)\n- ip6mr: fix tables suspicious RCU usage (git-fixes).\n- ip_tunnel: annotate data-races around t-\u003eparms.link (git-fixes).\n- ipmr: fix incorrect parameter validation in the ip_mroute_getsockopt() function (git-fixes).\n- ipmr: fix tables suspicious RCU usage (git-fixes).\n- ipv4: Convert ip_route_input() to dscp_t (git-fixes).\n- ipv4: Correct/silence an endian warning in __ip_do_redirect (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: save dontfrag in cork (git-fixes).\n- ipvs: Always clear ipvs_property flag in skb_scrub_packet() (git-fixes).\n- isolcpus: fix bug in returning number of allocated cpumask (bsc#1243774).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jffs2: check jffs2_prealloc_raw_node_refs() result in few other places (git-fixes).\n- jffs2: check that raw node were preallocated before writing summary (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI fix after KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- kABI workaround for hda_codec.beep_just_power_on flag (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: PCI: endpoint: Retain fixed-size BAR size as well as aligned size (git-fixes).\n- kABI: ipv6: save dontfrag in cork (git-fixes).\n- kABI: serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- kabi: restore layout of struct cgroup_subsys (bsc#1241166).\n- kabi: restore layout of struct mem_control (jsc#PED-12551).\n- kabi: restore layout of struct page_counter (jsc#PED-12551).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-obs-qa: Do not depend on srchash when qemu emulation is used In this case the dependency is never fulfilled\n- kernel-source: Do not use multiple -r in sed parameters\n- kernel-source: Remove log.sh from sources\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- leds: pwm-multicolor: Add check for fwnode_property_read_u32 (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- loop: Add sanity check for read/write_iter (git-fixes).\n- loop: add file_start_write() and file_end_write() (git-fixes).\n- mailbox: use error ret code of of_parse_phandle_with_args() (stable-fixes).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- md/raid1,raid10: do not handle IO error for REQ_RAHEAD and REQ_NOWAIT (git-fixes).\n- md/raid1: Add check for missing source disk in process_checks() (git-fixes).\n- media: adv7180: Disable test-pattern control on adv7180 (stable-fixes).\n- media: c8sectpfe: Call of_node_put(i2c_bus) only once in c8sectpfe_probe() (stable-fixes).\n- media: ccs-pll: Check for too high VT PLL multiplier in dual PLL case (git-fixes).\n- media: ccs-pll: Correct the upper limit of maximum op_pre_pll_clk_div (git-fixes).\n- media: ccs-pll: Start OP pre-PLL multiplier search from correct value (git-fixes).\n- media: ccs-pll: Start VT pre-PLL multiplier search from correct value (git-fixes).\n- media: cx231xx: set device_caps for 417 (stable-fixes).\n- media: cxusb: no longer judge rbuf when the write fails (git-fixes).\n- media: davinci: vpif: Fix memory leak in probe error path (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: gspca: Add error handling for stv06xx_read_sensor() (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: i2c: imx219: Correct the minimum vblanking value (stable-fixes).\n- media: imx-jpeg: Cleanup after an allocation error (git-fixes).\n- media: imx-jpeg: Drop the first error frames (git-fixes).\n- media: imx-jpeg: Move mxc_jpeg_free_slot_data() ahead (git-fixes).\n- media: imx-jpeg: Reset slot data pointers when freed (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: nxp: imx8-isi: better handle the m2m usage_count (git-fixes).\n- media: omap3isp: use sgtable-based scatterlist wrappers (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: ov5675: suppress probe deferral errors (git-fixes).\n- media: ov8856: suppress probe deferral errors (git-fixes).\n- media: qcom: camss: csid: Only add TPG v4l2 ctrl if TPG hardware is available (stable-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: rkvdec: Fix frame size enumeration (git-fixes).\n- media: tc358746: improve calculation of the D-PHY timing registers (stable-fixes).\n- media: test-drivers: vivid: do not call schedule in loop (stable-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Add sanity check to uvc_ioctl_xu_ctrl_map (stable-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: uvcvideo: Fix deferred probing error (git-fixes).\n- media: uvcvideo: Handle uvc menu translation inside uvc_get_le_value (stable-fixes).\n- media: uvcvideo: Return the number of processed controls (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: v4l2-dev: fix error handling in __video_register_device() (git-fixes).\n- media: v4l: Memset argument to 0 before calling get_mbus_config pad op (stable-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: Fix probe error handling (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: videobuf2: use sgtable-based scatterlist wrappers (git-fixes).\n- media: vidtv: Terminating the subsequent process of initialization failure (git-fixes).\n- media: vivid: Change the siize of the composing (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: exynos-lpass: Avoid calling exynos_lpass_disable() twice in exynos_lpass_remove() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- mfd: stmpe-spi: Correct the name used in MODULE_DEVICE_TABLE (git-fixes).\n- mfd: tps65219: Remove TPS65219_REG_TI_DEV_ID check (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mkspec: Exclude rt flavor from kernel-syms dependencies (bsc#1244337).\n- mm, memcg: cg2 memory{.swap,}.peak write handlers (jsc#PED-12551).\n- mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431).\n- mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431).\n- mm/memcontrol: export memcg.swap watermark via sysfs for v2 memcg (jsc#PED-12551).\n- mmc: Add quirk to disable DDR50 tuning (stable-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: dw_mmc: add exynos7870 DW MMC support (stable-fixes).\n- mmc: host: Wait for Vdd to settle on card power off (stable-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci: Disable SD card clock before changing parameters (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: nand: ecc-mxic: Fix use of uninitialized variable ret (git-fixes).\n- mtd: nand: sunxi: Add randomizer configuration before randomizer enable (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: sunxi: Add randomizer configuration in sunxi_nfc_hw_ecc_write_chunk (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- neighbour: Do not let neigh_forced_gc() disable preemption for long (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds clause 45 read/write access (git-fixes).\n- net/mdiobus: Fix potential out-of-bounds read/write access (git-fixes).\n- net/mlx4_en: Prevent potential integer overflow calculating Hz (git-fixes).\n- net/mlx5: Add error handling in mlx5_query_nic_vport_node_guid() (git-fixes).\n- net/mlx5: Ensure fw pages are always allocated on same NUMA (git-fixes).\n- net/mlx5: Fix ECVF vports unload on shutdown flow (git-fixes).\n- net/mlx5: Fix return value when searching for existing flow group (git-fixes).\n- net/mlx5_core: Add error handling inmlx5_query_nic_vport_qkey_viol_cntr() (git-fixes).\n- net/mlx5e: Fix leak of Geneve TLV option object (git-fixes).\n- net/neighbor: clear error in case strict check is not set (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: fix use-after-free in taprio_dev_notifier (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net: Fix TOCTOU issue in sk_is_readable() (git-fixes).\n- net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) (git-fixes).\n- net: add rcu safety to rtnl_prop_list_size() (git-fixes).\n- net: fix udp gso skb_segment after pull from frag_list (git-fixes).\n- net: give more chances to rcu in netdev_wait_allrefs_any() (git-fixes).\n- net: ice: Perform accurate aRFS flow match (git-fixes).\n- net: ipv4: fix a memleak in ip_setup_cork (git-fixes).\n- net: linkwatch: use system_unbound_wq (git-fixes).\n- net: mana: Add support for Multi Vports on Bare metal (bsc#1244229).\n- net: mana: Record doorbell physical address in PF mode (bsc#1244229).\n- net: page_pool: fix warning code (git-fixes).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: clear phydev-\u003edevlink when the link is deleted (git-fixes).\n- net: phy: fix up const issues in to_mdio_device() and to_phy_device() (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: move phy_link_change() prior to mdio_bus_phy_may_suspend() (bsc#1243538)\n- net: phy: mscc: Fix memory leak when using one step timestamping (git-fixes).\n- net: phy: mscc: Stop clearing the the UDPv4 checksum for L2 frames (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: sched: cls_u32: Fix allocation size in u32_init() (git-fixes).\n- net: sched: consistently use rcu_replace_pointer() in taprio_change() (git-fixes).\n- net: sched: em_text: fix possible memory leak in em_text_destroy() (git-fixes).\n- net: sched: fix erspan_opt settings in cls_flower (git-fixes).\n- net: usb: aqc111: debug info before sanitation (git-fixes).\n- net: usb: aqc111: fix error handling of usbnet read calls (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: wwan: t7xx: Fix napi rx poll issue (git-fixes).\n- net_sched: ets: fix a race in ets_qdisc_change() (git-fixes).\n- net_sched: prio: fix a race in prio_tune() (git-fixes).\n- net_sched: red: fix a race in __red_change() (git-fixes).\n- net_sched: sch_fifo: implement lockless __fifo_dump() (bsc#1237312)\n- net_sched: sch_sfq: reject invalid perturb period (git-fixes).\n- net_sched: sch_sfq: use a temporary work area for validating configuration (bsc#1232504)\n- net_sched: tbf: fix a race in tbf_change() (git-fixes).\n- netdev-genl: Hold rcu_read_lock in napi_get (git-fixes).\n- netlink: fix potential sleeping issue in mqueue_flush_file (git-fixes).\n- netlink: specs: dpll: replace underscores with dashes in names (git-fixes).\n- netpoll: Use rcu_access_pointer() in __netpoll_setup (git-fixes).\n- netpoll: hold rcu read lock in __netpoll_send_skb() (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: Initialize ssc before laundromat_work to prevent NULL dereference (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request (git-fixes).\n- nfsd: validate the nfsd_serv pointer before calling svc_wake_up (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- ntp: Clamp maxerror and esterror to operating range (git-fixes)\n- ntp: Remove invalid cast in time offset math (git-fixes)\n- ntp: Safeguard against time_constant overflow (git-fixes)\n- nvme-fc: do not reference lsrsp after failure (bsc#1245193).\n- nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (git-fixes).\n- nvme-pci: add quirks for WDC Blue SN550 15b7:5009 (git-fixes).\n- nvme-pci: add quirks for device 126f:1001 (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: always punt polled uring_cmd end_io work to task_work (git-fixes).\n- nvme: fix command limits status code (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix implicit bool to flags conversion (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-fc: free pending reqs on tgtport unregister (bsc#1245193).\n- nvmet-fc: take tgtport refs for portentry (bsc#1245193).\n- nvmet-fcloop: access fcpreq only when holding reqlock (bsc#1245193).\n- nvmet-fcloop: add missing fcloop_callback_host_done (bsc#1245193).\n- nvmet-fcloop: allocate/free fcloop_lsreq directly (bsc#1245193).\n- nvmet-fcloop: do not wait for lport cleanup (bsc#1245193).\n- nvmet-fcloop: drop response if targetport is gone (bsc#1245193).\n- nvmet-fcloop: prevent double port deletion (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_delete_local_port (bsc#1245193).\n- nvmet-fcloop: refactor fcloop_nport_alloc and track lport (bsc#1245193).\n- nvmet-fcloop: remove nport from list on last user (bsc#1245193).\n- nvmet-fcloop: track ref counts for nports (bsc#1245193).\n- nvmet-fcloop: update refs on tfcp_req (bsc#1245193).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- orangefs: Do not truncate file size (git-fixes).\n- pNFS/flexfiles: Report ENETDOWN as a connection error (git-fixes).\n- page_pool: Fix use-after-free in page_pool_recycle_in_ring (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: core: do not require set_mode() callback for phy_get_mode() to work (stable-fixes).\n- phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Add support to initialize the bus (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Assert PLL reset on PHY power off (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Lock around hardware registers and driver data (git-fixes).\n- phy: renesas: rcar-gen3-usb2: Move IRQ request in probe (stable-fixes).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl-tegra: Restore SFSEL bit when freeing pins (stable-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_gpio_get_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_gpio_set_direction() (stable-fixes).\n- pinctrl: armada-37xx: propagate error from armada_37xx_pmx_set_by_name() (stable-fixes).\n- pinctrl: armada-37xx: set GPIO output value before setting direction (git-fixes).\n- pinctrl: armada-37xx: use correct OUTPUT_VAL register for GPIOs \u003e 31 (git-fixes).\n- pinctrl: at91: Fix possible out-of-boundary access (git-fixes).\n- pinctrl: bcm281xx: Use 'unsigned int' instead of bare 'unsigned' (stable-fixes).\n- pinctrl: devicetree: do not goto err when probing hogs in pinctrl_dt_to_map (stable-fixes).\n- pinctrl: mcp23s08: Reset all pins to input at probe (stable-fixes).\n- pinctrl: meson: define the pull up/down resistor value as 60 kOhm (stable-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: qcom: pinctrl-qcm2290: Add missing pins (git-fixes).\n- pinctrl: st: Drop unused st_gpio_bank() function (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinctrl: tegra: Fix off by one in tegra_pinctrl_get_group() (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86/amd: pmc: Clear metrics table at start of cycle (git-fixes).\n- platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: dell_rbu: Fix list usage (git-fixes).\n- platform/x86: dell_rbu: Stop overwriting data buffer (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (git-fixes).\n- platform/x86: fujitsu-laptop: Support Lifebook S2110 hotkeys (stable-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: ideapad-laptop: use usleep_range() for EC polling (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- platform/x86: thinkpad_acpi: Ignore battery threshold change event notification (stable-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (git-fixes).\n- platform/x86: thinkpad_acpi: Support also NEC Lavie X1475JAS (stable-fixes).\n- power: reset: at91-reset: Optimize at91_reset() (git-fixes).\n- power: supply: bq27xxx: Retrieve again when busy (stable-fixes).\n- power: supply: collie: Fix wakeup source leaks on device unbind (stable-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- powerpc/eeh: Fix missing PE bridge reconfiguration during VFIO EEH recovery (bsc#1215199).\n- powerpc/powernv/memtrace: Fix out of bounds issue in memtrace mmap (bsc#1244309 ltc#213790).\n- powerpc/pseries/msi: Avoid reading PCI device registers in reduced power states (bsc#1215199).\n- powerpc/vas: Return -EINVAL if the offset is non-zero in mmap() (bsc#1244309 ltc#213790).\n- pstore: Change kmsg_bytes storage size to u32 (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- ptp: remove ptp-\u003en_vclocks check logic in ptp_vclock_in_use() (git-fixes).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- r8152: add vendor/device ID pair for Dell Alienware AW1022z (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: ad5398: Add device tree support (stable-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: max14577: Add error check for max14577_read_reg() (git-fixes).\n- regulator: max20086: Change enable gpio to optional (git-fixes).\n- regulator: max20086: Fix MAX200086 chip id (git-fixes).\n- regulator: max20086: Fix refcount leak in max20086_parse_regulators_dt() (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/check-for-config-changes: add more to IGNORED_CONFIGS_RE Useful when someone tries (needs) to build the kernel with clang.\n- rpm/kernel-source.changes.old: Drop bogus bugzilla reference (bsc#1244725)\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879)\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rpm: Stop using is_kotd_qa macro \n- rtc: Fix offset calculation for .start_secs \u0026lt; 0 (git-fixes).\n- rtc: Make rtc_time64_to_tm() support dates before 1970 (stable-fixes).\n- rtc: at91rm9200: drop unused module alias (git-fixes).\n- rtc: cmos: use spin_lock_irqsave in cmos_interrupt (git-fixes).\n- rtc: cpcap: drop unused module alias (git-fixes).\n- rtc: da9063: drop unused module alias (git-fixes).\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: ds1307: stop disabling alarms on probe (stable-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: jz4740: drop unused module alias (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pm8xxx: drop unused module alias (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3032: fix EERD location (stable-fixes).\n- rtc: s3c: drop unused module alias (git-fixes).\n- rtc: sh: assign correct interrupts with DT (git-fixes).\n- rtc: stm32: drop unused module alias (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Allow re-add of a reserved but not yet removed device (bsc#1244145).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix __pcilg_mio_inuser() inline assembly (git-fixes bsc#1245226).\n- s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs (git-fixes bsc#1244145).\n- s390/pci: Fix potential double remove of hotplug slot (bsc#1244145).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pci: Prevent self deletion in disable_slot() (bsc#1244145).\n- s390/pci: Remove redundant bus removal and disable from zpci_release_device() (bsc#1244145).\n- s390/pci: Serialize device addition and removal (bsc#1244145).\n- s390/pci: introduce lock to synchronize state of zpci_dev's (jsc#PED-10253 bsc#1244145).\n- s390/pci: remove hotplug slot when releasing the device (bsc#1244145).\n- s390/pci: rename lock member in struct zpci_dev (jsc#PED-10253 bsc#1244145).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390/tty: Fix a potential memory leak bug (git-fixes bsc#1245228).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- scsi: Improve CDL control (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: dc395x: Remove DEBUG conditional compilation (git-fixes).\n- scsi: dc395x: Remove leftover if statement in reselect() (git-fixes).\n- scsi: elx: efct: Fix memory leak in efct_hw_parse_filter() (git-fixes).\n- scsi: hisi_sas: Call I_T_nexus after soft reset for SATA disk (git-fixes).\n- scsi: hisi_sas: Fix I/O errors caused by hardware port ID changes (git-fixes).\n- scsi: iscsi: Fix incorrect error path labels for flashnode operations (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Block zero-length ATA VPD inquiry (git-fixes).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: mpi3mr: Add level check to control event logging (git-fixes).\n- scsi: mpt3sas: Send a diag reset if target reset fails (git-fixes).\n- scsi: pm80xx: Set phy_attached to zero when device is gone (git-fixes).\n- scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- scsi: sd_zbc: block: Respect bio vector limits for REPORT ZONES buffer (git-fixes).\n- scsi: st: ERASE does not change tape location (git-fixes).\n- scsi: st: Restore some drive settings after reset (git-fixes).\n- scsi: st: Tighten the page format heuristics with MODE SELECT (git-fixes).\n- scsi: storvsc: Do not report the host packet status as the hv status (git-fixes).\n- scsi: storvsc: Increase the timeouts to storvsc_timeout (git-fixes).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix bpf_nf selftest failure (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- selftests/mm: restore default nr_hugepages value during cleanup in hugetlb_reparenting_test.sh (git-fixes).\n- selftests/net: have `gro.sh -t` return a correct exit code (stable-fixes).\n- selftests/seccomp: fix syscall_restart test for arm compat (git-fixes).\n- serial: Fix potential null-ptr-deref in mlb_usio_probe() (git-fixes).\n- serial: imx: Restore original RXTL for console to fix data loss (git-fixes).\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (git-fixes).\n- serial: sh-sci: Move runtime PM enable to sci_probe_single() (stable-fixes).\n- serial: sh-sci: Save and restore more registers (git-fixes).\n- serial: sh-sci: Update the suspend/resume support (stable-fixes).\n- smb3: fix Open files on server counter going negative (git-fixes).\n- smb: client: Use str_yes_no() helper function (git-fixes).\n- smb: client: allow more DFS referrals to be cached (git-fixes).\n- smb: client: avoid unnecessary reconnects when refreshing referrals (git-fixes).\n- smb: client: change return value in open_cached_dir_by_dentry() if !cfids (git-fixes).\n- smb: client: do not retry DFS targets on server shutdown (git-fixes).\n- smb: client: do not trust DFSREF_STORAGE_SERVER bit (git-fixes).\n- smb: client: do not try following DFS links in cifs_tree_connect() (git-fixes).\n- smb: client: fix DFS interlink failover (git-fixes).\n- smb: client: fix DFS mount against old servers with NTLMSSP (git-fixes).\n- smb: client: fix hang in wait_for_response() for negproto (bsc#1242709).\n- smb: client: fix potential race in cifs_put_tcon() (git-fixes).\n- smb: client: fix return value of parse_dfs_referrals() (git-fixes).\n- smb: client: get rid of @nlsc param in cifs_tree_connect() (git-fixes).\n- smb: client: get rid of TCP_Server_Info::refpath_lock (git-fixes).\n- smb: client: get rid of kstrdup() in get_ses_refpath() (git-fixes).\n- smb: client: improve purging of cached referrals (git-fixes).\n- smb: client: introduce av_for_each_entry() helper (git-fixes).\n- smb: client: optimize referral walk on failed link targets (git-fixes).\n- smb: client: parse DNS domain name from domain= option (git-fixes).\n- smb: client: parse av pair type 4 in CHALLENGE_MESSAGE (git-fixes).\n- smb: client: provide dns_resolve_{unc,name} helpers (git-fixes).\n- smb: client: refresh referral without acquiring refpath_lock (git-fixes).\n- smb: client: remove unnecessary checks in open_cached_dir() (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop() (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: aspeed: lpc: Fix impossible judgment condition (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soc: qcom: smp2p: Fix fallback to qcom,ipc parse (git-fixes).\n- soc: ti: k3-socinfo: Do not use syscon helper to build regmap (stable-fixes).\n- software node: Correct a OOB check in software_node_get_reference_args() (stable-fixes).\n- soundwire: amd: change the soundwire wake enable/disable sequence (stable-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi-rockchip: Fix register out of bounds access (stable-fixes).\n- spi: bcm63xx-hsspi: fix shared reset (git-fixes).\n- spi: bcm63xx-spi: fix shared reset (git-fixes).\n- spi: sh-msiof: Fix maximum DMA transfer size (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- spi: spi-sun4i: fix early activation (stable-fixes).\n- spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers (git-fixes).\n- spi: tegra210-quad: modify chip select (CS) deactivation (git-fixes).\n- spi: tegra210-quad: remove redundant error handling code (git-fixes).\n- spi: zynqmp-gqspi: Always acknowledge interrupts (stable-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: iio: ad5933: Correct settling cycles encoding per datasheet (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- staging: rtl8723bs: Avoid memset() in aes_cipher() and aes_decipher() (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- struct usci: hide additional member (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (git-fixes).\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp/dccp: allow a connection when sk_max_ack_backlog is zero (git-fixes).\n- tcp/dccp: bypass empty buckets in inet_twsk_purge() (git-fixes).\n- tcp/dccp: complete lockless accesses to sk-\u003esk_max_ack_backlog (git-fixes).\n- tcp: bring back NUMA dispersion in inet_ehash_locks_alloc() (git-fixes).\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- tcp_metrics: optimize tcp_metrics_flush_all() (git-fixes).\n- thermal/drivers/qoriq: Power down TMU on system suspend (stable-fixes).\n- thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer (stable-fixes).\n- thunderbolt: Do not double dequeue a configuration request (stable-fixes).\n- thunderbolt: Fix a logic error in wake on connect (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- timekeeping: Fix bogus clock_was_set() invocation in (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation corner case (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation for non-x86 (git-fixes)\n- timekeeping: Fix cross-timestamp interpolation on counter (git-fixes)\n- trace/trace_event_perf: remove duplicate samples on the first tracepoint event (git-fixes).\n- tracing/eprobe: Fix to release eprobe when failed to add dyn_event (git-fixes).\n- tracing: Add __print_dynamic_array() helper (bsc#1243544).\n- tracing: Add __string_len() example (bsc#1243544).\n- tracing: Fix cmp_entries_dup() to respect sort() comparison rules (git-fixes).\n- tracing: Fix compilation warning on arm32 (bsc#1243551).\n- tracing: Use atomic64_inc_return() in trace_clock_counter() (git-fixes).\n- truct dwc3 hide new member wakeup_pending_funcs (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_debugfs_entry: hide signedness change (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- udp: annotate data-races around up-\u003epending (git-fixes).\n- udp: fix incorrect parameter validation in the udp_lib_getsockopt() function (git-fixes).\n- udp: fix receiving fraglist GSO packets (git-fixes).\n- udp: preserve the connected status if only UDP cmsg (git-fixes).\n- uprobes: Use kzalloc to allocate xol area (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: Flush altsetting 0 endpoints before reinitializating them after reset (git-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with detecting USB 3.2 speed (git-fixes).\n- usb: cdnsp: Fix issue with detecting command completion event (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: gadget: Make gadget_wakeup asynchronous (git-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: quirks: Add NO_LPM quirk for SanDisk Extreme 55AE (stable-fixes).\n- usb: renesas_usbhs: Reorder clock handling and power management in probe (git-fixes).\n- usb: storage: Ignore UAS driver for SanDisk 3.2 Gen2 storage device (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm/tcpci_maxim: Fix bounds check in process_rx() (git-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Only enable supported notifications (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: allow non-partner GET_PDOS for Qualcomm devices (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix Clang -Wsign-conversion warning (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: fix UCSI on buggy Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: limit the UCSI_NO_PARTNER_PDOS even further (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: usbtmc: Fix read_stb function and get_stb ioctl (git-fixes).\n- usb: usbtmc: Fix timeout value in get_stb (git-fixes).\n- usb: xhci: Do not change the status of stalled TDs on failed Stop EP (stable-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- usbnet: asix AX88772: leave the carrier control to phylink (stable-fixes).\n- vgacon: Add check for vc_origin address range in vgacon_scroll() (git-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vmxnet3: correctly report gso type for UDP tunnels (bsc#1244626).\n- vmxnet3: support higher link speeds from vmxnet3 v9 (bsc#1244626).\n- vmxnet3: update MTU after device quiesce (bsc#1244626).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- vt: remove VT_RESIZE and VT_RESIZEX from vt_compat_ioctl() (git-fixes).\n- watchdog: da9052_wdt: respect TWDMIN (stable-fixes).\n- watchdog: exar: Shorten identity name to fit correctly (git-fixes).\n- watchdog: fix watchdog may detect false positive of softlockup (stable-fixes).\n- watchdog: it87_wdt: add PWRGD enable quirk for Qotom QCML04 (git-fixes).\n- watchdog: mediatek: Add support for MT6735 TOPRGU/WDT (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: Fix QMI memory reuse logic (stable-fixes).\n- wifi: ath11k: avoid burning CPU in ath11k_debugfs_fw_stats_request() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: convert timeouts to secs_to_jiffies() (stable-fixes).\n- wifi: ath11k: do not use static variables in ath11k_debugfs_fw_stats_process() (git-fixes).\n- wifi: ath11k: do not wait when there is no vdev started (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath11k: fix ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix rx completion meta data corruption (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix soc_dp_stats debugfs file permission (stable-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath11k: move some firmware stats related functions outside of debugfs (git-fixes).\n- wifi: ath11k: update channel list in worker when wait flag is set (bsc#1243847).\n- wifi: ath11k: validate ath11k_crypto_mode on top of ath11k_core_qmi_firmware_ready (git-fixes).\n- wifi: ath12k: Add MSDU length validation for TKIP MIC error (git-fixes).\n- wifi: ath12k: Avoid napi_sync() before napi_enable() (stable-fixes).\n- wifi: ath12k: Fix WMI tag for EHT rate in peer assoc (git-fixes).\n- wifi: ath12k: Fix end offset bit definition in monitor ring descriptor (stable-fixes).\n- wifi: ath12k: Fix invalid memory access while forming 802.11 header (git-fixes).\n- wifi: ath12k: Fix memory leak during vdev_id mismatch (git-fixes).\n- wifi: ath12k: Fix the QoS control field offset to build QoS header (git-fixes).\n- wifi: ath12k: Improve BSS discovery with hidden SSID in 6 GHz band (stable-fixes).\n- wifi: ath12k: Pass correct values of center freq1 and center freq2 for 160 MHz (stable-fixes).\n- wifi: ath12k: Report proper tx completion status to mac80211 (stable-fixes).\n- wifi: ath12k: fix a possible dead lock caused by ab-\u003ebase_lock (stable-fixes).\n- wifi: ath12k: fix ath12k_hal_tx_cmd_ext_desc_setup() info1 override (stable-fixes).\n- wifi: ath12k: fix cleanup path after mhi init (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix failed to set mhi state error during reboot with hardware grouping (stable-fixes).\n- wifi: ath12k: fix incorrect CE addresses (stable-fixes).\n- wifi: ath12k: fix invalid access to memory (git-fixes).\n- wifi: ath12k: fix link valid field initialization in the monitor Rx (stable-fixes).\n- wifi: ath12k: fix macro definition HAL_RX_MSDU_PKT_LENGTH_GET (stable-fixes).\n- wifi: ath12k: fix node corruption in ar-\u003earvifs list (git-fixes).\n- wifi: ath12k: fix ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: ath9k: return by of_get_mac_address (stable-fixes).\n- wifi: ath9k_htc: Abort software beacon handling if disabled (git-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: carl9170: do not ping device which has failed to load firmware (git-fixes).\n- wifi: iwlfiwi: mvm: Fix the rate reporting (git-fixes).\n- wifi: iwlwifi: Add missing MODULE_FIRMWARE for Qu-c0-jf-b0 (stable-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: add support for Killer on MTL (stable-fixes).\n- wifi: iwlwifi: fix debug actions order (stable-fixes).\n- wifi: iwlwifi: pcie: make sure to lock rxq-\u003eread (stable-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: VLAN traffic in multicast path (stable-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: do not offer a mesh path if forwarding is disabled (stable-fixes).\n- wifi: mac80211: do not unconditionally call drv_mgd_complete_tx() (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: fix beacon interval calculation overflow (git-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mac80211: remove misplaced drv_mgd_complete_tx() call (stable-fixes).\n- wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled (stable-fixes).\n- wifi: mt76: mt76x2: Add support for LiteOn WN4516R,WN4519R (stable-fixes).\n- wifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init() (git-fixes).\n- wifi: mt76: mt7921: add 160 MHz AP for mt7922 device (stable-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: ensure all MCU commands wait for response (git-fixes).\n- wifi: mt76: mt7925: fix host interrupt register initialization (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: mt76: mt7925: prevent multiple scan commands (git-fixes).\n- wifi: mt76: mt7925: refine the sniffer commnad (git-fixes).\n- wifi: mt76: mt7996: drop fragments with multicast or broadcast RA (stable-fixes).\n- wifi: mt76: mt7996: fix RX buffer size of MCU event (git-fixes).\n- wifi: mt76: mt7996: revise TXS size (stable-fixes).\n- wifi: mt76: mt7996: set EHT max ampdu length capability (git-fixes).\n- wifi: mt76: only mark tx-status-failed frames as ACKed on mt76x0/2 (stable-fixes).\n- wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723 (git-fixes).\n- wifi: rtw88: Do not use static local variable in rtw8822b_set_tx_power_index_by_rate (stable-fixes).\n- wifi: rtw88: Fix __rtw_download_firmware() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix download_firmware_validate() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_desc_to_mcsrate() to handle MCS16-31 (stable-fixes).\n- wifi: rtw88: Fix rtw_init_ht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: Fix rtw_init_vht_cap() for RTL8814AU (stable-fixes).\n- wifi: rtw88: do not ignore hardware read error during DPK (git-fixes).\n- wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds (git-fixes).\n- wifi: rtw88: sdio: call rtw_sdio_indicate_tx_status unconditionally (git-fixes).\n- wifi: rtw88: sdio: map mgmt frames to queue TX_DESC_QSEL_MGMT (git-fixes).\n- wifi: rtw88: usb: Reduce control message timeout to 500 ms (git-fixes).\n- wifi: rtw89: add wiphy_lock() to work that isn't held wiphy_lock() yet (stable-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: rtw89: fw: propagate error code from rtw89_h2c_tx() (stable-fixes).\n- wifi: rtw89: leave idle mode when setting WEP encryption for AP mode (stable-fixes).\n- wifi: rtw89: pci: enlarge retry times of RX tag to 1000 (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/idle: Remove MFENCEs for X86_BUG_CLFLUSH_MONITOR in mwait_idle_with_hints() and prefer_mwait_c1_over_halt() (git-fixes).\n- x86/kaslr: Reduce KASLR entropy on most x86 systems (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/microcode/AMD: Add get_patch_level() (git-fixes).\n- x86/microcode/AMD: Do not return error when microcode update is not necessary (git-fixes).\n- x86/microcode/AMD: Get rid of the _load_microcode_amd() forward declaration (git-fixes).\n- x86/microcode/AMD: Have __apply_microcode_amd() return bool (git-fixes).\n- x86/microcode/AMD: Make __verify_patch_size() return bool (git-fixes).\n- x86/microcode/AMD: Merge early_apply_microcode() into its single callsite (git-fixes).\n- x86/microcode/AMD: Remove ugly linebreak in __verify_patch_section() signature (git-fixes).\n- x86/microcode/AMD: Return bool from find_blobs_in_containers() (git-fixes).\n- x86/microcode: Consolidate the loader enablement checking (git-fixes).\n- x86/mm/init: Handle the special case of device private pages in add_pages(), to not increase max_pfn and trigger dma_addressing_limited() bounce buffers (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86/xen: fix balloon target initialization for PVH dom0 (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xen/arm: call uaccess_ttbr0_enable for dm_op hypercall (git-fixes)\n- xen/x86: fix initial memory balloon target (git-fixes).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n- xsk: always clear DMA mapping information when unmapping the pool (git-fixes).\n","status":"published","published":"2025-08-20T07:24:58Z","modified":"2026-02-04T03:11:07.580308Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:02969-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21854: selftest/bpf: Add vsock test for sockmap rejecting unconnected (bsc#1239470).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-22090: mm: (un)track_pfn_copy() fix + doc improvements (bsc#1241537).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- acpi: LPSS: Remove AudioDSP related ID (git-fixes).\n- acpi: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- acpi: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- acpica: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- alsa: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- alsa: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- alsa: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- alsa: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- alsa: hda/tegra: Add Tegra264 support (stable-fixes).\n- alsa: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- alsa: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- alsa: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- alsa: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- alsa: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- alsa: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- asoc: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- asoc: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- asoc: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- asoc: amd: yc: update quirk data for HP Victus (stable-fixes).\n- asoc: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- asoc: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- asoc: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- asoc: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- asoc: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- asoc: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- asoc: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- asoc: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hid: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- hid: core: do not bypass hid_hw_raw_request (stable-fixes).\n- hid: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- hid: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- hid: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- hid: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ib/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- input: iqs7222 - explicitly define number of external channels (git-fixes).\n- input: xpad - adjust error handling for disconnect (git-fixes).\n- input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-obs-qa: Do not depend on srchash when qemu emulation is used In this case the dependency is never fulfilled Fixes: 485ae1da2b88 ('kernel-obs-qa: Use srchash for dependency as well')\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- logitech C-270 even more broken (stable-fixes).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfs: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- nfs: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- nfs: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- nfs: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- nfsd: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsv4.2: another fix for listxattr (git-fixes).\n- nfsv4.2: fix listxattr to return selinux security label (git-fixes).\n- nfsv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- nfsv4: Always set NLINK even if the server does not support it (git-fixes).\n- nfsv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- pci/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- pci: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- pci: endpoint: Fix configfs group list head handling (git-fixes).\n- pci: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- pci: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- pci: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- pci: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- pci: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- pm / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- rdma/core: Rate limit GID cache warning messages (git-fixes)\n- rdma/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- rdma/hns: Drop GFP_NOWARN (git-fixes)\n- rdma/hns: Fix -Wframe-larger-than issue (git-fixes)\n- rdma/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- rdma/hns: Fix accessing uninitialized resources (git-fixes)\n- rdma/hns: Fix double destruction of rsv_qp (git-fixes)\n- rdma/hns: Get message length of ack_req from FW (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- rdma/mlx5: Fix CC counters query for MPV (git-fixes)\n- rdma/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- rdma/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- rdma/mlx5: Fix vport loopback for MPV device (git-fixes)\n- rdma/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- rdma/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- rdma/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- rdma/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879) Put the same workaround to avoid file truncation of vmlinux and co in kernel-default-base package, too.\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- smb3: send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- smb: client: fix parsing of device numbers (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- sunrpc: fix handling of server side tls alerts (git-fixes).\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- usb: serial: option: add Foxconn T99W640 (stable-fixes).\n- usb: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-25T06:22:23Z","modified":"2026-02-04T02:45:57.384555Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:02996-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (1230216).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21854: selftest/bpf: Add vsock test for sockmap rejecting unconnected (bsc#1239470).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-22090: mm: (un)track_pfn_copy() fix + doc improvements (bsc#1241537).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- Fix dma_unmap_sg() nents value (git-fixes)\n- Logitech C-270 even more broken (stable-fixes).\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- acpi: LPSS: Remove AudioDSP related ID (git-fixes).\n- acpi: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- acpi: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- acpica: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- alsa: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- alsa: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- alsa: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- alsa: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- alsa: hda/tegra: Add Tegra264 support (stable-fixes).\n- alsa: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- alsa: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- alsa: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- alsa: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- alsa: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- alsa: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- asoc: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- asoc: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- asoc: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- asoc: amd: yc: update quirk data for HP Victus (stable-fixes).\n- asoc: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- asoc: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- asoc: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- asoc: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- asoc: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- asoc: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- asoc: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- asoc: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- documentation: ACPI: Fix parent device references (git-fixes).\n- documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hid: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- hid: core: do not bypass hid_hw_raw_request (stable-fixes).\n- hid: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- hid: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- hid: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- hid: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ib/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- input: iqs7222 - explicitly define number of external channels (git-fixes).\n- input: xpad - adjust error handling for disconnect (git-fixes).\n- input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfs: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- nfs: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- nfs: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- nfs: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- nfsd: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsv4.2: another fix for listxattr (git-fixes).\n- nfsv4.2: fix listxattr to return selinux security label (git-fixes).\n- nfsv4/pnfs: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- nfsv4: Always set NLINK even if the server does not support it (git-fixes).\n- nfsv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- pci/msi: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- pci: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- pci: endpoint: Fix configfs group list head handling (git-fixes).\n- pci: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- pci: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- pci: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- pci: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- pci: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- pm / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- pnfs/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- rdma/core: Rate limit GID cache warning messages (git-fixes)\n- rdma/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- rdma/hns: Drop GFP_NOWARN (git-fixes)\n- rdma/hns: Fix -Wframe-larger-than issue (git-fixes)\n- rdma/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- rdma/hns: Fix accessing uninitialized resources (git-fixes)\n- rdma/hns: Fix double destruction of rsv_qp (git-fixes)\n- rdma/hns: Get message length of ack_req from FW (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- rdma/mlx5: Fix CC counters query for MPV (git-fixes)\n- rdma/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- rdma/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- rdma/mlx5: Fix vport loopback for MPV device (git-fixes)\n- rdma/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- rdma/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- rdma/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- rdma/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- smb3: send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- usb: serial: option: add Foxconn T99W640 (stable-fixes).\n- usb: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-27T12:02:43Z","modified":"2026-03-23T04:46:59.637219Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:02997-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: enabled CONFIG_X86_INTEL_TSX_MODE_AUTO (bsc#1139073, bsc#1246695)\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-39298:mm/memory-failure: fix handling of dissolved but not taken off from buddy pages (bsc#1227082).\n- CVE-2024-42134: virtio-pci: Check if is_avq is NULL (bsc#1228664).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21854: selftest/bpf: Add vsock test for sockmap rejecting unconnected (bsc#1239470).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-22090: mm: (un)track_pfn_copy() fix + doc improvements (bsc#1241537).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38047: x86/fred: Fix system hang during S4 resume with FRED enabled (bsc#1245084).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38256: io_uring/rsrc: fix folio unpinning (bsc#1246188).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: kABI workaround for bpf: Do not include stack ptr register in precision backtracking bookkeeping (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38453: kABI: io_uring: msg_ring ensure io_kiocb freeing is deferred (bsc#1247234).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38475: smc: Fix various oops due to inet_sock type confusion (bsc#1247308).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- accel/ivpu: Remove copy engine support (stable-fixes).\n- acpi: LPSS: Remove AudioDSP related ID (git-fixes).\n- acpi: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- acpi: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- acpica: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- alsa: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- alsa: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- alsa: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- alsa: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- alsa: hda/realtek: Fix mute LED mask on HP OMEN 16 laptop (git-fixes).\n- alsa: hda/tegra: Add Tegra264 support (stable-fixes).\n- alsa: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- alsa: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- alsa: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- alsa: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- alsa: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- alsa: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- alsa: scarlett2: Add retry on -EPROTO from scarlett2_usb_tx() (git-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- asoc: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- asoc: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- asoc: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- asoc: amd: yc: update quirk data for HP Victus (stable-fixes).\n- asoc: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- asoc: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- asoc: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- asoc: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- asoc: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- asoc: fsl_sai: Force a software reset when starting in consumer mode (git-fixes).\n- asoc: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- asoc: mediatek: use reserved memory or enable buffer pre-allocation (git-fixes).\n- asoc: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- asoc: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- bluetooth: HCI: Set extended advertising data synchronously (git-fixes).\n- bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type (git-fixes).\n- bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_core: add missing braces when using macro parameters (git-fixes).\n- bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- bnxt_en: Fix double invocation of bnxt_ulp_stop()/bnxt_ulp_start() (git-fixes).\n- bonding: Correctly support GSO ESP offload (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: hkdf - skip TVs with unapproved salt lengths in FIPS mode (bsc#1241200 bsc#1246134).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dax: add a sysfs knob to control memmap_on_memory behavior (bsc#1235515,jsc#PED-12731).\n- dax: add a sysfs knob to control memmap_on_memory behavior (bsc#1235515,jsc#PED-12731).\n- devlink: Add support for u64 parameters (jsc#PED-12745).\n- devlink: Add support for u64 parameters (jsc#PED-12745).\n- devlink: avoid param type value translations (jsc#PED-12745).\n- devlink: avoid param type value translations (jsc#PED-12745).\n- devlink: define enum for attr types of dynamic attributes  (jsc#PED-12745).\n- devlink: define enum for attr types of dynamic attributes (jsc#PED-12745).\n- devlink: introduce devlink_nl_put_u64() (jsc#PED-12745).\n- devlink: introduce devlink_nl_put_u64() (jsc#PED-12745).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- documentatiion/ABI: add ABI documentation for sys-bus-dax (bsc#1235515,jsc#PED-12731).\n- documentation/ABI: add ABI documentation for sys-bus-dax (bsc#1235515,jsc#PED-12731).\n- documentation: ACPI: Fix parent device references (git-fixes).\n- documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- dpll: Add basic Microchip ZL3073x support (jsc#PED-12745).\n- dpll: Add basic Microchip ZL3073x support (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set frequency on pins  (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set frequency on pins (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set priority on input pins  (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set priority on input pins (jsc#PED-12745).\n- dpll: zl3073x: Fetch invariants during probe (jsc#PED-12745).\n- dpll: zl3073x: Fetch invariants during probe (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin selection in manual mode  (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin selection in manual mode (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin state setting in automatic  mode (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin state setting in automatic mode (jsc#PED-12745).\n- dpll: zl3073x: Read DPLL types and pin properties from system  firmware (jsc#PED-12745).\n- dpll: zl3073x: Read DPLL types and pin properties from system firmware (jsc#PED-12745).\n- dpll: zl3073x: Register DPLL devices and pins (jsc#PED-12745).\n- dpll: zl3073x: Register DPLL devices and pins (jsc#PED-12745).\n- drm/amd/display: Check dce_hwseq before dereferencing it (stable-fixes).\n- drm/amd/display: Correct non-OLED pre_T11_delay (stable-fixes).\n- drm/amd/display: Disable CRTC degamma LUT for DCN401 (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/display: Fix RMCM programming seq errors (stable-fixes).\n- drm/amd/display: Fix mpv playback corruption on weston (stable-fixes).\n- drm/amd/display: Free memory allocation (stable-fixes).\n- drm/amd/display: fix initial backlight brightness calculation (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/discovery: use specific ip_discovery.bin for legacy asics (stable-fixes).\n- drm/amdgpu/gfx10: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu/gfx9.4.3: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx9: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/ip_discovery: add missing ip_discovery fw (stable-fixes).\n- drm/amdgpu: Add kicker device detection (stable-fixes).\n- drm/amdgpu: Fix SDMA UTC_L1 handling during start/stop sequences (stable-fixes).\n- drm/amdgpu: Increase reset counter only on success (stable-fixes).\n- drm/amdgpu: Initialize data to NULL in imu_v12_0_program_rlc_ram() (git-fixes).\n- drm/amdgpu: Remove nbiov7.9 replay count reporting (git-fixes).\n- drm/amdgpu: Reset the clear flag in buddy during resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdgpu: seq64 memory unmap uses uninterruptible lock (stable-fixes).\n- drm/amdkfd: Do not call mmput from MMU notifier callback (git-fixes).\n- drm/amdkfd: Fix instruction hazard in gfx12 trap handler (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/amdkfd: remove gfx 12 trap handler page size cap (stable-fixes).\n- drm/bridge: aux-hpd-bridge: fix assignment of the of_node (git-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/connector: hdmi: Evaluate limited range after computing format (git-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/display: Fix dma_fence_wait_timeout() return value handling (git-fixes).\n- drm/i915/dsi: Fix off by one in BXT_MIPI_TRANS_VTOTAL (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/imagination: Fix kernel crash when hard resetting the GPU (git-fixes).\n- drm/mediatek: Add wait_event_timeout when disabling plane (git-fixes).\n- drm/mediatek: only announce AFBC if really supported (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/nouveau: check ioctl command codes better (git-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/panthor: Add missing explicit padding in drm_panthor_gpu_info (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/v3d: Disable interrupts before resetting the GPU (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- drm/xe/bmg: fix compressed VRAM handling (git-fixes).\n- drm/xe/guc: Dead CT helper (stable-fixes).\n- drm/xe/guc: Explicitly exit CT safe mode on unwind (git-fixes).\n- drm/xe/guc_submit: add back fix (git-fixes).\n- drm/xe/mocs: Initialize MOCS index early (stable-fixes).\n- drm/xe/pf: Clear all LMTT pages on alloc (git-fixes).\n- drm/xe/pf: Move VFs reprovisioning to worker (stable-fixes).\n- drm/xe/pf: Prepare to stop SR-IOV support prior GT reset (git-fixes).\n- drm/xe/pf: Sanitize VF scratch registers on FLR (stable-fixes).\n- drm/xe/pm: Correct comment of xe_pm_set_vram_threshold() (git-fixes).\n- drm/xe/uapi: Correct sync type definition in comments (git-fixes).\n- drm/xe/vf: Disable CSC support on VF (git-fixes).\n- drm/xe: Allocate PF queue size on pow2 boundary (git-fixes).\n- drm/xe: Allow bo mapping on multiple ggtts (stable-fixes).\n- drm/xe: Fix DSB buffer coherency (stable-fixes).\n- drm/xe: Fix build without debugfs (git-fixes).\n- drm/xe: Fix early wedge on GuC load failure (git-fixes).\n- drm/xe: Fix taking invalid lock on wedge (stable-fixes).\n- drm/xe: Move DSB l2 flush to a more sensible place (git-fixes).\n- drm/xe: Replace double space with single space after comma (stable-fixes).\n- drm/xe: add interface to request physical alignment for buffer objects (stable-fixes).\n- drm/xe: move DPT l2 flush to a more sensible place (git-fixes).\n- dt-bindings: dpll: Add DPLL device and pin (jsc#PED-12745).\n- dt-bindings: dpll: Add DPLL device and pin (jsc#PED-12745).\n- dt-bindings: dpll: Add support for Microchip Azurite chip family  (jsc#PED-12745).\n- dt-bindings: dpll: Add support for Microchip Azurite chip family (jsc#PED-12745).\n- e1000: Move cancel_work_sync to avoid deadlock (git-fixes).\n- enable SMC_LO (a.k.a SMC-D) (jsc#PED-13248).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fix dma_unmap_sg() nents value (git-fixes)\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hid: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- hid: core: do not bypass hid_hw_raw_request (stable-fixes).\n- hid: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- hid: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- hid: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- hid: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ib/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- ice, irdma: fix an off by one in error handling code (bsc#1247712).\n- ice, irdma: move interrupts code to irdma (bsc#1247712).\n- ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712).\n- ice: count combined queues using Rx/Tx count (bsc#1247712).\n- ice: devlink PF MSI-X max and min parameter (bsc#1247712).\n- ice: enable_rdma devlink param (bsc#1247712).\n- ice: fix eswitch code memory leak in reset scenario (git-fixes).\n- ice: get rid of num_lan_msix field (bsc#1247712).\n- ice: init flow director before RDMA (bsc#1247712).\n- ice: remove splitting MSI-X between features (bsc#1247712).\n- ice: simplify VF MSI-X managing (bsc#1247712).\n- ice: treat dyn_allowed only as suggestion (bsc#1247712).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- input: iqs7222 - explicitly define number of external channels (git-fixes).\n- input: xpad - adjust error handling for disconnect (git-fixes).\n- input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- io_uring/timeout: fix multishot updates (bsc#1247021).\n- io_uring: fix potential page leak in io_sqe_buffer_register() (git-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/tegra241-cmdqv: Read SMMU IDR1.CMDQS instead of hardcoding (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- irdma: free iwdev-\u003erf after removing MSI-X (bsc#1247712).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI fix after KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- kABI fixes for struct memory_block changes  (bsc#1235515,jsc#PED-12731).\n- kABI fixes for struct memory_block changes (bsc#1235515,jsc#PED-12731).\n- kABI workaround for fw_attributes_class_get() (stable-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kabi/severities: ignore two unused/dropped symbols from MEI\n- kabi: Hide adding of u64 to devlink_param_type (jsc#PED-12745).\n- kabi: Hide adding of u64 to devlink_param_type (jsc#PED-12745).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-obs-qa: Do not depend on srchash when qemu emulation is used In this case the dependency is never fulfilled Fixes: 485ae1da2b88 ('kernel-obs-qa: Use srchash for dependency as well')\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- kvm: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- logitech C-270 even more broken (stable-fixes).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ipu6: isys: Use correct pads for xlate_streams() (git-fixes).\n- media: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: verisilicon: Fix AV1 decoder clock frequency (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- mei: vsc: Destroy mutex after freeing the IRQ (git-fixes).\n- mei: vsc: Do not re-init VSC from mei_vsc_hw_reset() on stop (git-fixes).\n- mei: vsc: Drop unused vsc_tp_request_irq() and vsc_tp_free_irq() (stable-fixes).\n- mei: vsc: Event notifier fixes (git-fixes).\n- mei: vsc: Fix 'BUG: Invalid wait context' lockdep error (git-fixes).\n- mei: vsc: Run event callback from a workqueue (git-fixes).\n- mei: vsc: Unset the event callback on remove and probe errors (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mm/memory_hotplug: allow architecture to override memmap on  memory support check (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow architecture to override memmap on memory support check (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow memmap on memory hotplug request to  fallback (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow memmap on memory hotplug request to fallback (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: embed vmem_altmap details in memory block  (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: embed vmem_altmap details in memory block (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: export mhp_supports_memmap_on_memory() (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: export mhp_supports_memmap_on_memory() (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval (git-fixes).\n- mm/memory_hotplug: replace an open-coded kmemdup() in (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: replace an open-coded kmemdup() in (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE  kconfig (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: split memmap_on_memory requests across memblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: split memmap_on_memory requests across memblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: support memmap_on_memory when memmap is  not aligned to pageblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: support memmap_on_memory when memmap is not aligned to pageblocks (bsc#1235515,jsc#PED-12731).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/mlx5: HWS, fix missing ip_version handling in definer (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net/smc: Fix lookup of netdev by using ib_device_get_netdev() (git-fixes bsc#1246217).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netlink: fix policy dump for int with validation callback  (jsc#PED-12745).\n- netlink: fix policy dump for int with validation callback (jsc#PED-12745).\n- netlink: specs: devlink: replace underscores with dashes in  names (jsc#PED-12745).\n- netlink: specs: devlink: replace underscores with dashes in names (jsc#PED-12745).\n- netlink: specs: nfsd: replace underscores with dashes in names (git-fixes).\n- netlink: specs: tc: replace underscores with dashes in names (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfs: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- nfs: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- nfs: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- nfs: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- nfsd: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsv4.2: another fix for listxattr (git-fixes).\n- nfsv4.2: fix listxattr to return selinux security label (git-fixes).\n- nfsv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- nfsv4: Always set NLINK even if the server does not support it (git-fixes).\n- nfsv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- pci/msi: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- pci: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- pci: endpoint: Fix configfs group list head handling (git-fixes).\n- pci: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- pci: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- pci: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- pci: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- pci: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: Fix initialization order for firmware_attributes_class (git-fixes).\n- platform/x86: dell-sysman: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: firmware_attributes_class: Move include linux/device/class.h (stable-fixes).\n- platform/x86: firmware_attributes_class: Simplify API (stable-fixes).\n- platform/x86: hp-bioscfg: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: hp-bioscfg: Fix class device unregistration (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: make fw_attr_class constant (stable-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- pm / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO add (bsc#1243042 ltc#212167).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- pwm: rockchip: Round period/duty down on apply, up on get (git-fixes).\n- rdma/core: Rate limit GID cache warning messages (git-fixes)\n- rdma/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- rdma/hns: Drop GFP_NOWARN (git-fixes)\n- rdma/hns: Fix -Wframe-larger-than issue (git-fixes)\n- rdma/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- rdma/hns: Fix accessing uninitialized resources (git-fixes)\n- rdma/hns: Fix double destruction of rsv_qp (git-fixes)\n- rdma/hns: Get message length of ack_req from FW (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- rdma/mlx5: Fix CC counters query for MPV (git-fixes)\n- rdma/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- rdma/mlx5: Fix UMR modifying of mkey page size (git-fixes)\n- rdma/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- rdma/mlx5: Fix vport loopback for MPV device (git-fixes)\n- rdma/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- rdma/mlx5: reduce stack usage in mlx5_ib_ufile_hw_cleanup (git-fixes)\n- rdma/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- rdma/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- rdma/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- re-enable qmi_wwan for arm64 (bsc#1246113)\n- reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: core: fix NULL dereference on unbind due to stale coupling data (stable-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- revert 'drm/nouveau: check ioctl command codes better' (git-fixes).\n- revert 'drm/xe/xe2: Enable Indirect Ring State support for Xe2' (git-fixes).\n- revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879) Put the same workaround to avoid file truncation of vmlinux and co in kernel-default-base package, too.\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1246644).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (git-fixes).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (git-fixes).\n- scsi: fnic: Set appropriate logging level for log message (bsc#1246644).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- smb3: send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- sprintf.h requires stdarg.h (git-fixes).\n- sprintf.h: mask additional include (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- staging: vchiq_arm: Make vchiq_shutdown never fail (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- supported.conf: Mark ZL3073X modules supported\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thermal: trip: Use READ_ONCE() for lockless access to trip properties (git-fixes).\n- thermal: trip: Use common set of trip type names (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- update config files (bsc#1243678)\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: Abort suspend on soft disconnect failure (git-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- usb: serial: option: add Foxconn T99W640 (stable-fixes).\n- usb: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: cfg80211/mac80211: correctly parse S1G beacon optional elements (git-fixes).\n- wifi: cfg80211: fix S1G beacon head validation in nl80211 (git-fixes).\n- wifi: cfg80211: remove scan request n_channels counted_by (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Create separate links for VLAN interfaces (stable-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: Write cnt before copying in ieee80211_copy_rnr_beacon() (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: finish link init before RCU publish (git-fixes).\n- wifi: mac80211: fix non-transmitted BSSID profile search (git-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: nl80211: Set num_sub_specs before looping through sub_specs (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rt2x00: fix remove callback type mismatch (git-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/CPU/AMD: Add more models to X86_FEATURE_ZEN5 (bsc#1246449).\n- x86/CPU/AMD: Improve the erratum 1386 workaround (git-fixes).\n- x86/CPU/AMD: Terminate the erratum_1386_microcode array (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/cpu: Avoid running off the end of an AMD erratum table (git-fixes).\n- x86/cpu: Expose only stepping min/max interface (git-fixes).\n- x86/cpu: Introduce new microcode matching helper (git-fixes).\n- x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id' (git-fixes).\n- x86/cpu: Replace PEBS use of 'x86_cpu_desc' use with 'x86_cpu_id' (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/mtrr: Rename mtrr_overwrite_state() to guest_force_mtrr_state() (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-27T12:04:21Z","modified":"2026-03-23T04:48:43.338132Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:03011-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: enabled CONFIG_X86_INTEL_TSX_MODE_AUTO (bsc#1139073, bsc#1246695).\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-39298:mm/memory-failure: fix handling of dissolved but not taken off from buddy pages (bsc#1227082).  \n- CVE-2024-42134: virtio-pci: Check if is_avq is NULL (bsc#1228664 bsc#1247831).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-49861: net: clear the dst when changing skb protocol (bsc#1245954).\n- CVE-2024-49996: cifs: Fix buffer overflow when parsing NFS reparse points (bsc#1232089).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21854: selftest/bpf: Add vsock test for sockmap rejecting unconnected (bsc#1239470).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-22090: mm: (un)track_pfn_copy() fix + doc improvements (bsc#1241537).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38047: x86/fred: Fix system hang during S4 resume with FRED enabled (bsc#1245084).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38256: io_uring/rsrc: fix folio unpinning (bsc#1246188).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38453: kABI: io_uring: msg_ring ensure io_kiocb freeing is deferred (bsc#1247234).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38475: smc: Fix various oops due to inet_sock type confusion (bsc#1247308).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/realtek: Fix mute LED mask on HP OMEN 16 laptop (git-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ALSA: scarlett2: Add retry on -EPROTO from scarlett2_usb_tx() (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_sai: Force a software reset when starting in consumer mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: mediatek: use reserved memory or enable buffer pre-allocation (git-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: HCI: Set extended advertising data synchronously (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btintel: Check if controller is ISO capable on btintel_classify_pkt_type (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_core: add missing braces when using macro parameters (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentatiion/ABI: add ABI documentation for sys-bus-dax (bsc#1235515,jsc#PED-12731).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Enable SMC_LO (a.k.a SMC-D) (jsc#PED-13248).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- PCI: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix UMR modifying of mkey page size (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/mlx5: reduce stack usage in mlx5_ib_ufile_hw_cleanup (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- Re-enable qmi_wwan for arm64 (bsc#1246113)\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'drm/nouveau: check ioctl command codes better' (git-fixes).\n- Revert 'drm/xe/xe2: Enable Indirect Ring State support for Xe2' (git-fixes).\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- Update config files. config/x86_64/default config/arm64/default CONFIG_INTEGRITY_MACHINE_KEYRING=y +CONFIG_INTEGRITY_CA_MACHINE_KEYRING=y +CONFIG_INTEGRITY_CA_MACHINE_KEYRING_MAX=y +CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=y (bsc#1243678)\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- accel/ivpu: Remove copy engine support (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bnxt_en: Fix double invocation of bnxt_ulp_stop()/bnxt_ulp_start() (git-fixes).\n- bonding: Correctly support GSO ESP offload (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: hkdf - skip TVs with unapproved salt lengths in FIPS mode (bsc#1241200 bsc#1246134).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dax: add a sysfs knob to control memmap_on_memory behavior (bsc#1235515,jsc#PED-12731).\n- devlink: Add support for u64 parameters (jsc#PED-12745).\n- devlink: avoid param type value translations (jsc#PED-12745).\n- devlink: define enum for attr types of dynamic attributes (jsc#PED-12745).\n- devlink: introduce devlink_nl_put_u64() (jsc#PED-12745).\n- disable ZL3073X\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- dpll: Add basic Microchip ZL3073x support (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set frequency on pins (jsc#PED-12745).\n- dpll: zl3073x: Add support to get/set priority on input pins (jsc#PED-12745).\n- dpll: zl3073x: Fetch invariants during probe (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin selection in manual mode (jsc#PED-12745).\n- dpll: zl3073x: Implement input pin state setting in automatic mode (jsc#PED-12745).\n- dpll: zl3073x: Read DPLL types and pin properties from system firmware (jsc#PED-12745).\n- dpll: zl3073x: Register DPLL devices and pins (jsc#PED-12745).\n- drm/amd/display: Check dce_hwseq before dereferencing it (stable-fixes).\n- drm/amd/display: Correct non-OLED pre_T11_delay (stable-fixes).\n- drm/amd/display: Disable CRTC degamma LUT for DCN401 (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/display: Fix RMCM programming seq errors (stable-fixes).\n- drm/amd/display: Fix mpv playback corruption on weston (stable-fixes).\n- drm/amd/display: Free memory allocation (stable-fixes).\n- drm/amd/display: fix initial backlight brightness calculation (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/discovery: use specific ip_discovery.bin for legacy asics (stable-fixes).\n- drm/amdgpu/gfx10: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu/gfx9.4.3: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/gfx9: fix kiq locking in KCQ reset (git-fixes).\n- drm/amdgpu/ip_discovery: add missing ip_discovery fw (stable-fixes).\n- drm/amdgpu: Add kicker device detection (stable-fixes).\n- drm/amdgpu: Fix SDMA UTC_L1 handling during start/stop sequences (stable-fixes).\n- drm/amdgpu: Increase reset counter only on success (stable-fixes).\n- drm/amdgpu: Initialize data to NULL in imu_v12_0_program_rlc_ram() (git-fixes).\n- drm/amdgpu: Remove nbiov7.9 replay count reporting (git-fixes).\n- drm/amdgpu: Reset the clear flag in buddy during resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdgpu: seq64 memory unmap uses uninterruptible lock (stable-fixes).\n- drm/amdkfd: Do not call mmput from MMU notifier callback (git-fixes).\n- drm/amdkfd: Fix instruction hazard in gfx12 trap handler (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/amdkfd: remove gfx 12 trap handler page size cap (stable-fixes).\n- drm/bridge: aux-hpd-bridge: fix assignment of the of_node (git-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/connector: hdmi: Evaluate limited range after computing format (git-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/display: Fix dma_fence_wait_timeout() return value handling (git-fixes).\n- drm/i915/dsi: Fix off by one in BXT_MIPI_TRANS_VTOTAL (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/imagination: Fix kernel crash when hard resetting the GPU (git-fixes).\n- drm/mediatek: Add wait_event_timeout when disabling plane (git-fixes).\n- drm/mediatek: only announce AFBC if really supported (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/nouveau: check ioctl command codes better (git-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/panthor: Add missing explicit padding in drm_panthor_gpu_info (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/v3d: Disable interrupts before resetting the GPU (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- drm/xe/bmg: fix compressed VRAM handling (git-fixes).\n- drm/xe/guc: Dead CT helper (stable-fixes).\n- drm/xe/guc: Explicitly exit CT safe mode on unwind (git-fixes).\n- drm/xe/guc_submit: add back fix (git-fixes).\n- drm/xe/mocs: Initialize MOCS index early (stable-fixes).\n- drm/xe/pf: Clear all LMTT pages on alloc (git-fixes).\n- drm/xe/pf: Move VFs reprovisioning to worker (stable-fixes).\n- drm/xe/pf: Prepare to stop SR-IOV support prior GT reset (git-fixes).\n- drm/xe/pf: Sanitize VF scratch registers on FLR (stable-fixes).\n- drm/xe/pm: Correct comment of xe_pm_set_vram_threshold() (git-fixes).\n- drm/xe/uapi: Correct sync type definition in comments (git-fixes).\n- drm/xe/vf: Disable CSC support on VF (git-fixes).\n- drm/xe: Allocate PF queue size on pow2 boundary (git-fixes).\n- drm/xe: Allow bo mapping on multiple ggtts (stable-fixes).\n- drm/xe: Fix DSB buffer coherency (stable-fixes).\n- drm/xe: Fix build without debugfs (git-fixes).\n- drm/xe: Fix early wedge on GuC load failure (git-fixes).\n- drm/xe: Fix taking invalid lock on wedge (stable-fixes).\n- drm/xe: Move DSB l2 flush to a more sensible place (git-fixes).\n- drm/xe: Replace double space with single space after comma (stable-fixes).\n- drm/xe: add interface to request physical alignment for buffer objects (stable-fixes).\n- drm/xe: move DPT l2 flush to a more sensible place (git-fixes).\n- dt-bindings: dpll: Add DPLL device and pin (jsc#PED-12745).\n- dt-bindings: dpll: Add support for Microchip Azurite chip family (jsc#PED-12745).\n- e1000: Move cancel_work_sync to avoid deadlock (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ice, irdma: fix an off by one in error handling code (bsc#1247712).\n- ice, irdma: move interrupts code to irdma (bsc#1247712).\n- ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712).\n- ice: count combined queues using Rx/Tx count (bsc#1247712).\n- ice: devlink PF MSI-X max and min parameter (bsc#1247712).\n- ice: enable_rdma devlink param (bsc#1247712).\n- ice: fix eswitch code memory leak in reset scenario (git-fixes).\n- ice: get rid of num_lan_msix field (bsc#1247712).\n- ice: init flow director before RDMA (bsc#1247712).\n- ice: remove splitting MSI-X between features (bsc#1247712).\n- ice: simplify VF MSI-X managing (bsc#1247712).\n- ice: treat dyn_allowed only as suggestion (bsc#1247712).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- io_uring/timeout: fix multishot updates (bsc#1247021).\n- io_uring: fix potential page leak in io_sqe_buffer_register() (git-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/tegra241-cmdqv: Read SMMU IDR1.CMDQS instead of hardcoding (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- irdma: free iwdev-\u003erf after removing MSI-X (bsc#1247712).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI fix after KVM: SVM: Fix SNP AP destroy race with VMRUN (git-fixes).\n- kABI fixes for struct memory_block changes (bsc#1235515,jsc#PED-12731).\n- kABI workaround for fw_attributes_class_get() (stable-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kabi/severities: ignore two unused/dropped symbols from MEI\n- kabi: Hide adding of u64 to devlink_param_type (jsc#PED-12745).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-obs-qa: Do not depend on srchash when qemu emulation is used In this case the dependency is never fulfilled\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ipu6: isys: Use correct pads for xlate_streams() (git-fixes).\n- media: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: verisilicon: Fix AV1 decoder clock frequency (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- mei: vsc: Destroy mutex after freeing the IRQ (git-fixes).\n- mei: vsc: Do not re-init VSC from mei_vsc_hw_reset() on stop (git-fixes).\n- mei: vsc: Drop unused vsc_tp_request_irq() and vsc_tp_free_irq() (stable-fixes).\n- mei: vsc: Event notifier fixes (git-fixes).\n- mei: vsc: Fix 'BUG: Invalid wait context' lockdep error (git-fixes).\n- mei: vsc: Run event callback from a workqueue (git-fixes).\n- mei: vsc: Unset the event callback on remove and probe errors (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mm/memory_hotplug: allow architecture to override memmap on memory support check (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: allow memmap on memory hotplug request to fallback (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: embed vmem_altmap details in memory block (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: export mhp_supports_memmap_on_memory() (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: fix memmap_on_memory sysfs value retrieval (git-fixes).\n- mm/memory_hotplug: replace an open-coded kmemdup() in (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: split memmap_on_memory requests across memblocks (bsc#1235515,jsc#PED-12731).\n- mm/memory_hotplug: support memmap_on_memory when memmap is not aligned to pageblocks (bsc#1235515,jsc#PED-12731).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/mlx5: HWS, fix missing ip_version handling in definer (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net/smc: Fix lookup of netdev by using ib_device_get_netdev() (git-fixes bsc#1246217).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netlink: fix policy dump for int with validation callback (jsc#PED-12745).\n- netlink: specs: devlink: replace underscores with dashes in names (jsc#PED-12745).\n- netlink: specs: nfsd: replace underscores with dashes in names (git-fixes).\n- netlink: specs: tc: replace underscores with dashes in names (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: Fix initialization order for firmware_attributes_class (git-fixes).\n- platform/x86: dell-sysman: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: firmware_attributes_class: Move include linux/device/class.h (stable-fixes).\n- platform/x86: firmware_attributes_class: Simplify API (stable-fixes).\n- platform/x86: hp-bioscfg: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: hp-bioscfg: Fix class device unregistration (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: make fw_attr_class constant (stable-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Directly use firmware_attributes_class (stable-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO add (bsc#1243042 ltc#212167).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- pwm: rockchip: Round period/duty down on apply, up on get (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: core: fix NULL dereference on unbind due to stale coupling data (stable-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879) Put the same workaround to avoid file truncation of vmlinux and co in kernel-default-base package, too.\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1246644).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (git-fixes).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (git-fixes).\n- scsi: fnic: Set appropriate logging level for log message (bsc#1246644).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 patches (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb: client: fix parsing of device numbers (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- sprintf.h requires stdarg.h (git-fixes).\n- sprintf.h: mask additional include (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- staging: vchiq_arm: Make vchiq_shutdown never fail (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- sunrpc: fix handling of server side tls alerts (git-fixes).\n- supported.conf: Mark ZL3073X modules supported\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thermal: trip: Use READ_ONCE() for lockless access to trip properties (git-fixes).\n- thermal: trip: Use common set of trip type names (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: Abort suspend on soft disconnect failure (git-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: cfg80211/mac80211: correctly parse S1G beacon optional elements (git-fixes).\n- wifi: cfg80211: fix S1G beacon head validation in nl80211 (git-fixes).\n- wifi: cfg80211: remove scan request n_channels counted_by (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Create separate links for VLAN interfaces (stable-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: Write cnt before copying in ieee80211_copy_rnr_beacon() (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: finish link init before RCU publish (git-fixes).\n- wifi: mac80211: fix non-transmitted BSSID profile search (git-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: nl80211: Set num_sub_specs before looping through sub_specs (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rt2x00: fix remove callback type mismatch (git-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/CPU/AMD: Add more models to X86_FEATURE_ZEN5 (bsc#1246449).\n- x86/CPU/AMD: Improve the erratum 1386 workaround (git-fixes).\n- x86/CPU/AMD: Terminate the erratum_1386_microcode array (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/cpu: Avoid running off the end of an AMD erratum table (git-fixes).\n- x86/cpu: Expose only stepping min/max interface (git-fixes).\n- x86/cpu: Introduce new microcode matching helper (git-fixes).\n- x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id' (git-fixes).\n- x86/cpu: Replace PEBS use of 'x86_cpu_desc' use with 'x86_cpu_id' (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/mtrr: Rename mtrr_overwrite_state() to guest_force_mtrr_state() (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-28T12:06:15Z","modified":"2026-03-23T04:47:56.876997Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:03023-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may (bsc#1139073)\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357: x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- Fix dma_unmap_sg() nents value (git-fixes)\n- Reapply 'wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()' (git-fixes).\n- Revert 'ACPI: battery: negate current when discharging' (stable-fixes).\n- Revert 'cgroup_freezer: cgroup_freezing: Check if not frozen' (bsc#1219338).\n- Revert 'drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1' (stable-fixes).\n- Revert 'mmc: sdhci: Disable SD card clock before changing parameters' (git-fixes).\n- Revert 'usb: xhci: Implement xhci_handshake_check_state() helper' (git-fixes).\n- Revert 'vgacon: Add check for vc_origin address range in vgacon_scroll()' (stable-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- acpi: LPSS: Remove AudioDSP related ID (git-fixes).\n- acpi: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- acpi: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- acpica: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- alsa: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- alsa: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- alsa: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- alsa: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- alsa: hda/tegra: Add Tegra264 support (stable-fixes).\n- alsa: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- alsa: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- alsa: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- alsa: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- alsa: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- alsa: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- asoc: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- asoc: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- asoc: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- asoc: amd: yc: update quirk data for HP Victus (stable-fixes).\n- asoc: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- asoc: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- asoc: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- asoc: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- asoc: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- asoc: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- asoc: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- asoc: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- docs/aBI: Fix sysfs-kernel-address_bits path (git-fixes).\n- documentation: ACPI: Fix parent device references (git-fixes).\n- documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hid: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- hid: core: do not bypass hid_hw_raw_request (stable-fixes).\n- hid: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- hid: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- hid: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- hid: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- ib/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- input: iqs7222 - explicitly define number of external channels (git-fixes).\n- input: xpad - adjust error handling for disconnect (git-fixes).\n- input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- logitech C-270 even more broken (stable-fixes).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfs: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- nfs: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- nfs: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- nfs: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- nfsd: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nfsv4.2: another fix for listxattr (git-fixes).\n- nfsv4.2: fix listxattr to return selinux security label (git-fixes).\n- nfsv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- nfsv4: Always set NLINK even if the server does not support it (git-fixes).\n- nfsv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- pci/msi: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- pci: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- pci: endpoint: Fix configfs group list head handling (git-fixes).\n- pci: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- pci: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- pci: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- pci: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- pci: rockchip-host: Fix 'Unexpected Completion' log message (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- pm / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- rdma/core: Rate limit GID cache warning messages (git-fixes)\n- rdma/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- rdma/hns: Drop GFP_NOWARN (git-fixes)\n- rdma/hns: Fix -Wframe-larger-than issue (git-fixes)\n- rdma/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- rdma/hns: Fix accessing uninitialized resources (git-fixes)\n- rdma/hns: Fix double destruction of rsv_qp (git-fixes)\n- rdma/hns: Get message length of ack_req from FW (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- rdma/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- rdma/mlx5: Fix CC counters query for MPV (git-fixes)\n- rdma/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- rdma/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- rdma/mlx5: Fix vport loopback for MPV device (git-fixes)\n- rdma/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- rdma/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- rdma/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- rdma/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- rdma/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879) Put the same workaround to avoid file truncation of vmlinux and co in kernel-default-base package, too.\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- smb3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- supported.conf: add missing entries for armv7hl\n- supported.conf: move nvme-apple to optional again\n- supported.conf: sort entries again\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- usb: serial: option: add Foxconn T99W640 (stable-fixes).\n- usb: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-29T11:54:08Z","modified":"2026-02-04T02:27:27.47331Z","updated_at":"2026-11-02T15:53:57.111474Z"},{"id":"SUSE-SU-2025:20577-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357:\n  x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between\n  handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Correctly put RDMA kabi patch into patches.kabi instead of patches.suse\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- PCI: rockchip-host: Fix \"Unexpected Completion\" log message (git-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- Reapply \"wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()\" (git-fixes).\n- Revert \"ACPI: battery: negate current when discharging\" (stable-fixes).\n- Revert \"cgroup_freezer: cgroup_freezing: Check if not frozen\" (bsc#1219338).\n- Revert \"drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1\" (stable-fixes).\n- Revert \"mmc: sdhci: Disable SD card clock before changing parameters\" (git-fixes).\n- Revert \"usb: xhci: Implement xhci_handshake_check_state() helper\" (git-fixes).\n- Revert \"vgacon: Add check for vc_origin address range in vgacon_scroll()\" (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- config: enable RBD (jsc#PED-13238)\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 patches (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-25T13:29:45Z","modified":"2026-03-23T04:48:19.913718Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20586-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357:\n  x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between\n  handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- PCI: rockchip-host: Fix \"Unexpected Completion\" log message (git-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- Reapply \"wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()\" (git-fixes).\n- Revert \"ACPI: battery: negate current when discharging\" (stable-fixes).\n- Revert \"cgroup_freezer: cgroup_freezing: Check if not frozen\" (bsc#1219338).\n- Revert \"drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1\" (stable-fixes).\n- Revert \"mmc: sdhci: Disable SD card clock before changing parameters\" (git-fixes).\n- Revert \"usb: xhci: Implement xhci_handshake_check_state() helper\" (git-fixes).\n- Revert \"vgacon: Add check for vc_origin address range in vgacon_scroll()\" (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- config: enable RBD (jsc#PED-13238)\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 patches (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-25T13:33:57Z","modified":"2026-03-23T04:48:20.488023Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20601-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357:\n  x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between\n  handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Correctly put RDMA kabi patch into patches.kabi instead of patches.suse\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- PCI: rockchip-host: Fix \"Unexpected Completion\" log message (git-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- Reapply \"wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()\" (git-fixes).\n- Revert \"ACPI: battery: negate current when discharging\" (stable-fixes).\n- Revert \"cgroup_freezer: cgroup_freezing: Check if not frozen\" (bsc#1219338).\n- Revert \"drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1\" (stable-fixes).\n- Revert \"mmc: sdhci: Disable SD card clock before changing parameters\" (git-fixes).\n- Revert \"usb: xhci: Implement xhci_handshake_check_state() helper\" (git-fixes).\n- Revert \"vgacon: Add check for vc_origin address range in vgacon_scroll()\" (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- config: enable RBD (jsc#PED-13238)\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 patches (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-25T11:19:19Z","modified":"2026-03-23T04:49:01.134607Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20602-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may\n- CVE-2024-36028: mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio() (bsc#1225707).\n- CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357:\n  x86/process: Move the buffer clearing before MONITOR (bsc#1238896).\n- CVE-2024-44963: btrfs: do not BUG_ON() when freeing tree block after error (bsc#1230216).\n- CVE-2024-56742: vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages() (bsc#1235613).\n- CVE-2025-21839: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (bsc#1239061).\n- CVE-2025-21872: efi/mokvar-table: Avoid repeated map/unmap of the same page (bsc#1240323).\n- CVE-2025-23163: net: vlan: do not propagate flags on open (bsc#1242837).\n- CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).\n- CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37920: kABI workaround for xsk: Fix race condition in AF_XDP generic RX path (bsc#1243479).\n- CVE-2025-37984: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() (bsc#1243669).\n- CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).\n- CVE-2025-38035: nvmet-tcp: do not restore null sk_state_change (bsc#1244801).\n- CVE-2025-38051: smb: client: Fix use-after-free in cifs_fill_dirent (bsc#1244750).\n- CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).\n- CVE-2025-38061: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (bsc#1245440).\n- CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).\n- CVE-2025-38063: dm: fix unconditional IO throttle caused by REQ_PREFLUSH (bsc#1245202).\n- CVE-2025-38064: virtio: break and reset virtio devices on device_shutdown() (bsc#1245201).\n- CVE-2025-38074: vhost-scsi: protect vq-\u003elog_used with vq-\u003emutex (bsc#1244735).\n- CVE-2025-38094: net: cadence: macb: Fix a possible deadlock in macb_halt_tx (bsc#1245649).\n- CVE-2025-38097: kabi: restore encap_sk in struct xfrm_state (bsc#1245660).\n- CVE-2025-38098: drm/amd/display: Do not treat wb connector as physical in (bsc#1245654).\n- CVE-2025-38099: Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers (bsc#1245671).\n- CVE-2025-38100: x86/iopl: Cure TIF_IO_BITMAP inconsistencies (bsc#1245650).\n- CVE-2025-38105: ALSA: usb-audio: Kill timer properly at removal (bsc#1245682).\n- CVE-2025-38115: net_sched: sch_sfq: fix a potential crash on gso_skb handling (bsc#1245689).\n- CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).\n- CVE-2025-38126: net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping (bsc#1245708).\n- CVE-2025-38131: coresight: prevent deactivate active config while enabling the config (bsc#1245677).\n- CVE-2025-38132: coresight: holding cscfg_csdev_lock while removing cscfg from csdev (bsc#1245679).\n- CVE-2025-38147: calipso: unlock rcu before returning -EAFNOSUPPORT (bsc#1245768).\n- CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error (bsc#1245750).\n- CVE-2025-38162: netfilter: nft_set_pipapo: prevent overflow in lookup table allocation (bsc#1245752).\n- CVE-2025-38166: bpf: fix ktls panic with sockmap (bsc#1245758).\n- CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).\n- CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).\n- CVE-2025-38183: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() (bsc#1246006).\n- CVE-2025-38187: drm/nouveau: fix a use-after-free in r535_gsp_rpc_push() (bsc#1245951).\n- CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE (bsc#1246098).\n- CVE-2025-38200: i40e: fix MMIO write access to an invalid page in i40e_clear_hw (bsc#1246045).\n- CVE-2025-38202: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (bsc#1245980).\n- CVE-2025-38203: jfs: Fix null-ptr-deref in jfs_ioc_trim (bsc#1246044).\n- CVE-2025-38204: jfs: fix array-index-out-of-bounds read in add_missing_indices (bsc#1245983).\n- CVE-2025-38206: exfat: fix double free in delayed_free (bsc#1246073).\n- CVE-2025-38210: configfs-tsm-report: Fix NULL dereference of tsm_ops (bsc#1246020).\n- CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU (bsc#1246029).\n- CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).\n- CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).\n- CVE-2025-38236: af_unix: Disable MSG_OOB for unprivileged users (bsc#1246093).\n- CVE-2025-38239: scsi: megaraid_sas: Fix invalid node index (bsc#1246178).\n- CVE-2025-38244: smb: client: fix potential deadlock when reconnecting channels (bsc#1246183).\n- CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration (bsc#1246173).\n- CVE-2025-38250: kABI workaround for bluetooth hci_dev changes (bsc#1246182).\n- CVE-2025-38264: llist: add interface to check if a node is on a list (bsc#1246387).\n- CVE-2025-38272: net: dsa: b53: do not enable EEE on bcm63xx (bsc#1246268).\n- CVE-2025-38279: selftests/bpf: Add tests with stack ptr register in conditional jmp (bsc#1246264).\n- CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver (bsc#1246273).\n- CVE-2025-38303: Bluetooth: eir: Fix possible crashes on eir_create_adv_data (bsc#1246354).\n- CVE-2025-38310: seg6: Fix validation of nexthop addresses (bsc#1246361).\n- CVE-2025-38323: net: atm: add lec_mutex (bsc#1246473).\n- CVE-2025-38334: x86/sgx: Prevent attempts to reclaim poisoned pages (bsc#1246384).\n- CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT (bsc#1246250).\n- CVE-2025-38337: jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata() (bsc#1246253).\n- CVE-2025-38349: eventpoll: do not decrement ep refcount while still holding the ep mutex (bsc#1246777).\n- CVE-2025-38350: net/sched: Always pass notifications when child class becomes empty (bsc#1246781).\n- CVE-2025-38352: posix-cpu-timers: fix race between\n  handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38364: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() (bsc#1247091).\n- CVE-2025-38365: btrfs: fix a race between renames and directory logging (bsc#1247023).\n- CVE-2025-38371: drm/v3d: Disable interrupts before resetting the GPU (bsc#1247178).\n- CVE-2025-38375: virtio-net: ensure the received length does not exceed allocated size (bsc#1247177).\n- CVE-2025-38382: btrfs: fix iteration of extrefs during log replay (bsc#1247031).\n- CVE-2025-38392: idpf: convert control queue mutex to a spinlock (bsc#1247169).\n- CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (bsc#1247156).\n- CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (bsc#1247097).\n- CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it (bsc#1247141).\n- CVE-2025-38414: wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850 (bsc#1247145).\n- CVE-2025-38426: drm/amdgpu: Add basic validation for RAS header (bsc#1247252).\n- CVE-2025-38429: bus: mhi: ep: Update read pointer only after buffer is written (bsc#1247253).\n- CVE-2025-38455: KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight (bsc#1247101).\n- CVE-2025-38457: net/sched: Abort __tc_modify_qdisc if parent class does not exist (bsc#1247098).\n- CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd() (bsc#1247143).\n- CVE-2025-38461: vsock: Fix transport_* TOCTOU (bsc#1247103).\n- CVE-2025-38462: vsock: Fix transport_{g2h,h2g} TOCTOU (bsc#1247104).\n- CVE-2025-38463: tcp: Correct signedness in skb remaining space calculation (bsc#1247113).\n- CVE-2025-38465: netlink: make sure we allow at least one dump skb (bsc#1247118).\n- CVE-2025-38470: kABI fix for net: vlan: fix VLAN 0 refcount imbalance of toggling (bsc#1247288).\n- CVE-2025-38471: tls: always refresh the queue when reading sock (bsc#1247450).\n- CVE-2025-38497: usb: gadget: configfs: Fix OOB read on empty string write (bsc#1247347).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n\nThe following non-security bugs were fixed:\n\n- ACPI: LPSS: Remove AudioDSP related ID (git-fixes).\n- ACPI: PRM: Reduce unnecessary printing to avoid user confusion (bsc#1246122).\n- ACPI: processor: perflib: Fix initial _PPC limit application (git-fixes).\n- ACPICA: Refuse to evaluate a method if arguments are missing (stable-fixes).\n- ALSA: hda/ca0132: Fix missing error handling in ca0132_alt_select_out() (git-fixes).\n- ALSA: hda/realtek - Add mute LED support for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek - Enable mute LED on HP Pavilion Laptop 15-eg100 (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Strix G712LWS (stable-fixes).\n- ALSA: hda/tegra: Add Tegra264 support (stable-fixes).\n- ALSA: hda: Add missing NVIDIA HDA codec IDs (stable-fixes).\n- ALSA: hda: Add new pci id for AMD GPU display HD audio controller (stable-fixes).\n- ALSA: hda: Ignore unsol events for cards being shut down (stable-fixes).\n- ALSA: intel_hdmi: Fix off-by-one error in __hdmi_lpe_audio_probe() (git-fixes).\n- ALSA: sb: Do not allow changing the DMA mode during operations (stable-fixes).\n- ALSA: sb: Force to disable DMAs once when DMA mode is changed (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Lenovo IdeaPad Slim 5 15 (stable-fixes).\n- ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic (stable-fixes).\n- ASoC: amd: yc: add quirk for Acer Nitro ANV15-41 internal mic (stable-fixes).\n- ASoC: amd: yc: update quirk data for HP Victus (stable-fixes).\n- ASoC: codec: wcd9335: Convert to GPIO descriptors (stable-fixes).\n- ASoC: codecs: wcd9335: Fix missing free of regulator supplies (git-fixes).\n- ASoC: codecs: wcd9335: Handle nicer probe deferral and simplify with dev_err_probe() (stable-fixes).\n- ASoC: cs35l56: probe() should fail if the device ID is not recognized (git-fixes).\n- ASoC: fsl_asrc: use internal measured ratio for non-ideal ratio mode (git-fixes).\n- ASoC: fsl_xcvr: get channel status data when PHY is not exists (git-fixes).\n- ASoC: ops: dynamically allocate struct snd_ctl_elem_value (git-fixes).\n- ASoC: soc-dai: tidyup return value of snd_soc_xlate_tdm_slot_mask() (git-fixes).\n- Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix L2CAP MTU negotiation (stable-fixes).\n- Bluetooth: L2CAP: Fix attempting to adjust outgoing MTU (git-fixes).\n- Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT (git-fixes).\n- Bluetooth: MGMT: mesh_send: check instances prior disabling advertising (git-fixes).\n- Bluetooth: MGMT: set_mesh: update LE scan interval and window (git-fixes).\n- Bluetooth: Prevent unintended pause by checking if advertising is active (git-fixes).\n- Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout (git-fixes).\n- Bluetooth: SMP: If an unallowed command is received consider it a failure (git-fixes).\n- Bluetooth: btusb: QCA: Fix downloading wrong NVM for WCN6855 GF variant without board ID (git-fixes).\n- Bluetooth: hci_conn: Fix sending BT_HCI_CMD_LE_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_event: Fix not marking Broadcast Sink BIS as connected (git-fixes).\n- Bluetooth: hci_event: Mask data status from LE ext adv reports (git-fixes).\n- Bluetooth: hci_sync: Attempt to dequeue connection attempt (git-fixes).\n- Bluetooth: hci_sync: Fix UAF on create_le_conn_complete (git-fixes).\n- Bluetooth: hci_sync: Fix handling of HCI_OP_CREATE_CONN_CANCEL (git-fixes).\n- Bluetooth: hci_sync: Fix not disabling advertising instance (git-fixes).\n- Bluetooth: hci_sync: fix connectable extended advertising when using static random address (git-fixes).\n- Bluetooth: hci_sync: revert some mesh modifications (git-fixes).\n- Docs/ABI: Fix sysfs-kernel-address_bits path (git-fixes).\n- Documentation: ACPI: Fix parent device references (git-fixes).\n- Documentation: usb: gadget: Wrap remaining usage snippets in literal code block (git-fixes).\n- Fix dma_unmap_sg() nents value (git-fixes)\n- HID: Add IGNORE quirk for SMARTLINKTECHNOLOGY (stable-fixes).\n- HID: core: do not bypass hid_hw_raw_request (stable-fixes).\n- HID: core: ensure __hid_request reserves the report ID as the first byte (git-fixes).\n- HID: core: ensure the allocated report buffer can contain the reserved report ID (stable-fixes).\n- HID: lenovo: Add support for ThinkPad X1 Tablet Thin Keyboard Gen2 (stable-fixes).\n- HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras (stable-fixes).\n- IB/mlx5: Fix potential deadlock in MR deregistration (git-fixes)\n- Input: iqs7222 - explicitly define number of external channels (git-fixes).\n- Input: xpad - adjust error handling for disconnect (git-fixes).\n- Input: xpad - set correct controller type for Acer NGR200 (git-fixes).\n- Input: xpad - support Acer NGR 200 Controller (stable-fixes).\n- Logitech C-270 even more broken (stable-fixes).\n- Move upstreamed SCSI and ACPI patches into sorted section\n- NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() (git-fixes).\n- NFS: Fix the setting of capabilities when automounting a new filesystem (git-fixes).\n- NFS: Fix wakeup of __nfs_lookup_revalidate() in unblock_revalidate() (git-fixes).\n- NFS: Fixup allocation flags for nfsiod's __GFP_NORETRY (git-fixes).\n- NFSD: detect mismatch of file handle and delegation stateid in OPEN op (git-fixes).\n- NFSv4.2: another fix for listxattr (git-fixes).\n- NFSv4.2: fix listxattr to return selinux security label (git-fixes).\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (git-fixes).\n- NFSv4: Always set NLINK even if the server does not support it (git-fixes).\n- NFSv4: xattr handlers should check for absent nfs filehandles (git-fixes).\n- PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations (bsc#1245457).\n- PCI: dwc: Make link training more robust by setting PORT_LOGIC_LINK_WIDTH to one lane (stable-fixes).\n- PCI: endpoint: Fix configfs group list head handling (git-fixes).\n- PCI: endpoint: Fix configfs group removal on driver teardown (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Fix the incorrect usage of __iomem attribute (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Return -ENOENT if pci_epc_get_next_free_bar() fails (git-fixes).\n- PCI: hv: Allow dynamic MSI-X vector allocation (bsc#1245457).\n- PCI: rockchip-host: Fix \"Unexpected Completion\" log message (git-fixes).\n- PM / devfreq: Check governor before using governor-\u003ename (git-fixes).\n- RDMA/core: Rate limit GID cache warning messages (git-fixes)\n- RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes)\n- RDMA/hns: Drop GFP_NOWARN (git-fixes)\n- RDMA/hns: Fix -Wframe-larger-than issue (git-fixes)\n- RDMA/hns: Fix HW configurations not cleared in error flow (git-fixes)\n- RDMA/hns: Fix accessing uninitialized resources (git-fixes)\n- RDMA/hns: Fix double destruction of rsv_qp (git-fixes)\n- RDMA/hns: Get message length of ack_req from FW (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes)\n- RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- RDMA/mlx5: Fix CC counters query for MPV (git-fixes)\n- RDMA/mlx5: Fix HW counters query for non-representor devices (git-fixes)\n- RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes)\n- RDMA/mlx5: Fix vport loopback for MPV device (git-fixes)\n- RDMA/mlx5: Initialize obj_event-\u003eobj_sub_list before xa_insert (git-fixes)\n- RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes)\n- RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages (git-fixes)\n- RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes)\n- RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes)\n- Reapply \"wifi: mac80211: Update skb's control block key in ieee80211_tx_dequeue()\" (git-fixes).\n- Revert \"ACPI: battery: negate current when discharging\" (stable-fixes).\n- Revert \"cgroup_freezer: cgroup_freezing: Check if not frozen\" (bsc#1219338).\n- Revert \"drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1\" (stable-fixes).\n- Revert \"mmc: sdhci: Disable SD card clock before changing parameters\" (git-fixes).\n- Revert \"usb: xhci: Implement xhci_handshake_check_state() helper\" (git-fixes).\n- Revert \"vgacon: Add check for vc_origin address range in vgacon_scroll()\" (stable-fixes).\n- SMB3: rename macro CIFS_SERVER_IS_CHAN to avoid confusion (git-fixes).\n- USB: serial: ftdi_sio: add support for NDI EMGUIDE GEMINI (stable-fixes).\n- USB: serial: option: add Foxconn T99W640 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 (ECM) composition (stable-fixes).\n- [SMB3] send channel sequence number in SMB3 requests after reconnects (git-fixes).\n- af_packet: fix the SO_SNDTIMEO constraint not effective on tpacked_snd() (git-fixes).\n- af_unix: Add a prompt to CONFIG_AF_UNIX_OOB (bsc#1246093).\n- amd/amdkfd: fix a kfd_process ref leak (stable-fixes).\n- aoe: clean device rq_list in aoedev_downdev() (git-fixes).\n- apple-mfi-fastcharge: protect first device name (git-fixes).\n- ata: pata_cs5536: fix build on 32-bit UML (stable-fixes).\n- audit,module: restore audit logging in load failure case (git-fixes).\n- bpf, sockmap: Fix sk_msg_reset_curr (git-fixes).\n- bpf/lpm_trie: Inline longest_prefix_match for fastpath (git-fixes).\n- bpf/selftests: Check errno when percpu map value size exceeds (git-fixes).\n- bpf: Add a possibly-zero-sized read test (git-fixes).\n- bpf: Avoid __hidden__ attribute in static object (git-fixes).\n- bpf: Check percpu map value size first (git-fixes).\n- bpf: Disable some `attribute ignored' warnings in GCC (git-fixes).\n- bpf: Fix memory leak in bpf_core_apply (git-fixes).\n- bpf: Fix potential integer overflow in resolve_btfids (git-fixes).\n- bpf: Harden __bpf_kfunc tag against linker kfunc removal (git-fixes).\n- bpf: Make the pointer returned by iter next method valid (git-fixes).\n- bpf: Simplify checking size of helper accesses (git-fixes).\n- bpf: fix order of args in call to bpf_map_kvcalloc (git-fixes).\n- bpf: sockmap, updating the sg structure should also update curr (git-fixes).\n- bpftool: Fix missing pids during link show (git-fixes).\n- bpftool: Fix undefined behavior caused by shifting into the sign bit (git-fixes).\n- bpftool: Mount bpffs on provided dir instead of parent dir (git-fixes).\n- bpftool: Remove unnecessary source files from bootstrap version (git-fixes).\n- bpftool: Un-const bpf_func_info to fix it for llvm 17 and newer (git-fixes).\n- btrfs: do not ignore inode missing when replaying log tree (git-fixes).\n- btrfs: do not silently ignore unexpected extent type when replaying log (git-fixes).\n- btrfs: do not skip remaining extrefs if dir not found during log replay (git-fixes).\n- btrfs: explicitly ref count block_group on new_bgs list (bsc#1243068)\n- btrfs: fix assertion when building free space tree (git-fixes).\n- btrfs: fix inode lookup error handling during log replay (git-fixes).\n- btrfs: fix invalid inode pointer dereferences during log replay (git-fixes).\n- btrfs: fix log tree replay failure due to file with 0 links and extents (git-fixes).\n- btrfs: fix missing error handling when searching for inode refs during log replay (git-fixes).\n- btrfs: fix non-empty delayed iputs list on unmount due to async workers (git-fixes).\n- btrfs: fix ssd_spread overallocation (git-fixes).\n- btrfs: make btrfs_discard_workfn() block_group ref explicit (bsc#1243068)\n- btrfs: propagate last_unlink_trans earlier when doing a rmdir (git-fixes).\n- btrfs: rename err to ret in btrfs_rmdir() (git-fixes).\n- btrfs: return a btrfs_inode from btrfs_iget_logging() (git-fixes).\n- btrfs: return a btrfs_inode from read_one_inode() (git-fixes).\n- btrfs: tests: fix chunk map leak after failure to add it to the tree (git-fixes).\n- btrfs: update superblock's device bytes_used when dropping chunk (git-fixes).\n- btrfs: use NOFS context when getting inodes during logging and log replay (git-fixes).\n- btrfs: use btrfs_record_snapshot_destroy() during rmdir (git-fixes).\n- bus: fsl-mc: Fix potential double device reference in fsl_mc_get_endpoint() (git-fixes).\n- bus: mhi: host: Detect events pointing to unexpected TREs (git-fixes).\n- can: dev: can_restart(): move debug message and stats after successful restart (stable-fixes).\n- can: dev: can_restart(): reverse logic to remove need for goto (stable-fixes).\n- can: kvaser_pciefd: Store device channel index (git-fixes).\n- can: kvaser_usb: Assign netdev.dev_port based on device channel index (git-fixes).\n- can: m_can: m_can_handle_lost_msg(): downgrade msg lost in rx message to debug level (git-fixes).\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (git-fixes).\n- can: peak_usb: fix USB FD devices potential malfunction (git-fixes).\n- cdc-acm: fix race between initial clearing halt and open (git-fixes).\n- cgroup,freezer: fix incomplete freezing when attaching tasks (bsc#1245789).\n- cgroup/cpuset: Extend kthread_is_per_cpu() check to all PF_NO_SETAFFINITY tasks (bsc#1241166).\n- cifs: reconnect helper should set reconnect for the right channel (git-fixes).\n- clk: clk-axi-clkgen: fix fpfd_max frequency for zynq (git-fixes).\n- clk: davinci: Add NULL check in davinci_lpsc_clk_register() (git-fixes).\n- clk: sunxi-ng: v3s: Fix de clock definition (git-fixes).\n- clk: xilinx: vcu: unregister pll_post only if registered correctly (git-fixes).\n- clocksource: Scale the watchdog read retries automatically (bsc#1241345 bsc#1244457).\n- clocksource: Set cs_watchdog_read() checks based on .uncertainty_margin (bsc#1241345 bsc#1244457).\n- comedi: Fail COMEDI_INSNLIST ioctl if n_insns is too large (git-fixes).\n- comedi: Fix initialization of data for instructions that write to subdevice (git-fixes).\n- comedi: Fix some signed shift left operations (git-fixes).\n- comedi: Fix use of uninitialized data in insn_rw_emulate_bits() (git-fixes).\n- comedi: aio_iiro_16: Fix bit shift out of bounds (git-fixes).\n- comedi: das16m1: Fix bit shift out of bounds (git-fixes).\n- comedi: das6402: Fix bit shift out of bounds (git-fixes).\n- comedi: pcl812: Fix bit shift out of bounds (git-fixes).\n- compiler_types.h: Define __retain for __attribute__((__retain__)) (git-fixes).\n- config: enable RBD (jsc#PED-13238)\n- crypto: arm/aes-neonbs - work around gcc-15 warning (git-fixes).\n- crypto: ccp - Fix crash when rebind ccp device for ccp.ko (git-fixes).\n- crypto: ccp - Fix locking on alloc failure handling (git-fixes).\n- crypto: img-hash - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: inside-secure - Fix `dma_unmap_sg()` nents value (git-fixes).\n- crypto: keembay - Fix dma_unmap_sg() nents value (git-fixes).\n- crypto: marvell/cesa - Fix engine load inaccuracy (git-fixes).\n- crypto: qat - allow enabling VFs in the absence of IOMMU (git-fixes).\n- crypto: qat - disable ZUC-256 capability for QAT GEN5 (git-fixes).\n- crypto: qat - fix DMA direction for compression on GEN2 devices (git-fixes).\n- crypto: qat - fix seq_file position update in adf_ring_next() (git-fixes).\n- crypto: qat - fix state restore for banks with exceptions (git-fixes).\n- crypto: qat - flush misc workqueue during device shutdown (git-fixes).\n- crypto: qat - use unmanaged allocation for dc_data (git-fixes).\n- crypto: sun8i-ce - fix nents passed to dma_unmap_sg() (git-fixes).\n- dm-bufio: fix sched in atomic context (git-fixes).\n- dm-flakey: error all IOs when num_features is absent (git-fixes).\n- dm-flakey: make corrupting read bios work (git-fixes).\n- dm-mirror: fix a tiny race condition (git-fixes).\n- dm-raid: fix variable in journal device check (git-fixes).\n- dm-verity: fix a memory leak if some arguments are specified multiple times (git-fixes).\n- dm: do not change md if dm_table_set_restrictions() fails (git-fixes).\n- dm: free table mempools if not used in __bind (git-fixes).\n- dm: restrict dm device size to 2^63-512 bytes (git-fixes).\n- dma-buf: fix timeout handling in dma_resv_wait_timeout v2 (stable-fixes).\n- dmaengine: dw-edma: Drop unused dchan2dev() and chan2dev() (git-fixes).\n- dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using (stable-fixes).\n- dmaengine: mv_xor: Fix missing check after DMA map and missing unmap (git-fixes).\n- dmaengine: nbpfaxi: Add missing check after DMA map (git-fixes).\n- dmaengine: nbpfaxi: Fix memory corruption in probe() (git-fixes).\n- dmaengine: qcom: gpi: Drop unused gpi_write_reg_field() (git-fixes).\n- dmaengine: xilinx_dma: Set dma_device directions (stable-fixes).\n- drm/amd/display: Do not overwrite dce60_clk_mgr (git-fixes).\n- drm/amd/pm/powerplay/hwmgr/smu_helper: fix order of mask and value (git-fixes).\n- drm/amdgpu/gfx8: reset compute ring wptr on the GPU on resume (git-fixes).\n- drm/amdgpu: amdgpu_vram_mgr_new(): Clamp lpfn to total vram (stable-fixes).\n- drm/amdkfd: Fix race in GWS queue scheduling (stable-fixes).\n- drm/bridge: panel: move prepare_prev_first handling to drm_panel_bridge_add_typed (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add HPD for DisplayPort connector type (git-fixes).\n- drm/bridge: ti-sn65dsi86: Remove extra semicolon in ti_sn_bridge_probe() (git-fixes).\n- drm/bridge: ti-sn65dsi86: make use of debugfs_init callback (stable-fixes).\n- drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling (git-fixes).\n- drm/exynos: fimd: Guard display clock control with runtime PM calls (git-fixes).\n- drm/framebuffer: Acquire internal references on GEM handles (git-fixes).\n- drm/gem: Acquire references on GEM handles for framebuffers (stable-fixes).\n- drm/gem: Fix race in drm_gem_handle_create_tail() (stable-fixes).\n- drm/i915/gsc: mei interrupt top half should be in irq disabled context (git-fixes).\n- drm/i915/gt: Fix timeline left held on VMA alloc error (git-fixes).\n- drm/i915/selftests: Change mock_request() to return error pointers (git-fixes).\n- drm/msm/dpu: Fill in min_prefill_lines for SC8180X (git-fixes).\n- drm/msm: Fix a fence leak in submit error path (stable-fixes).\n- drm/msm: Fix another leak in the submit error path (stable-fixes).\n- drm/panfrost: Fix panfrost device variable name in devfreq (git-fixes).\n- drm/rockchip: cleanup fb when drm_gem_fb_afbc_init failed (git-fixes).\n- drm/sched: Increment job count before swapping tail spsc queue (git-fixes).\n- drm/sched: Remove optimization that causes hang when killing dependent jobs (git-fixes).\n- drm/scheduler: signal scheduled fence when kill job (stable-fixes).\n- drm/tegra: nvdec: Fix dma_alloc_coherent error check (git-fixes).\n- drm/ttm: fix error handling in ttm_buffer_object_transfer (git-fixes).\n- drm/vmwgfx: Fix Host-Backed userspace on Guest-Backed kernel (git-fixes).\n- exfat: fdatasync flag should be same like generic_write_sync() (git-fixes).\n- fbcon: Fix outdated registered_fb reference in comment (git-fixes).\n- fbdev: imxfb: Check fb_add_videomode to prevent null-ptr-deref (git-fixes).\n- firewire: ohci: correct code comments about bus_reset tasklet (git-fixes).\n- fs/jfs: consolidate sanity checking in dbMount (git-fixes).\n- fs/orangefs: Allow 2 more characters in do_c_string() (git-fixes).\n- gpio: mlxbf2: use platform_get_irq_optional() (git-fixes).\n- gpio: pca953x: log an error when failing to get the reset GPIO (git-fixes).\n- gpio: sim: include a missing header (git-fixes).\n- gpio: vf610: add locking to gpio direction functions (git-fixes).\n- gpio: virtio: Fix config space reading (git-fixes).\n- gpiolib: Fix debug messaging in gpiod_find_and_request() (git-fixes).\n- gpiolib: Handle no pin_ranges in gpiochip_generic_config() (git-fixes).\n- gpiolib: acpi: Do not use GPIO chip fwnode in acpi_gpiochip_find() (bsc#1233300).\n- gpiolib: acpi: Fix failed in acpi_gpiochip_find() by adding parent node match (bsc#1233300).\n- gpiolib: cdev: Ignore reconfiguration without direction (git-fixes).\n- gpiolib: of: Add polarity quirk for s5m8767 (stable-fixes).\n- hfs: make splice write available again (git-fixes).\n- hfsplus: make splice write available again (git-fixes).\n- hfsplus: remove mutex_lock check in hfsplus_free_extents (git-fixes).\n- hv_netvsc: Use VF's tso_max_size value when data path is VF (bsc#1246203).\n- hwmon: (corsair-cpro) Validate the size of the received input buffer (git-fixes).\n- hwmon: (gsc-hwmon) fix fan pwm setpoint show functions (git-fixes).\n- hwmon: (pmbus/max34440) Fix support for max34451 (stable-fixes).\n- hwrng: mtk - handle devm_pm_runtime_enable errors (git-fixes).\n- i2c/designware: Fix an initialization issue (git-fixes).\n- i2c: qup: jump out of the loop in case of timeout (git-fixes).\n- i2c: stm32: fix the device used for the DMA map (git-fixes).\n- i2c: tegra: Fix reset error handling with ACPI (git-fixes).\n- i2c: virtio: Avoid hang by using interruptible completion wait (git-fixes).\n- i3c: fix module_i3c_i2c_driver() with I3C=n (git-fixes).\n- iio: accel: fxls8962af: Fix use after free in fxls8962af_fifo_flush (git-fixes).\n- iio: adc: ad7949: use spi_is_bpw_supported() (git-fixes).\n- iio: adc: ad_sigma_delta: Fix use of uninitialized status_pos (stable-fixes).\n- iio: adc: ad_sigma_delta: change to buffer predisable (git-fixes).\n- iio: adc: max1363: Fix MAX1363_4X_CHANS/MAX1363_8X_CHANS[] (stable-fixes).\n- iio: adc: max1363: Reorder mode_list[] entries (stable-fixes).\n- iio: adc: stm32-adc: Fix race in installing chained IRQ handler (git-fixes).\n- iio: imu: bno055: fix OOB access of hw_xlate array (git-fixes).\n- iio: pressure: zpa2326: Use aligned_s64 for the timestamp (stable-fixes).\n- iommu/amd: Fix geometry.aperture_end for V2 tables (git-fixes).\n- iommu/amd: Set the pgsize_bitmap correctly (git-fixes).\n- iommu/arm-smmu-qcom: Add SM6115 MDSS compatible (git-fixes).\n- iommu/vt-d: Fix possible circular locking dependency (git-fixes).\n- iommu/vt-d: Fix system hang on reboot -f (git-fixes).\n- ipv6: fix possible infinite loop in fib6_info_uses_dev() (git-fixes).\n- ipv6: mcast: Delay put pmc-\u003eidev in mld_del_delrec() (git-fixes).\n- ipv6: prevent infinite loop in rt6_nlmsg_size() (git-fixes).\n- ipv6: reject malicious packets in ipv6_gso_segment() (git-fixes).\n- iwlwifi: Add missing check for alloc_ordered_workqueue (git-fixes).\n- jfs: fix metapage reference count leak in dbAllocCtl (git-fixes).\n- kABI workaround for struct drm_framebuffer changes (git-fixes).\n- kABI: Fix the module::name type in audit_context (git-fixes).\n- kasan: remove kasan_find_vm_area() to prevent possible deadlock (git-fixes).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- leds: multicolor: Fix intensity setting while SW blinking (stable-fixes).\n- lib/group_cpus.c: avoid acquiring cpu hotplug lock in group_cpus_evenly (bsc#1236897).\n- lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (bsc#1236897).\n- maple_tree: fix mt_destroy_walk() on root leaf node (git-fixes).\n- md/md-bitmap: fix dm-raid max_write_behind setting (git-fixes).\n- media: gspca: Add bounds checking to firmware parser (git-fixes).\n- media: hi556: correct the test pattern configuration (git-fixes).\n- media: imx: fix a potential memory leak in imx_media_csc_scaler_device_init() (git-fixes).\n- media: ov2659: Fix memory leaks in ov2659_probe() (git-fixes).\n- media: rainshadow-cec: fix TOCTOU race condition in rain_interrupt() (git-fixes).\n- media: usbtv: Lock resolution while streaming (git-fixes).\n- media: uvcvideo: Do not mark valid metadata as invalid (git-fixes).\n- media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (git-fixes).\n- media: v4l2-ctrls: Do not reset handler's error in v4l2_ctrl_handler_free() (git-fixes).\n- media: v4l2-ctrls: Fix H264 SEPARATE_COLOUR_PLANE check (git-fixes).\n- media: venus: Add a check for packet size after reading from shared memory (git-fixes).\n- media: venus: hfi: explicitly release IRQ during teardown (git-fixes).\n- media: venus: protect against spurious interrupts during probe (git-fixes).\n- media: venus: vdec: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: venus: venc: Clamp param smaller than 1fps and bigger than 240 (git-fixes).\n- media: vivid: fix wrong pixel_array control size (git-fixes).\n- memstick: core: Zero initialize id_reg in h_memstick_read_dev_id() (git-fixes).\n- mfd: max14577: Fix wakeup source leaks on device unbind (stable-fixes).\n- misc: rtsx: usb: Ensure mmc child device is active when card is present (git-fixes).\n- mmc: bcm2835: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier (git-fixes).\n- mmc: sdhci-pci: Quirk for broken command queuing on Intel GLK-based Positivo models (git-fixes).\n- mmc: sdhci: Add a helper function for dump register in dynamic debug mode (stable-fixes).\n- mmc: sdhci_am654: Workaround for Errata i2312 (git-fixes).\n- module: Fix memory deallocation on error path in move_module() (git-fixes).\n- module: Remove unnecessary +1 from last_unloaded_module::name size (git-fixes).\n- module: Restore the moduleparam prefix length check (git-fixes).\n- mtd: fix possible integer overflow in erase_xfer() (git-fixes).\n- mtd: rawnand: atmel: Fix dma_mapping_error() address (git-fixes).\n- mtd: rawnand: atmel: set pmecc data setup time (git-fixes).\n- mtd: rawnand: fsmc: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: renesas: Add missing check after DMA map (git-fixes).\n- mtd: rawnand: rockchip: Add missing check after DMA map (git-fixes).\n- mtd: spi-nor: Fix spi_nor_try_unlock_all() (git-fixes).\n- mtd: spinand: fix memory leak of ECC engine conf (stable-fixes).\n- mtd: spinand: propagate spinand_wait() errors from spinand_write_page() (git-fixes).\n- mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data (git-fixes).\n- mtk-sd: Prevent memory corruption from DMA map failure (git-fixes).\n- mtk-sd: reset host-\u003emrq on prepare_data() error (git-fixes).\n- mwl8k: Add missing check after DMA map (git-fixes).\n- nbd: fix uaf in nbd_genl_connect() error path (git-fixes).\n- net/packet: fix a race in packet_set_ring() and packet_notifier() (git-fixes).\n- net/sched: Restrict conditions for adding duplicating netems to qdisc tree (git-fixes).\n- net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree (git-fixes).\n- net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (git-fixes).\n- net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class (git-fixes).\n- net/sched: sch_qfq: Fix race condition on qfq_aggregate (git-fixes).\n- net/sched: taprio: enforce minimum value for picos_per_byte (git-fixes).\n- net: mana: Add debug logs in MANA network driver (bsc#1246212).\n- net: mana: Add handler for hardware servicing events (bsc#1245730).\n- net: mana: Allocate MSI-X vectors dynamically (bsc#1245457).\n- net: mana: Allow irq_setup() to skip cpus for affinity (bsc#1245457).\n- net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE (bsc#1246203).\n- net: mana: Expose additional hardware counters for drop and TC via ethtool (bsc#1245729).\n- net: mana: Set tx_packets to post gso processing packet count (bsc#1245731).\n- net: mana: explain irq_setup() algorithm (bsc#1245457).\n- net: phy: Do not register LEDs for genphy (git-fixes).\n- net: phy: micrel: fix KSZ8081/KSZ8091 cable test (git-fixes).\n- net: phy: microchip: limit 100M workaround to link-down events on LAN88xx (git-fixes).\n- net: phy: smsc: Fix Auto-MDIX configuration when disabled by strap (git-fixes).\n- net: phy: smsc: Fix link failure in forced mode with Auto-MDIX (git-fixes).\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect (git-fixes).\n- net: usb: qmi_wwan: add SIMCom 8230C composition (stable-fixes).\n- net: usbnet: Avoid potential RCU stall on LINK_CHANGE event (git-fixes).\n- net: usbnet: Fix the wrong netif_carrier_on() call (git-fixes).\n- netpoll: prevent hanging NAPI when netcons gets enabled (git-fixes).\n- nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (git-fixes).\n- nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (git-fixes).\n- nilfs2: reject invalid file types when reading inodes (git-fixes).\n- nvme-pci: refresh visible attrs after being checked (git-fixes).\n- nvme: Fix incorrect cdw15 value in passthru error logging (git-fixes).\n- nvme: fix endianness of command word prints in nvme_log_err_passthru() (git-fixes).\n- nvme: fix inconsistent RCU list manipulation in nvme_ns_add_to_ctrl_list() (git-fixes).\n- nvme: fix misaccounting of nvme-mpath inflight I/O (git-fixes).\n- nvmet-tcp: fix callback lock for TLS handshake (git-fixes).\n- objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret() (git-fixes).\n- objtool: Fix UNWIND_HINT_{SAVE,RESTORE} across basic blocks (git-fixes).\n- objtool: Fix _THIS_IP_ detection for cold functions (git-fixes).\n- objtool: Fix error handling inconsistencies in check() (git-fixes).\n- objtool: Ignore dangling jump table entries (git-fixes).\n- objtool: Ignore end-of-section jumps for KCOV/GCOV (git-fixes).\n- objtool: Properly disable uaccess validation (git-fixes).\n- objtool: Silence more KCOV warnings (git-fixes).\n- objtool: Silence more KCOV warnings, part 2 (git-fixes).\n- objtool: Stop UNRET validation on UD2 (git-fixes).\n- pNFS/flexfiles: do not attempt pnfs on fatal DS errors (git-fixes).\n- pch_uart: Fix dma_sync_sg_for_device() nents value (git-fixes).\n- perf: Fix sample vs do_exit() (bsc#1246547).\n- phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode (git-fixes).\n- pinctrl: amd: Clear GPIO debounce for suspend (git-fixes).\n- pinctrl: qcom: msm: mark certain pins as invalid for interrupts (git-fixes).\n- pinctrl: sunxi: Fix memory leak on krealloc failure (git-fixes).\n- pinmux: fix race causing mux_owner NULL with active mux_usecount (git-fixes).\n- platform/chrome: cros_ec: Unregister notifier in cros_ec_unregister() (git-fixes).\n- platform/mellanox: mlxbf-pmc: Fix duplicate event ID for CACHE_DATA1 (git-fixes).\n- platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment (git-fixes).\n- platform/mellanox: mlxreg-lc: Fix logic error in power state check (git-fixes).\n- platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message (git-fixes).\n- platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks (git-fixes).\n- platform/x86: ideapad-laptop: Fix kbd backlight not remembered among boots (git-fixes).\n- platform/x86: think-lmi: Create ksets consecutively (stable-fixes).\n- platform/x86: think-lmi: Fix kobject cleanup (git-fixes).\n- platform/x86: think-lmi: Fix sysfs group cleanup (git-fixes).\n- power: supply: cpcap-charger: Fix null check for power_supply_get_by_name (git-fixes).\n- power: supply: max14577: Handle NULL pdata when CONFIG_OF is not set (git-fixes).\n- powercap: call put_device() on an error path in powercap_register_control_type() (stable-fixes).\n- powercap: dtpm_cpu: Fix NULL pointer dereference in get_pd_power_uw() (git-fixes).\n- powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed (git-fixes).\n- powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH (git-fixes).\n- ptp: fix breakage after ptp_vclock_in_use() rework (bsc#1246506).\n- pwm: imx-tpm: Reset counter if CMOD is 0 (git-fixes).\n- pwm: mediatek: Ensure to disable clocks in error path (git-fixes).\n- regmap: fix potential memory leak of regmap_bus (git-fixes).\n- regulator: fan53555: add enable_time support and soft-start times (stable-fixes).\n- regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (git-fixes).\n- regulator: pwm-regulator: Calculate the output voltage for disabled PWMs (stable-fixes).\n- resource: fix false warning in __request_region() (git-fixes).\n- restore UCSI_CONNECTOR_RESET_HARD definition (git-fixes).\n- ring-buffer: Do not allow events in NMI with generic atomic64 cmpxchg() (git-fixes).\n- rose: fix dangling neighbour pointers in rose_rt_device_down() (git-fixes).\n- rpl: Fix use-after-free in rpl_do_srh_inline() (git-fixes).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rtc: ds1307: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: hym8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: nct3018y: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf85063: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: pcf8563: fix incorrect maximum clock rate handling (git-fixes).\n- rtc: rv3028: fix incorrect maximum clock rate handling (git-fixes).\n- s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again (git-fixes bsc#1246870).\n- s390/entry: Fix last breaking event handling in case of stack corruption (git-fixes bsc#1243806).\n- s390/pci: Do not try re-enabling load/store if device is disabled (git-fixes bsc#1245646).\n- s390/pci: Fix stale function handles in error handling (git-fixes bsc#1245647).\n- s390/pkey: Prevent overflow in size calculation for memdup_user() (git-fixes bsc#1245598).\n- s390: Add z17 elf platform (LTC#214086 bsc#1245540).\n- samples: mei: Fix building on musl libc (git-fixes).\n- sched,freezer: Remove unnecessary warning in __thaw_task (bsc#1219338).\n- sched: Add test_and_clear_wake_up_bit() and atomic_dec_and_wake_up() (git-fixes).\n- scsi: core: Enforce unlimited max_segment_size when virt_boundary_mask is set (git-fixes).\n- scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Copyright updates for 14.4.0.10 patches (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Early return out of FDMI cmpl for locally rejected statuses (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Ensure HBA_SETUP flag is used only for SLI4 in dev_loss_tmo_callbk (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Modify end-of-life adapters' model descriptions (bsc#1245260 bsc#1243100 bsc#1246125 bsc#1204142).\n- scsi: lpfc: Move clearing of HBA_SETUP flag to before lpfc_sli4_queue_unset (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Relocate clearing initial phba flags from link up to link down hdlr (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise CQ_CREATE_SET mailbox bitfield definitions (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Revise logging format for failed CT MIB requests (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Simplify error handling for failed lpfc_get_sli4_parameters cmd (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Skip RSCN processing when FC_UNLOADING flag is set (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update debugfs trace ring initialization messages (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: lpfc: Update lpfc version to 14.4.0.10 (bsc#1245260 bsc#1243100 bsc#1246125).\n- scsi: megaraid_sas: Fix invalid node index (git-fixes).\n- scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database() (git-fixes).\n- scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu() (git-fixes).\n- scsi: s390: zfcp: Ensure synchronous unit_add (git-fixes bsc#1245599).\n- selftests/bpf: Add CFLAGS per source file and runner (git-fixes).\n- selftests/bpf: Add tests for iter next method returning valid pointer (git-fixes).\n- selftests/bpf: Change functions definitions to support GCC (git-fixes).\n- selftests/bpf: Fix a few tests for GCC related warnings (git-fixes).\n- selftests/bpf: Fix pointer arithmetic in test_xdp_do_redirect (git-fixes).\n- selftests/bpf: Fix prog numbers in test_sockmap (git-fixes).\n- smb3: move server check earlier when setting channel sequence number (git-fixes).\n- soc/tegra: cbb: Clear ERR_FORCE register with ERR_STATUS (git-fixes).\n- soc: aspeed: lpc-snoop: Cleanup resources in stack-order (git-fixes).\n- soc: aspeed: lpc-snoop: Do not disable channels that are not enabled (git-fixes).\n- soc: qcom: QMI encoding/decoding for big endian (git-fixes).\n- soc: qcom: fix endianness for QMI header (git-fixes).\n- soc: qcom: pmic_glink: fix OF node leak (git-fixes).\n- soundwire: amd: fix for clearing command status register (git-fixes).\n- soundwire: stream: restore params when prepare ports fail (git-fixes).\n- spi: spi-fsl-dspi: Clear completion counter before initiating transfer (git-fixes).\n- staging: axis-fifo: remove sysfs interface (git-fixes).\n- staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() (git-fixes).\n- staging: nvec: Fix incorrect null termination of battery manufacturer (git-fixes).\n- struct cdns: move new member to the end (git-fixes).\n- struct ucsi_operations: use padding for new operation (git-fixes).\n- sunrpc: do not immediately retransmit on seqno miss (git-fixes).\n- sunrpc: fix client side handling of tls alerts (git-fixes).\n- tcp: call tcp_measure_rcv_mss() for ooo packets (git-fixes).\n- thunderbolt: Fix bit masking in tb_dp_port_set_hops() (git-fixes).\n- thunderbolt: Fix copy+paste error in match_service_id() (git-fixes).\n- thunderbolt: Fix wake on connect at runtime (git-fixes).\n- tracing/kprobe: Make trace_kprobe's module callback called after jump_label update (git-fixes).\n- tracing/kprobes: Fix to free objects when failed to copy a symbol (git-fixes).\n- types: Complement the aligned types with signed 64-bit one (stable-fixes).\n- ucount: fix atomic_long_inc_below() argument type (git-fixes).\n- ucsi-glink: adapt to kABI consistency (git-fixes).\n- ucsi_ccg: Refine the UCSI Interrupt handling (git-fixes).\n- ucsi_operations: add stubs for all operations (git-fixes).\n- ucsi_ops: adapt update_connector to kABI consistency (git-fixes).\n- usb: Add checks for snprintf() calls in usb_alloc_dev() (stable-fixes).\n- usb: atm: cxacru: Merge cxacru_upload_firmware() into cxacru_heavy_init() (git-fixes).\n- usb: cdc-wdm: avoid setting WDM_READ for ZLP-s (stable-fixes).\n- usb: cdnsp: Fix issue with CV Bad Descriptor test (git-fixes).\n- usb: cdnsp: Fix issue with resuming from L1 (git-fixes).\n- usb: cdnsp: Replace snprintf() with the safer scnprintf() variant (stable-fixes).\n- usb: cdnsp: do not disable slot for disabled slot (git-fixes).\n- usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume (git-fixes).\n- usb: common: usb-conn-gpio: use a unique name for usb connector device (stable-fixes).\n- usb: dwc2: also exit clock_gating when stopping udc while suspended (stable-fixes).\n- usb: dwc3: meson-g12a: fix device leaks at unbind (git-fixes).\n- usb: early: xhci-dbc: Fix early_ioremap leak (git-fixes).\n- usb: gadget : fix use-after-free in composite_dev_cleanup() (git-fixes).\n- usb: gadget: u_serial: Fix race condition in TTY wakeup (git-fixes).\n- usb: gadget: udc: renesas_usb3: fix device leak at unbind (git-fixes).\n- usb: host: xhci-plat: fix incorrect type for of_match variable in xhci_plat_probe() (git-fixes).\n- usb: hub: Do not try to recover devices lost during warm reset (git-fixes).\n- usb: misc: apple-mfi-fastcharge: Make power supply names unique (git-fixes).\n- usb: musb: fix gadget state on disconnect (git-fixes).\n- usb: musb: omap2430: fix device leak at unbind (git-fixes).\n- usb: net: sierra: check for no status endpoint (git-fixes).\n- usb: potential integer overflow in usbg_make_tpg() (stable-fixes).\n- usb: typec: Update sysfs when setting ops (git-fixes).\n- usb: typec: altmodes/displayport: do not index invalid pin_assignments (git-fixes).\n- usb: typec: displayport: Fix potential deadlock (git-fixes).\n- usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode (stable-fixes).\n- usb: typec: mux: do not return on EOPNOTSUPP in {mux, switch}_set (stable-fixes).\n- usb: typec: tcpm: allow switching to mode accessory to mux properly (stable-fixes).\n- usb: typec: tcpm: allow to use sink in accessory mode (stable-fixes).\n- usb: typec: tcpm: apply vbus before data bringup in tcpm_src_attach (git-fixes).\n- usb: typec: ucsi: Add DATA_RESET option of Connector Reset command (git-fixes).\n- usb: typec: ucsi: Add qcm6490-pmic-glink as needing PDOS quirk (git-fixes).\n- usb: typec: ucsi: Delay alternate mode discovery (git-fixes).\n- usb: typec: ucsi: Fix busy loop on ASUS VivoBooks (git-fixes).\n- usb: typec: ucsi: Fix the partner PD revision (git-fixes).\n- usb: typec: ucsi: Get PD revision for partner (git-fixes).\n- usb: typec: ucsi: Set orientation as none when connector is unplugged (git-fixes).\n- usb: typec: ucsi: Update power_supply on power role change (git-fixes).\n- usb: typec: ucsi: add callback for connector status updates (git-fixes).\n- usb: typec: ucsi: add update_connector callback (git-fixes).\n- usb: typec: ucsi: do not retrieve PDOs if not supported (git-fixes).\n- usb: typec: ucsi: extract code to read PD caps (git-fixes).\n- usb: typec: ucsi: fix UCSI on SM8550 \u0026 SM8650 Qualcomm devices (git-fixes).\n- usb: typec: ucsi: glink: fix off-by-one in connector_status (git-fixes).\n- usb: typec: ucsi: glink: increase max ports for x1e80100 (git-fixes).\n- usb: typec: ucsi: glink: move GPIO reading into connector_status callback (git-fixes).\n- usb: typec: ucsi: glink: use typec_set_orientation (git-fixes).\n- usb: typec: ucsi: move ucsi_acknowledge() from ucsi_read_error() (git-fixes).\n- usb: typec: ucsi: properly register partner's PD device (git-fixes).\n- usb: typec: ucsi: support delaying GET_PDOS for device (git-fixes).\n- usb: typec: ucsi_acpi: Add LG Gram quirk (git-fixes).\n- usb: typec: ucsi_glink: drop NO_PARTNER_PDOS quirk for sm8550 / sm8650 (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk (git-fixes).\n- usb: typec: ucsi_glink: enable the UCSI_DELAY_DEVICE_PDOS quirk on qcm6490 (git-fixes).\n- usb: typec: ucsi_glink: rework quirks implementation (git-fixes).\n- usb: xhci: Skip xhci_reset in xhci_resume if xhci is being removed (git-fixes).\n- usb: xhci: quirk for data loss in ISOC transfers (stable-fixes).\n- usb:cdnsp: remove TRB_FLUSH_ENDPOINT command (stable-fixes).\n- virtgpu: do not reset on shutdown (git-fixes).\n- vmci: Prevent the dispatching of uninitialized payloads (git-fixes).\n- vt: add missing notification when switching back to text mode (stable-fixes).\n- vt: defkeymap: Map keycodes above 127 to K_HOLE (git-fixes).\n- vt: keyboard: Do not process Unicode characters in K_OFF mode (git-fixes).\n- watchdog: ziirave_wdt: check record length in ziirave_firm_verify() (git-fixes).\n- wifi: ath11k: clear initialized flag for deinit-ed srng lists (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() (git-fixes).\n- wifi: ath11k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath11k: fix suspend use-after-free after probe failure (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption (git-fixes).\n- wifi: ath12k: fix dest ring-buffer corruption when ring is full (git-fixes).\n- wifi: ath12k: fix endianness handling while accessing wmi service bit (git-fixes).\n- wifi: ath12k: fix source ring-buffer corruption (git-fixes).\n- wifi: ath6kl: remove WARN on bad firmware input (stable-fixes).\n- wifi: brcmfmac: fix P2P discovery failure in P2P peer due to missing P2P IE (git-fixes).\n- wifi: brcmsmac: Remove const from tbl_ptr parameter in wlc_lcnphy_common_read_table() (git-fixes).\n- wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (git-fixes).\n- wifi: iwlwifi: Fix memory leak in iwl_mvm_init() (git-fixes).\n- wifi: iwlwifi: return ERR_PTR from opmode start() (stable-fixes).\n- wifi: mac80211: Add link iteration macro for link data (stable-fixes).\n- wifi: mac80211: Check 802.11 encaps offloading in ieee80211_tx_h_select_key() (git-fixes).\n- wifi: mac80211: Do not call fq_flow_idx() for management frames (git-fixes).\n- wifi: mac80211: Do not schedule stopped TXQs (git-fixes).\n- wifi: mac80211: chan: chandef is non-NULL for reserved (stable-fixes).\n- wifi: mac80211: drop invalid source address OCB frames (stable-fixes).\n- wifi: mac80211: reject TDLS operations when station is not associated (git-fixes).\n- wifi: mt76: mt7925: Fix null-ptr-deref in mt7925_thermal_init() (git-fixes).\n- wifi: mt76: mt7925: fix invalid array index in ssid assignment during hw scan (git-fixes).\n- wifi: mt76: mt7925: fix the wrong config for tx interrupt (git-fixes).\n- wifi: plfxlc: Fix error handling in usb driver probe (git-fixes).\n- wifi: prevent A-MSDU attacks in mesh networks (stable-fixes).\n- wifi: rtl818x: Kill URBs before clearing tx status queue (git-fixes).\n- wifi: rtw89: avoid NULL dereference when RX problematic packet on unsupported 6 GHz band (git-fixes).\n- wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() (git-fixes).\n- x86/cpu/amd: Fix workaround for erratum 1054 (git-fixes).\n- x86/mce/amd: Add default names for MCA banks and blocks (git-fixes).\n- x86/mce/amd: Fix threshold limit reset (git-fixes).\n- x86/mce: Do not remove sysfs if thresholding sysfs init fails (git-fixes).\n- x86/mce: Make sure CMCI banks are cleared during shutdown on Intel (git-fixes).\n- x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).\n- x86/traps: Initialize DR6 by writing its architectural reset value (git-fixes).\n- x86/virt/tdx: Avoid indirect calls to TDX assembly functions (git-fixes).\n- x86: UV RTC: Add parameter to disable RTC clocksource (bsc#1241345).\n- xfs: fix off-by-one error in fsmap's end_daddr usage (bsc#1235837).\n- xfs: only create event xfs_file_compat_ioctl when CONFIG_COMPAT is configure (git-fixes).\n- xfs: remove unused event xfs_alloc_near_error (git-fixes).\n- xfs: remove unused event xfs_alloc_near_nominleft (git-fixes).\n- xfs: remove unused event xfs_attr_node_removename (git-fixes).\n- xfs: remove unused event xfs_ioctl_clone (git-fixes).\n- xfs: remove unused event xfs_pagecache_inval (git-fixes).\n- xfs: remove unused event xlog_iclog_want_sync (git-fixes).\n- xfs: remove unused trace event xfs_attr_remove_iter_return (git-fixes).\n- xfs: remove unused trace event xfs_attr_rmtval_set (git-fixes).\n- xfs: remove unused trace event xfs_reflink_cow_enospc (git-fixes).\n- xfs: remove unused xfs_attr events (git-fixes).\n- xfs: remove unused xfs_reflink_compare_extents events (git-fixes).\n- xfs: remove usused xfs_end_io_direct events (git-fixes).\n- xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS (git-fixes).\n- xhci: dbc: Flush queued requests before stopping dbc (git-fixes).\n- xhci: dbctty: disable ECHO flag by default (git-fixes).\n","status":"published","published":"2025-08-25T13:32:36Z","modified":"2026-03-23T04:49:01.396914Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"USN-7769-1","title":"linux, linux-aws, linux-gcp, linux-gcp-6.14, linux-oracle, linux-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38122, CVE-2025-38119, CVE-2025-38071, CVE-2025-38310,\nCVE-2025-38166, CVE-2025-38055, CVE-2025-38292, CVE-2025-38078,\nCVE-2025-38134, CVE-2025-38063, CVE-2025-38282, CVE-2025-38059,\nCVE-2025-38112, CVE-2025-38082, CVE-2025-38296, CVE-2025-38126,\nCVE-2025-38136, CVE-2025-38075, CVE-2025-38042, CVE-2025-38113,\nCVE-2025-38003, CVE-2025-38318, CVE-2025-38156, CVE-2025-38290,\nCVE-2025-38102, CVE-2025-38076, CVE-2025-38097, CVE-2025-38313,\nCVE-2025-38298, CVE-2025-38300, CVE-2025-38169, CVE-2025-38131,\nCVE-2025-38301, CVE-2025-38050, CVE-2025-38139, CVE-2025-38305,\nCVE-2025-38317, CVE-2025-38045, CVE-2025-38040, CVE-2025-38279,\nCVE-2025-38123, CVE-2025-38074, CVE-2025-38111, CVE-2025-38117,\nCVE-2025-38069, CVE-2025-38035, CVE-2025-38128, CVE-2025-38277,\nCVE-2025-38061, CVE-2025-38306, CVE-2025-38051, CVE-2025-38124,\nCVE-2025-38291, CVE-2025-38130, CVE-2025-38319, CVE-2025-38272,\nCVE-2025-38175, CVE-2025-38176, CVE-2025-38070, CVE-2025-38032,\nCVE-2025-38151, CVE-2025-38107, CVE-2025-38103, CVE-2025-38274,\nCVE-2025-38163, CVE-2025-38293, CVE-2025-38064, CVE-2025-38498,\nCVE-2025-38039, CVE-2025-38173, CVE-2025-38038, CVE-2025-38135,\nCVE-2025-38149, CVE-2025-38142, CVE-2025-38414, CVE-2025-38120,\nCVE-2025-38106, CVE-2025-38092, CVE-2025-38091, CVE-2025-38415,\nCVE-2025-38294, CVE-2025-38043, CVE-2025-38147, CVE-2025-38037,\nCVE-2025-38108, CVE-2025-38088, CVE-2025-38316, CVE-2025-38312,\nCVE-2025-38352, CVE-2025-38115, CVE-2025-38161, CVE-2025-38036,\nCVE-2025-38275, CVE-2025-38098, CVE-2025-38132, CVE-2025-38146,\nCVE-2025-38288, CVE-2025-38143, CVE-2025-38278, CVE-2025-38155,\nCVE-2025-38047, CVE-2025-38160, CVE-2025-38053, CVE-2025-38072,\nCVE-2025-38140, CVE-2025-38141, CVE-2025-38068, CVE-2025-38058,\nCVE-2025-38062, CVE-2025-38303, CVE-2025-38164, CVE-2025-38101,\nCVE-2025-38145, CVE-2025-38105, CVE-2025-38295, CVE-2025-38284,\nCVE-2025-38137, CVE-2025-38073, CVE-2025-38269, CVE-2025-38118,\nCVE-2025-38165, CVE-2025-38162, CVE-2025-38170, CVE-2025-38114,\nCVE-2025-38066, CVE-2025-38116, CVE-2025-38315, CVE-2025-38153,\nCVE-2025-38031, CVE-2025-38041, CVE-2025-38168, CVE-2025-38499,\nCVE-2025-38048, CVE-2025-38158, CVE-2025-38060, CVE-2025-38299,\nCVE-2025-38286, CVE-2025-38125, CVE-2025-38297, CVE-2025-38270,\nCVE-2025-38044, CVE-2025-38080, CVE-2025-38096, CVE-2025-38314,\nCVE-2025-38307, CVE-2025-38174, CVE-2025-38267, CVE-2025-38304,\nCVE-2025-38057, CVE-2025-38065, CVE-2025-38311, CVE-2025-38302,\nCVE-2025-38138, CVE-2025-38033, CVE-2025-38079, CVE-2025-38280,\nCVE-2025-38109, CVE-2025-38287, CVE-2025-38159, CVE-2025-38289,\nCVE-2025-38283, CVE-2025-38081, CVE-2025-38172, CVE-2025-38148,\nCVE-2025-38285, CVE-2025-38034, CVE-2025-38154, CVE-2025-38077,\nCVE-2025-38054, CVE-2025-38029, CVE-2025-38127, CVE-2025-38281,\nCVE-2025-38100, CVE-2025-38129, CVE-2025-38004, CVE-2025-38099,\nCVE-2025-38157, CVE-2025-38067, CVE-2025-38265, CVE-2025-38052,\nCVE-2025-38110, CVE-2025-38268, CVE-2025-38167)\n","status":"published","published":"2025-12-03T09:21:48Z","modified":"2026-11-03T14:33:46.773726354Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7769-2","title":"linux-realtime-6.14 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38112, CVE-2025-38283, CVE-2025-38120, CVE-2025-38091,\nCVE-2025-38124, CVE-2025-38031, CVE-2025-38288, CVE-2025-38047,\nCVE-2025-38295, CVE-2025-38284, CVE-2025-38281, CVE-2025-38151,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38299, CVE-2025-38065,\nCVE-2025-38107, CVE-2025-38143, CVE-2025-38113, CVE-2025-38289,\nCVE-2025-38160, CVE-2025-38311, CVE-2025-38052, CVE-2025-38131,\nCVE-2025-38268, CVE-2025-38066, CVE-2025-38129, CVE-2025-38127,\nCVE-2025-38317, CVE-2025-38158, CVE-2025-38039, CVE-2025-38064,\nCVE-2025-38306, CVE-2025-38291, CVE-2025-38162, CVE-2025-38111,\nCVE-2025-38147, CVE-2025-38415, CVE-2025-38290, CVE-2025-38294,\nCVE-2025-38499, CVE-2025-38167, CVE-2025-38098, CVE-2025-38298,\nCVE-2025-38279, CVE-2025-38278, CVE-2025-38149, CVE-2025-38073,\nCVE-2025-38100, CVE-2025-38033, CVE-2025-38080, CVE-2025-38314,\nCVE-2025-38166, CVE-2025-38154, CVE-2025-38050, CVE-2025-38123,\nCVE-2025-38070, CVE-2025-38169, CVE-2025-38077, CVE-2025-38082,\nCVE-2025-38061, CVE-2025-38032, CVE-2025-38092, CVE-2025-38176,\nCVE-2025-38044, CVE-2025-38277, CVE-2025-38305, CVE-2025-38034,\nCVE-2025-38293, CVE-2025-38115, CVE-2025-38057, CVE-2025-38126,\nCVE-2025-38312, CVE-2025-38117, CVE-2025-38141, CVE-2025-38155,\nCVE-2025-38161, CVE-2025-38142, CVE-2025-38036, CVE-2025-38165,\nCVE-2025-38069, CVE-2025-38106, CVE-2025-38267, CVE-2025-38138,\nCVE-2025-38119, CVE-2025-38282, CVE-2025-38275, CVE-2025-38081,\nCVE-2025-38414, CVE-2025-38313, CVE-2025-38307, CVE-2025-38076,\nCVE-2025-38130, CVE-2025-38301, CVE-2025-38062, CVE-2025-38003,\nCVE-2025-38285, CVE-2025-38265, CVE-2025-38302, CVE-2025-38272,\nCVE-2025-38270, CVE-2025-38274, CVE-2025-38139, CVE-2025-38103,\nCVE-2025-38063, CVE-2025-38045, CVE-2025-38055, CVE-2025-38136,\nCVE-2025-38145, CVE-2025-38304, CVE-2025-38310, CVE-2025-38498,\nCVE-2025-38292, CVE-2025-38053, CVE-2025-38157, CVE-2025-38079,\nCVE-2025-38075, CVE-2025-38128, CVE-2025-38318, CVE-2025-38071,\nCVE-2025-38175, CVE-2025-38088, CVE-2025-38043, CVE-2025-38137,\nCVE-2025-38170, CVE-2025-38352, CVE-2025-38164, CVE-2025-38135,\nCVE-2025-38042, CVE-2025-38173, CVE-2025-38114, CVE-2025-38072,\nCVE-2025-38051, CVE-2025-38110, CVE-2025-38078, CVE-2025-38118,\nCVE-2025-38300, CVE-2025-38029, CVE-2025-38174, CVE-2025-38074,\nCVE-2025-38163, CVE-2025-38132, CVE-2025-38108, CVE-2025-38038,\nCVE-2025-38122, CVE-2025-38280, CVE-2025-38004, CVE-2025-38097,\nCVE-2025-38296, CVE-2025-38159, CVE-2025-38125, CVE-2025-38140,\nCVE-2025-38040, CVE-2025-38146, CVE-2025-38041, CVE-2025-38054,\nCVE-2025-38172, CVE-2025-38286, CVE-2025-38156, CVE-2025-38269,\nCVE-2025-38287, CVE-2025-38116, CVE-2025-38148, CVE-2025-38105,\nCVE-2025-38297, CVE-2025-38060, CVE-2025-38035, CVE-2025-38319,\nCVE-2025-38101, CVE-2025-38109, CVE-2025-38067, CVE-2025-38153,\nCVE-2025-38303, CVE-2025-38099, CVE-2025-38048, CVE-2025-38134,\nCVE-2025-38037, CVE-2025-38316, CVE-2025-38068, CVE-2025-38096,\nCVE-2025-38168, CVE-2025-38315, CVE-2025-38102)\n","status":"published","published":"2025-09-24T15:20:53Z","modified":"2026-11-03T14:33:50.166389004Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7769-3","title":"linux-aws-6.14, linux-hwe-6.14 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38115, CVE-2025-38004, CVE-2025-38035, CVE-2025-38057,\nCVE-2025-38314, CVE-2025-38317, CVE-2025-38074, CVE-2025-38113,\nCVE-2025-38130, CVE-2025-38175, CVE-2025-38155, CVE-2025-38062,\nCVE-2025-38050, CVE-2025-38159, CVE-2025-38352, CVE-2025-38101,\nCVE-2025-38034, CVE-2025-38061, CVE-2025-38288, CVE-2025-38153,\nCVE-2025-38043, CVE-2025-38268, CVE-2025-38415, CVE-2025-38291,\nCVE-2025-38270, CVE-2025-38044, CVE-2025-38146, CVE-2025-38048,\nCVE-2025-38069, CVE-2025-38298, CVE-2025-38058, CVE-2025-38161,\nCVE-2025-38158, CVE-2025-38059, CVE-2025-38066, CVE-2025-38047,\nCVE-2025-38040, CVE-2025-38112, CVE-2025-38042, CVE-2025-38107,\nCVE-2025-38296, CVE-2025-38278, CVE-2025-39890, CVE-2025-38088,\nCVE-2025-38174, CVE-2025-38118, CVE-2025-38117, CVE-2025-38110,\nCVE-2025-38305, CVE-2025-38136, CVE-2025-38063, CVE-2025-38498,\nCVE-2025-38499, CVE-2025-38106, CVE-2025-38292, CVE-2025-38163,\nCVE-2025-38169, CVE-2025-38032, CVE-2025-38310, CVE-2025-38302,\nCVE-2025-38092, CVE-2025-38052, CVE-2025-38282, CVE-2025-38082,\nCVE-2025-38036, CVE-2025-38054, CVE-2025-38105, CVE-2025-38265,\nCVE-2025-38116, CVE-2025-38060, CVE-2025-38154, CVE-2025-38280,\nCVE-2025-38176, CVE-2025-38156, CVE-2025-38289, CVE-2025-38166,\nCVE-2025-38080, CVE-2025-38098, CVE-2025-38127, CVE-2025-38125,\nCVE-2025-38172, CVE-2025-38142, CVE-2025-38096, CVE-2025-38055,\nCVE-2025-38138, CVE-2025-38126, CVE-2025-38073, CVE-2025-38173,\nCVE-2025-38031, CVE-2025-38128, CVE-2025-38064, CVE-2025-38071,\nCVE-2025-38099, CVE-2025-38316, CVE-2025-38119, CVE-2025-38108,\nCVE-2025-38079, CVE-2025-38301, CVE-2025-38122, CVE-2025-38269,\nCVE-2025-38300, CVE-2025-38097, CVE-2025-38318, CVE-2025-38100,\nCVE-2025-38045, CVE-2025-38053, CVE-2025-38124, CVE-2025-38295,\nCVE-2025-38078, CVE-2025-38037, CVE-2025-38135, CVE-2025-38165,\nCVE-2025-38294, CVE-2025-38132, CVE-2025-38065, CVE-2025-38281,\nCVE-2025-38145, CVE-2025-38311, CVE-2025-38075, CVE-2025-38033,\nCVE-2025-38275, CVE-2025-38319, CVE-2025-38081, CVE-2025-38279,\nCVE-2025-38076, CVE-2025-38077, CVE-2025-38068, CVE-2025-38148,\nCVE-2025-38313, CVE-2025-38134, CVE-2025-38143, CVE-2025-38102,\nCVE-2025-38131, CVE-2025-38283, CVE-2025-38151, CVE-2025-38111,\nCVE-2025-38029, CVE-2025-38141, CVE-2025-38277, CVE-2025-38414,\nCVE-2025-38147, CVE-2025-38167, CVE-2025-38286, CVE-2025-38315,\nCVE-2025-38103, CVE-2025-38303, CVE-2025-38123, CVE-2025-38129,\nCVE-2025-38164, CVE-2025-38157, CVE-2025-38306, CVE-2025-38299,\nCVE-2025-38307, CVE-2025-38091, CVE-2025-38304, CVE-2025-38149,\nCVE-2025-38170, CVE-2025-38137, CVE-2025-38293, CVE-2025-38070,\nCVE-2025-38120, CVE-2025-38290, CVE-2025-38003, CVE-2025-38160,\nCVE-2025-38039, CVE-2025-38139, CVE-2025-38114, CVE-2025-38041,\nCVE-2025-38038, CVE-2025-38168, CVE-2025-38274, CVE-2025-38051,\nCVE-2025-38072, CVE-2025-38287, CVE-2025-38067, CVE-2025-38285,\nCVE-2025-38284, CVE-2025-38312, CVE-2025-38109, CVE-2025-38272,\nCVE-2025-38140, CVE-2025-38162, CVE-2025-38267, CVE-2025-38297)\n","status":"published","published":"2025-09-26T07:47:41Z","modified":"2026-11-03T14:32:34.629975375Z","updated_at":"2026-11-03T14:35:23.570529Z"},{"id":"USN-7770-1","title":"linux-azure vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38155, CVE-2025-38145, CVE-2025-38072, CVE-2025-38306,\nCVE-2025-38004, CVE-2025-38053, CVE-2025-38293, CVE-2025-38045,\nCVE-2025-38105, CVE-2025-38079, CVE-2025-38161, CVE-2025-38031,\nCVE-2025-38114, CVE-2025-38033, CVE-2025-38274, CVE-2025-38265,\nCVE-2025-38135, CVE-2025-38075, CVE-2025-38313, CVE-2025-38064,\nCVE-2025-38118, CVE-2025-38299, CVE-2025-38123, CVE-2025-38112,\nCVE-2025-38073, CVE-2025-38070, CVE-2025-38138, CVE-2025-38303,\nCVE-2025-38148, CVE-2025-38035, CVE-2025-38157, CVE-2025-38131,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38071, CVE-2025-38081,\nCVE-2025-38301, CVE-2025-38415, CVE-2025-38034, CVE-2025-38294,\nCVE-2025-38314, CVE-2025-38285, CVE-2025-38147, CVE-2025-38113,\nCVE-2025-38352, CVE-2025-38170, CVE-2025-38103, CVE-2025-38282,\nCVE-2025-38290, CVE-2025-38117, CVE-2025-38078, CVE-2025-38122,\nCVE-2025-38176, CVE-2025-38082, CVE-2025-38289, CVE-2025-38124,\nCVE-2025-38039, CVE-2025-38281, CVE-2025-38126, CVE-2025-38111,\nCVE-2025-38080, CVE-2025-38088, CVE-2025-38048, CVE-2025-38269,\nCVE-2025-38003, CVE-2025-38102, CVE-2025-38140, CVE-2025-38316,\nCVE-2025-38268, CVE-2025-38132, CVE-2025-38286, CVE-2025-38159,\nCVE-2025-38120, CVE-2025-38295, CVE-2025-38077, CVE-2025-38297,\nCVE-2025-38174, CVE-2025-38160, CVE-2025-38119, CVE-2025-38099,\nCVE-2025-38134, CVE-2025-38051, CVE-2025-38061, CVE-2025-38317,\nCVE-2025-38142, CVE-2025-38175, CVE-2025-38091, CVE-2025-38311,\nCVE-2025-38066, CVE-2025-38062, CVE-2025-38169, CVE-2025-38065,\nCVE-2025-38098, CVE-2025-38146, CVE-2025-38292, CVE-2025-38040,\nCVE-2025-38096, CVE-2025-38115, CVE-2025-38047, CVE-2025-38067,\nCVE-2025-38270, CVE-2025-38074, CVE-2025-38129, CVE-2025-38143,\nCVE-2025-38498, CVE-2025-38125, CVE-2025-38092, CVE-2025-38149,\nCVE-2025-38287, CVE-2025-38057, CVE-2025-38307, CVE-2025-38037,\nCVE-2025-38162, CVE-2025-38141, CVE-2025-38068, CVE-2025-38029,\nCVE-2025-38101, CVE-2025-38059, CVE-2025-38300, CVE-2025-38283,\nCVE-2025-38272, CVE-2025-38042, CVE-2025-38100, CVE-2025-38044,\nCVE-2025-38284, CVE-2025-38063, CVE-2025-38043, CVE-2025-38151,\nCVE-2025-38158, CVE-2025-38168, CVE-2025-38278, CVE-2025-38166,\nCVE-2025-38499, CVE-2025-38116, CVE-2025-38128, CVE-2025-38060,\nCVE-2025-38291, CVE-2025-38304, CVE-2025-38172, CVE-2025-38052,\nCVE-2025-38312, CVE-2025-38319, CVE-2025-38136, CVE-2025-38267,\nCVE-2025-38154, CVE-2025-38296, CVE-2025-38130, CVE-2025-38097,\nCVE-2025-38275, CVE-2025-38106, CVE-2025-38156, CVE-2025-38137,\nCVE-2025-38153, CVE-2025-38167, CVE-2025-38315, CVE-2025-38032,\nCVE-2025-38350, CVE-2025-38173, CVE-2025-38139, CVE-2025-38110,\nCVE-2025-38318, CVE-2025-38163, CVE-2025-38058, CVE-2025-38280,\nCVE-2025-38036, CVE-2025-38041, CVE-2025-38302, CVE-2025-38038,\nCVE-2025-38310, CVE-2025-38076, CVE-2025-38164, CVE-2025-38414,\nCVE-2025-38277, CVE-2025-38069, CVE-2025-38288, CVE-2025-38165,\nCVE-2025-38279, CVE-2025-38305, CVE-2025-38054, CVE-2025-38127,\nCVE-2025-38055, CVE-2025-38050, CVE-2025-38298, CVE-2025-38109)\n","status":"published","published":"2025-09-24T13:30:11.58727Z","modified":"2026-02-04T02:53:36.117933Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-7771-1","title":"linux-oem-6.14 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38141, CVE-2025-38039, CVE-2025-38283, CVE-2025-38272,\nCVE-2025-38290, CVE-2025-38168, CVE-2025-38134, CVE-2025-38158,\nCVE-2025-38097, CVE-2025-38078, CVE-2025-38161, CVE-2025-38116,\nCVE-2025-38312, CVE-2025-38067, CVE-2025-38129, CVE-2025-38119,\nCVE-2025-38061, CVE-2025-38352, CVE-2025-38269, CVE-2025-38163,\nCVE-2025-38315, CVE-2025-38301, CVE-2025-38115, CVE-2025-38032,\nCVE-2025-38127, CVE-2025-38029, CVE-2025-38277, CVE-2025-38075,\nCVE-2025-38300, CVE-2025-38059, CVE-2025-38047, CVE-2025-38118,\nCVE-2025-38038, CVE-2025-38278, CVE-2025-38169, CVE-2025-38074,\nCVE-2025-38292, CVE-2025-38295, CVE-2025-38294, CVE-2025-38154,\nCVE-2025-38165, CVE-2025-38069, CVE-2025-38120, CVE-2025-38098,\nCVE-2025-38050, CVE-2025-38068, CVE-2025-38063, CVE-2025-38034,\nCVE-2025-38123, CVE-2025-38092, CVE-2025-38103, CVE-2025-38170,\nCVE-2025-38313, CVE-2025-38062, CVE-2025-38159, CVE-2025-38147,\nCVE-2025-38415, CVE-2025-38045, CVE-2025-38279, CVE-2025-38302,\nCVE-2025-38162, CVE-2025-38414, CVE-2025-38146, CVE-2025-38035,\nCVE-2025-38040, CVE-2025-38073, CVE-2025-38054, CVE-2025-38099,\nCVE-2025-38291, CVE-2025-38126, CVE-2025-38088, CVE-2025-38310,\nCVE-2025-38176, CVE-2025-38102, CVE-2025-38149, CVE-2025-38124,\nCVE-2025-38003, CVE-2025-38140, CVE-2025-38100, CVE-2025-38081,\nCVE-2025-38319, CVE-2025-38142, CVE-2025-38303, CVE-2025-38155,\nCVE-2025-38044, CVE-2025-38316, CVE-2025-38052, CVE-2025-38317,\nCVE-2025-38151, CVE-2025-38164, CVE-2025-38148, CVE-2025-38082,\nCVE-2025-38267, CVE-2025-38031, CVE-2025-38132, CVE-2025-38138,\nCVE-2025-38125, CVE-2025-38111, CVE-2025-38106, CVE-2025-38287,\nCVE-2025-38137, CVE-2025-38117, CVE-2025-38130, CVE-2025-38122,\nCVE-2025-38058, CVE-2025-38110, CVE-2025-38101, CVE-2025-38048,\nCVE-2025-38080, CVE-2025-38304, CVE-2025-38128, CVE-2025-38072,\nCVE-2025-38265, CVE-2025-38166, CVE-2025-38131, CVE-2025-38105,\nCVE-2025-38096, CVE-2025-38275, CVE-2025-38305, CVE-2025-38156,\nCVE-2025-38139, CVE-2025-38318, CVE-2025-38136, CVE-2025-38107,\nCVE-2025-38041, CVE-2025-38288, CVE-2025-38055, CVE-2025-38033,\nCVE-2025-38064, CVE-2025-38036, CVE-2025-38077, CVE-2025-38053,\nCVE-2025-38112, CVE-2025-38070, CVE-2025-38109, CVE-2025-38143,\nCVE-2025-38299, CVE-2025-38051, CVE-2025-38167, CVE-2025-38172,\nCVE-2025-38057, CVE-2025-38311, CVE-2025-38285, CVE-2025-38076,\nCVE-2025-38280, CVE-2025-38157, CVE-2025-38043, CVE-2025-38065,\nCVE-2025-38289, CVE-2025-38060, CVE-2025-38274, CVE-2025-38004,\nCVE-2025-38037, CVE-2025-38282, CVE-2025-38298, CVE-2025-38293,\nCVE-2025-38499, CVE-2025-38135, CVE-2025-38173, CVE-2025-38079,\nCVE-2025-38296, CVE-2025-38108, CVE-2025-38175, CVE-2025-38066,\nCVE-2025-38286, CVE-2025-38160, CVE-2025-38498, CVE-2025-38281,\nCVE-2025-38268, CVE-2025-38270, CVE-2025-38153, CVE-2025-38042,\nCVE-2025-38114, CVE-2025-38284, CVE-2025-38297, CVE-2025-38306,\nCVE-2025-38071, CVE-2025-38307, CVE-2025-38091, CVE-2025-38314,\nCVE-2025-38145, CVE-2025-38113)\n","status":"published","published":"2025-09-24T13:48:28Z","modified":"2026-11-03T14:33:47.318497822Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7789-1","title":"linux-oracle-6.14 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38137, CVE-2025-38141, CVE-2025-38035, CVE-2025-38298,\nCVE-2025-38042, CVE-2025-38140, CVE-2025-38138, CVE-2025-38316,\nCVE-2025-38304, CVE-2025-38165, CVE-2025-38306, CVE-2025-38082,\nCVE-2025-38132, CVE-2025-38498, CVE-2025-38158, CVE-2025-38154,\nCVE-2025-38064, CVE-2025-38129, CVE-2025-38096, CVE-2025-38352,\nCVE-2025-38303, CVE-2025-38122, CVE-2025-38048, CVE-2025-38296,\nCVE-2025-38149, CVE-2025-38319, CVE-2025-38078, CVE-2025-38066,\nCVE-2025-38099, CVE-2025-38291, CVE-2025-38267, CVE-2025-38268,\nCVE-2025-38126, CVE-2025-38076, CVE-2025-38077, CVE-2025-38101,\nCVE-2025-38071, CVE-2025-38163, CVE-2025-38285, CVE-2025-38265,\nCVE-2025-38125, CVE-2025-38302, CVE-2025-38172, CVE-2025-38292,\nCVE-2025-38279, CVE-2025-38170, CVE-2025-38062, CVE-2025-38074,\nCVE-2025-38050, CVE-2025-38116, CVE-2025-38414, CVE-2025-38173,\nCVE-2025-38033, CVE-2025-38112, CVE-2025-38091, CVE-2025-38290,\nCVE-2025-39890, CVE-2025-38156, CVE-2025-38289, CVE-2025-38275,\nCVE-2025-38295, CVE-2025-38123, CVE-2025-38300, CVE-2025-38067,\nCVE-2025-38131, CVE-2025-38294, CVE-2025-38105, CVE-2025-38107,\nCVE-2025-38106, CVE-2025-38069, CVE-2025-38041, CVE-2025-38111,\nCVE-2025-38312, CVE-2025-38092, CVE-2025-38054, CVE-2025-38166,\nCVE-2025-38044, CVE-2025-38159, CVE-2025-38061, CVE-2025-38115,\nCVE-2025-38058, CVE-2025-38036, CVE-2025-38100, CVE-2025-38075,\nCVE-2025-38160, CVE-2025-38102, CVE-2025-38269, CVE-2025-38108,\nCVE-2025-38119, CVE-2025-38052, CVE-2025-38175, CVE-2025-38103,\nCVE-2025-38286, CVE-2025-38051, CVE-2025-38004, CVE-2025-38283,\nCVE-2025-38118, CVE-2025-38139, CVE-2025-38079, CVE-2025-38315,\nCVE-2025-38145, CVE-2025-38072, CVE-2025-38045, CVE-2025-38117,\nCVE-2025-38143, CVE-2025-38068, CVE-2025-38053, CVE-2025-38081,\nCVE-2025-38032, CVE-2025-38134, CVE-2025-38063, CVE-2025-38128,\nCVE-2025-38278, CVE-2025-38270, CVE-2025-38060, CVE-2025-38161,\nCVE-2025-38073, CVE-2025-38065, CVE-2025-38313, CVE-2025-38148,\nCVE-2025-38124, CVE-2025-38305, CVE-2025-38146, CVE-2025-38047,\nCVE-2025-38055, CVE-2025-38169, CVE-2025-38120, CVE-2025-38164,\nCVE-2025-38070, CVE-2025-38176, CVE-2025-38282, CVE-2025-38288,\nCVE-2025-38274, CVE-2025-38113, CVE-2025-38174, CVE-2025-38301,\nCVE-2025-38293, CVE-2025-38136, CVE-2025-38311, CVE-2025-38039,\nCVE-2025-38297, CVE-2025-38155, CVE-2025-38307, CVE-2025-38147,\nCVE-2025-38043, CVE-2025-38109, CVE-2025-38281, CVE-2025-38280,\nCVE-2025-38127, CVE-2025-38057, CVE-2025-38029, CVE-2025-38038,\nCVE-2025-38167, CVE-2025-38151, CVE-2025-38415, CVE-2025-38317,\nCVE-2025-38031, CVE-2025-38162, CVE-2025-38098, CVE-2025-38130,\nCVE-2025-38114, CVE-2025-38142, CVE-2025-38135, CVE-2025-38299,\nCVE-2025-38272, CVE-2025-38277, CVE-2025-38037, CVE-2025-38088,\nCVE-2025-38287, CVE-2025-38168, CVE-2025-38003, CVE-2025-38284,\nCVE-2025-38499, CVE-2025-38097, CVE-2025-38318, CVE-2025-38059,\nCVE-2025-38040, CVE-2025-38314, CVE-2025-38110, CVE-2025-38157,\nCVE-2025-38153, CVE-2025-38080, CVE-2025-38034, CVE-2025-38310)\n","status":"published","published":"2025-10-01T13:59:22Z","modified":"2026-11-03T14:33:51.703344301Z","updated_at":"2026-11-03T15:17:23.859376Z"},{"id":"USN-7789-2","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Android drivers;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - VMware VMCI Driver;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - NI-700 PMU driver;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PTP clock framework;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - USB Gadget drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Port Controller Manager driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Virtio drivers;\n  - BTRFS file system;\n  - EROFS file system;\n  - F2FS file system;\n  - File systems infrastructure;\n  - Network file systems library;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Codetag library;\n  - BPF subsystem;\n  - LZO compression library;\n  - Mellanox drivers;\n  - IPv4 networking;\n  - Bluetooth subsystem;\n  - Network sockets;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Padata parallel execution mechanism;\n  - DVFS energy model driver;\n  - Restartable seuqences system call mechanism;\n  - Timer subsystem;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - CAN network layer;\n  - Networking core;\n  - IPv6 networking;\n  - Netfilter;\n  - NetLabel subsystem;\n  - Open vSwitch;\n  - Network traffic control;\n  - TIPC protocol;\n  - TLS protocol;\n  - ALSA framework;\n  - sma1307 audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - USB sound devices;\n(CVE-2025-38081, CVE-2025-38142, CVE-2025-38157, CVE-2025-38174,\nCVE-2025-38156, CVE-2025-38044, CVE-2025-38414, CVE-2025-38041,\nCVE-2025-38124, CVE-2025-38122, CVE-2025-38285, CVE-2025-38317,\nCVE-2025-38159, CVE-2025-38352, CVE-2025-38117, CVE-2025-38040,\nCVE-2025-38292, CVE-2025-38301, CVE-2025-38149, CVE-2025-38299,\nCVE-2025-38116, CVE-2025-38100, CVE-2025-38107, CVE-2025-38063,\nCVE-2025-38069, CVE-2025-38130, CVE-2025-38032, CVE-2025-38113,\nCVE-2025-38287, CVE-2025-38138, CVE-2025-38004, CVE-2025-38097,\nCVE-2025-38270, CVE-2025-38311, CVE-2025-38499, CVE-2025-38050,\nCVE-2025-38064, CVE-2025-38278, CVE-2025-38297, CVE-2025-38091,\nCVE-2025-38065, CVE-2025-38114, CVE-2025-38048, CVE-2025-38096,\nCVE-2025-38112, CVE-2025-38148, CVE-2025-38101, CVE-2025-38062,\nCVE-2025-38057, CVE-2025-38029, CVE-2025-38105, CVE-2025-38277,\nCVE-2025-38053, CVE-2025-38302, CVE-2025-38169, CVE-2025-38307,\nCVE-2025-38153, CVE-2025-38106, CVE-2025-38293, CVE-2025-38267,\nCVE-2025-38314, CVE-2025-38291, CVE-2025-38284, CVE-2025-38141,\nCVE-2025-38052, CVE-2025-38079, CVE-2025-38088, CVE-2025-38164,\nCVE-2025-38288, CVE-2025-38289, CVE-2025-38074, CVE-2025-38073,\nCVE-2025-38274, CVE-2025-38167, CVE-2025-38129, CVE-2025-38082,\nCVE-2025-38109, CVE-2025-38003, CVE-2025-38042, CVE-2025-38319,\nCVE-2025-38165, CVE-2025-38102, CVE-2025-38045, CVE-2025-38154,\nCVE-2025-38127, CVE-2025-38034, CVE-2025-38051, CVE-2025-38143,\nCVE-2025-38061, CVE-2025-38119, CVE-2025-38077, CVE-2025-38115,\nCVE-2025-38175, CVE-2025-38147, CVE-2025-38172, CVE-2025-38176,\nCVE-2025-38269, CVE-2025-38126, CVE-2025-38131, CVE-2025-38296,\nCVE-2025-38170, CVE-2025-38110, CVE-2025-38111, CVE-2025-38295,\nCVE-2025-38072, CVE-2025-38168, CVE-2025-38098, CVE-2025-38160,\nCVE-2025-38125, CVE-2025-38054, CVE-2025-38286, CVE-2025-38310,\nCVE-2025-38162, CVE-2025-38135, CVE-2025-38161, CVE-2025-38055,\nCVE-2025-38066, CVE-2025-38318, CVE-2025-38173, CVE-2025-38033,\nCVE-2025-38281, CVE-2025-38140, CVE-2025-38146, CVE-2025-38305,\nCVE-2025-38103, CVE-2025-38080, CVE-2025-38068, CVE-2025-38037,\nCVE-2025-38043, CVE-2025-38272, CVE-2025-38137, CVE-2025-38279,\nCVE-2025-38275, CVE-2025-38151, CVE-2025-38123, CVE-2025-38158,\nCVE-2025-38268, CVE-2025-38136, CVE-2025-38132, CVE-2025-38120,\nCVE-2025-38047, CVE-2025-38304, CVE-2025-38298, CVE-2025-38265,\nCVE-2025-38134, CVE-2025-38128, CVE-2025-38118, CVE-2025-38058,\nCVE-2025-38303, CVE-2025-38316, CVE-2025-38092, CVE-2025-38163,\nCVE-2025-38155, CVE-2025-38145, CVE-2025-38280, CVE-2025-38076,\nCVE-2025-38031, CVE-2025-38306, CVE-2025-38078, CVE-2025-38035,\nCVE-2025-38315, CVE-2025-38300, CVE-2025-38283, CVE-2025-38059,\nCVE-2025-38312, CVE-2025-38071, CVE-2025-38294, CVE-2025-38036,\nCVE-2025-38498, CVE-2025-38099, CVE-2025-38070, CVE-2025-38166,\nCVE-2025-38060, CVE-2025-38282, CVE-2025-38313, CVE-2025-38038,\nCVE-2025-38290, CVE-2025-39890, CVE-2025-38415, CVE-2025-38039,\nCVE-2025-38067, CVE-2025-38075, CVE-2025-38108, CVE-2025-38139)\n","status":"published","published":"2025-10-08T08:22:25.125024Z","modified":"2026-02-04T03:47:01.229416Z","updated_at":"2026-11-02T16:58:21.91885Z"},{"id":"USN-8028-1","title":"linux, linux-raspi vulnerabilities","description":"\nIt was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-11T16:39:10Z","modified":"2026-11-03T14:34:46.341804014Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8028-2","title":"linux-realtime-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-12T09:57:11Z","modified":"2026-11-03T14:34:35.34044986Z","updated_at":"2026-11-03T15:16:59.562266Z"},{"id":"USN-8028-3","title":"linux-realtime, linux-raspi-realtime vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-17T14:03:27Z","modified":"2026-11-03T14:34:45.712363126Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8028-4","title":"linux-aws-fips, linux-fips vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-17T14:41:16Z","modified":"2026-11-03T14:34:46.888176267Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8028-5","title":"linux-aws, linux-aws-6.8, linux-gkeop, linux-nvidia, linux-nvidia-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-17T15:38:25Z","modified":"2026-11-03T14:38:15.5301337Z","updated_at":"2026-11-03T15:14:17.286738Z"},{"id":"USN-8028-6","title":"linux-hwe-6.8, linux-lowlatency-hwe-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-19T09:01:52Z","modified":"2026-11-03T14:35:19.673991765Z","updated_at":"2026-11-03T15:16:22.507285Z"},{"id":"USN-8028-7","title":"linux-nvidia-lowlatency vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-19T12:29:23Z","modified":"2026-11-03T14:34:35.33102093Z","updated_at":"2026-11-03T15:16:59.562266Z"},{"id":"USN-8028-8","title":"linux-ibm, linux-ibm-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-24T18:36:08Z","modified":"2026-11-03T14:35:22.59799177Z","updated_at":"2026-11-03T15:16:18.473448Z"},{"id":"USN-8031-1","title":"linux-gcp-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38503, CVE-2025-38506, CVE-2025-38507,\nCVE-2025-38510, CVE-2025-38511, CVE-2025-38512, CVE-2025-38513,\nCVE-2025-38514, CVE-2025-38515, CVE-2025-38516, CVE-2025-38520,\nCVE-2025-38521, CVE-2025-38524, CVE-2025-38526, CVE-2025-38527,\nCVE-2025-38528, CVE-2025-38529, CVE-2025-38530, CVE-2025-38531,\nCVE-2025-38532, CVE-2025-38533, CVE-2025-38535, CVE-2025-38537,\nCVE-2025-38538, CVE-2025-38539, CVE-2025-38540, CVE-2025-38542,\nCVE-2025-38543, CVE-2025-38544, CVE-2025-38546, CVE-2025-38548,\nCVE-2025-38549, CVE-2025-38550, CVE-2025-38551, CVE-2025-38552,\nCVE-2025-38553, CVE-2025-38555, CVE-2025-38560, CVE-2025-38562,\nCVE-2025-38566, CVE-2025-38568, CVE-2025-38569, CVE-2025-38571,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38582,\nCVE-2025-38583, CVE-2025-38584, CVE-2025-38585, CVE-2025-38587,\nCVE-2025-38588, CVE-2025-38590, CVE-2025-38593, CVE-2025-38595,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38610, CVE-2025-38612, CVE-2025-38614,\nCVE-2025-38615, CVE-2025-38619, CVE-2025-38622, CVE-2025-38623,\nCVE-2025-38624, CVE-2025-38625, CVE-2025-38626, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38644, CVE-2025-38645, CVE-2025-38646,\nCVE-2025-38648, CVE-2025-38650, CVE-2025-38652, CVE-2025-38653,\nCVE-2025-38659, CVE-2025-38660, CVE-2025-38663, CVE-2025-38664,\nCVE-2025-38665, CVE-2025-38668, CVE-2025-38670, CVE-2025-38671,\nCVE-2025-38675, CVE-2025-38676, CVE-2025-38677, CVE-2025-38679,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38683, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38710, CVE-2025-38711,\nCVE-2025-38712, CVE-2025-38713, CVE-2025-38714, CVE-2025-38715,\nCVE-2025-38716, CVE-2025-38718, CVE-2025-38721, CVE-2025-38722,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38728, CVE-2025-38729,\nCVE-2025-38730, CVE-2025-38732, CVE-2025-38734, CVE-2025-38735,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39679,\nCVE-2025-39681, CVE-2025-39683, CVE-2025-39684, CVE-2025-39685,\nCVE-2025-39686, CVE-2025-39687, CVE-2025-39689, CVE-2025-39691,\nCVE-2025-39692, CVE-2025-39693, CVE-2025-39694, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39889, CVE-2025-39890,\nCVE-2025-39946, CVE-2025-39989, CVE-2025-40215, CVE-2025-40297,\nCVE-2025-68750)\n","status":"published","published":"2026-02-12T10:13:02Z","modified":"2026-11-03T14:34:33.889553261Z","updated_at":"2026-11-03T15:16:59.562266Z"},{"id":"USN-8031-2","title":"linux-gcp-fips vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38503, CVE-2025-38506, CVE-2025-38507,\nCVE-2025-38510, CVE-2025-38511, CVE-2025-38512, CVE-2025-38513,\nCVE-2025-38514, CVE-2025-38515, CVE-2025-38516, CVE-2025-38520,\nCVE-2025-38521, CVE-2025-38524, CVE-2025-38526, CVE-2025-38527,\nCVE-2025-38528, CVE-2025-38529, CVE-2025-38530, CVE-2025-38531,\nCVE-2025-38532, CVE-2025-38533, CVE-2025-38535, CVE-2025-38537,\nCVE-2025-38538, CVE-2025-38539, CVE-2025-38540, CVE-2025-38542,\nCVE-2025-38543, CVE-2025-38544, CVE-2025-38546, CVE-2025-38548,\nCVE-2025-38549, CVE-2025-38550, CVE-2025-38551, CVE-2025-38552,\nCVE-2025-38553, CVE-2025-38555, CVE-2025-38560, CVE-2025-38562,\nCVE-2025-38566, CVE-2025-38568, CVE-2025-38569, CVE-2025-38571,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38582,\nCVE-2025-38583, CVE-2025-38584, CVE-2025-38585, CVE-2025-38587,\nCVE-2025-38588, CVE-2025-38590, CVE-2025-38593, CVE-2025-38595,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38610, CVE-2025-38612, CVE-2025-38614,\nCVE-2025-38615, CVE-2025-38619, CVE-2025-38622, CVE-2025-38623,\nCVE-2025-38624, CVE-2025-38625, CVE-2025-38626, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38644, CVE-2025-38645, CVE-2025-38646,\nCVE-2025-38648, CVE-2025-38650, CVE-2025-38652, CVE-2025-38653,\nCVE-2025-38659, CVE-2025-38660, CVE-2025-38663, CVE-2025-38664,\nCVE-2025-38665, CVE-2025-38668, CVE-2025-38670, CVE-2025-38671,\nCVE-2025-38675, CVE-2025-38676, CVE-2025-38677, CVE-2025-38679,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38683, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38710, CVE-2025-38711,\nCVE-2025-38712, CVE-2025-38713, CVE-2025-38714, CVE-2025-38715,\nCVE-2025-38716, CVE-2025-38718, CVE-2025-38721, CVE-2025-38722,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38728, CVE-2025-38729,\nCVE-2025-38730, CVE-2025-38732, CVE-2025-38734, CVE-2025-38735,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39679,\nCVE-2025-39681, CVE-2025-39683, CVE-2025-39684, CVE-2025-39685,\nCVE-2025-39686, CVE-2025-39687, CVE-2025-39689, CVE-2025-39691,\nCVE-2025-39692, CVE-2025-39693, CVE-2025-39694, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39889, CVE-2025-39890,\nCVE-2025-39946, CVE-2025-39989, CVE-2025-40215, CVE-2025-40297,\nCVE-2025-68750)\n","status":"published","published":"2026-02-18T10:06:54Z","modified":"2026-11-03T14:34:34.813034883Z","updated_at":"2026-11-03T15:16:59.562266Z"},{"id":"USN-8031-3","title":"linux-gcp, linux-gke vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38503, CVE-2025-38506, CVE-2025-38507,\nCVE-2025-38510, CVE-2025-38511, CVE-2025-38512, CVE-2025-38513,\nCVE-2025-38514, CVE-2025-38515, CVE-2025-38516, CVE-2025-38520,\nCVE-2025-38521, CVE-2025-38524, CVE-2025-38526, CVE-2025-38527,\nCVE-2025-38528, CVE-2025-38529, CVE-2025-38530, CVE-2025-38531,\nCVE-2025-38532, CVE-2025-38533, CVE-2025-38535, CVE-2025-38537,\nCVE-2025-38538, CVE-2025-38539, CVE-2025-38540, CVE-2025-38542,\nCVE-2025-38543, CVE-2025-38544, CVE-2025-38546, CVE-2025-38548,\nCVE-2025-38549, CVE-2025-38550, CVE-2025-38551, CVE-2025-38552,\nCVE-2025-38553, CVE-2025-38555, CVE-2025-38560, CVE-2025-38562,\nCVE-2025-38566, CVE-2025-38568, CVE-2025-38569, CVE-2025-38571,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38582,\nCVE-2025-38583, CVE-2025-38584, CVE-2025-38585, CVE-2025-38587,\nCVE-2025-38588, CVE-2025-38590, CVE-2025-38593, CVE-2025-38595,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38610, CVE-2025-38612, CVE-2025-38614,\nCVE-2025-38615, CVE-2025-38619, CVE-2025-38622, CVE-2025-38623,\nCVE-2025-38624, CVE-2025-38625, CVE-2025-38626, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38644, CVE-2025-38645, CVE-2025-38646,\nCVE-2025-38648, CVE-2025-38650, CVE-2025-38652, CVE-2025-38653,\nCVE-2025-38659, CVE-2025-38660, CVE-2025-38663, CVE-2025-38664,\nCVE-2025-38665, CVE-2025-38668, CVE-2025-38670, CVE-2025-38671,\nCVE-2025-38675, CVE-2025-38676, CVE-2025-38677, CVE-2025-38679,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38683, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38710, CVE-2025-38711,\nCVE-2025-38712, CVE-2025-38713, CVE-2025-38714, CVE-2025-38715,\nCVE-2025-38716, CVE-2025-38718, CVE-2025-38721, CVE-2025-38722,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38728, CVE-2025-38729,\nCVE-2025-38730, CVE-2025-38732, CVE-2025-38734, CVE-2025-38735,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39679,\nCVE-2025-39681, CVE-2025-39683, CVE-2025-39684, CVE-2025-39685,\nCVE-2025-39686, CVE-2025-39687, CVE-2025-39689, CVE-2025-39691,\nCVE-2025-39692, CVE-2025-39693, CVE-2025-39694, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39889, CVE-2025-39890,\nCVE-2025-39946, CVE-2025-39989, CVE-2025-40215, CVE-2025-40297,\nCVE-2025-68750)\n","status":"published","published":"2026-02-19T09:26:23Z","modified":"2026-11-03T14:34:47.042824298Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8052-1","title":"linux-lowlatency vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-19T09:51:06Z","modified":"2026-11-03T14:35:12.915366191Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8052-2","title":"linux-xilinx vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-24T18:57:40Z","modified":"2026-11-03T14:35:11.403018594Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8074-1","title":"linux-azure vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37956, CVE-2025-37957,\nCVE-2025-37959, CVE-2025-37960, CVE-2025-37961, CVE-2025-37962,\nCVE-2025-37963, CVE-2025-37967, CVE-2025-37968, CVE-2025-37969,\nCVE-2025-37970, CVE-2025-37972, CVE-2025-37973, CVE-2025-37975,\nCVE-2025-37977, CVE-2025-37978, CVE-2025-37979, CVE-2025-37980,\nCVE-2025-37982, CVE-2025-37983, CVE-2025-37984, CVE-2025-37985,\nCVE-2025-37986, CVE-2025-37987, CVE-2025-37988, CVE-2025-37989,\nCVE-2025-37990, CVE-2025-37991, CVE-2025-37992, CVE-2025-37994,\nCVE-2025-37995, CVE-2025-37998, CVE-2025-38003, CVE-2025-38004,\nCVE-2025-38005, CVE-2025-38006, CVE-2025-38007, CVE-2025-38008,\nCVE-2025-38009, CVE-2025-38010, CVE-2025-38011, CVE-2025-38013,\nCVE-2025-38014, CVE-2025-38015, CVE-2025-38018, CVE-2025-38019,\nCVE-2025-38020, CVE-2025-38023, CVE-2025-38024, CVE-2025-38027,\nCVE-2025-38031, CVE-2025-38034, CVE-2025-38035, CVE-2025-38037,\nCVE-2025-38039, CVE-2025-38040, CVE-2025-38043, CVE-2025-38044,\nCVE-2025-38045, CVE-2025-38048, CVE-2025-38051, CVE-2025-38052,\nCVE-2025-38053, CVE-2025-38055, CVE-2025-38057, CVE-2025-38058,\nCVE-2025-38059, CVE-2025-38060, CVE-2025-38061, CVE-2025-38062,\nCVE-2025-38063, CVE-2025-38065, CVE-2025-38066, CVE-2025-38067,\nCVE-2025-38068, CVE-2025-38071, CVE-2025-38072, CVE-2025-38074,\nCVE-2025-38075, CVE-2025-38077, CVE-2025-38078, CVE-2025-38079,\nCVE-2025-38080, CVE-2025-38081, CVE-2025-38084, CVE-2025-38085,\nCVE-2025-38086, CVE-2025-38087, CVE-2025-38088, CVE-2025-38089,\nCVE-2025-38090, CVE-2025-38094, CVE-2025-38095, CVE-2025-38097,\nCVE-2025-38098, CVE-2025-38099, CVE-2025-38100, CVE-2025-38101,\nCVE-2025-38102, CVE-2025-38103, CVE-2025-38104, CVE-2025-38107,\nCVE-2025-38108, CVE-2025-38109, CVE-2025-38110, CVE-2025-38111,\nCVE-2025-38112, CVE-2025-38113, CVE-2025-38115, CVE-2025-38117,\nCVE-2025-38119, CVE-2025-38120, CVE-2025-38122, CVE-2025-38123,\nCVE-2025-38124, CVE-2025-38125, CVE-2025-38126, CVE-2025-38127,\nCVE-2025-38129, CVE-2025-38131, CVE-2025-38135, CVE-2025-38136,\nCVE-2025-38138, CVE-2025-38142, CVE-2025-38143, CVE-2025-38145,\nCVE-2025-38146, CVE-2025-38147, CVE-2025-38148, CVE-2025-38149,\nCVE-2025-38153, CVE-2025-38154, CVE-2025-38155, CVE-2025-38156,\nCVE-2025-38157, CVE-2025-38158, CVE-2025-38159, CVE-2025-38160,\nCVE-2025-38161, CVE-2025-38162, CVE-2025-38163, CVE-2025-38164,\nCVE-2025-38165, CVE-2025-38166, CVE-2025-38167, CVE-2025-38169,\nCVE-2025-38170, CVE-2025-38173, CVE-2025-38174, CVE-2025-38180,\nCVE-2025-38181, CVE-2025-38182, CVE-2025-38183, CVE-2025-38184,\nCVE-2025-38185, CVE-2025-38190, CVE-2025-38191, CVE-2025-38192,\nCVE-2025-38193, CVE-2025-38194, CVE-2025-38197, CVE-2025-38198,\nCVE-2025-38200, CVE-2025-38202, CVE-2025-38208, CVE-2025-38210,\nCVE-2025-38211, CVE-2025-38212, CVE-2025-38214, CVE-2025-38215,\nCVE-2025-38217, CVE-2025-38218, CVE-2025-38219, CVE-2025-38220,\nCVE-2025-38222, CVE-2025-38225, CVE-2025-38226, CVE-2025-38229,\nCVE-2025-38230, CVE-2025-38231, CVE-2025-38232, CVE-2025-38236,\nCVE-2025-38239, CVE-2025-38245, CVE-2025-38246, CVE-2025-38248,\nCVE-2025-38249, CVE-2025-38250, CVE-2025-38251, CVE-2025-38253,\nCVE-2025-38255, CVE-2025-38257, CVE-2025-38258, CVE-2025-38259,\nCVE-2025-38260, CVE-2025-38262, CVE-2025-38263, CVE-2025-38264,\nCVE-2025-38265, CVE-2025-38269, CVE-2025-38274, CVE-2025-38275,\nCVE-2025-38277, CVE-2025-38278, CVE-2025-38279, CVE-2025-38280,\nCVE-2025-38282, CVE-2025-38283, CVE-2025-38285, CVE-2025-38286,\nCVE-2025-38289, CVE-2025-38290, CVE-2025-38292, CVE-2025-38293,\nCVE-2025-38295, CVE-2025-38298, CVE-2025-38299, CVE-2025-38300,\nCVE-2025-38303, CVE-2025-38304, CVE-2025-38305, CVE-2025-38307,\nCVE-2025-38310, CVE-2025-38312, CVE-2025-38313, CVE-2025-38319,\nCVE-2025-38320, CVE-2025-38321, CVE-2025-38322, CVE-2025-38323,\nCVE-2025-38324, CVE-2025-38326, CVE-2025-38328, CVE-2025-38331,\nCVE-2025-38332, CVE-2025-38333, CVE-2025-38334, CVE-2025-38335,\nCVE-2025-38336, CVE-2025-38337, CVE-2025-38338, CVE-2025-38342,\nCVE-2025-38343, CVE-2025-38344, CVE-2025-38345, CVE-2025-38346,\nCVE-2025-38347, CVE-2025-38348, CVE-2025-38349, CVE-2025-38351,\nCVE-2025-38354, CVE-2025-38361, CVE-2025-38362, CVE-2025-38363,\nCVE-2025-38364, CVE-2025-38365, CVE-2025-38368, CVE-2025-38369,\nCVE-2025-38371, CVE-2025-38373, CVE-2025-38374, CVE-2025-38375,\nCVE-2025-38376, CVE-2025-38377, CVE-2025-38382, CVE-2025-38384,\nCVE-2025-38385, CVE-2025-38386, CVE-2025-38387, CVE-2025-38388,\nCVE-2025-38389, CVE-2025-38390, CVE-2025-38391, CVE-2025-38392,\nCVE-2025-38393, CVE-2025-38395, CVE-2025-38396, CVE-2025-38399,\nCVE-2025-38400, CVE-2025-38401, CVE-2025-38402, CVE-2025-38403,\nCVE-2025-38405, CVE-2025-38406, CVE-2025-38407, CVE-2025-38408,\nCVE-2025-38409, CVE-2025-38410, CVE-2025-38412, CVE-2025-38414,\nCVE-2025-38415, CVE-2025-38416, CVE-2025-38418, CVE-2025-38419,\nCVE-2025-38420, CVE-2025-38422, CVE-2025-38424, CVE-2025-38425,\nCVE-2025-38427, CVE-2025-38428, CVE-2025-38429, CVE-2025-38430,\nCVE-2025-38436, CVE-2025-38437, CVE-2025-38439, CVE-2025-38441,\nCVE-2025-38443, CVE-2025-38444, CVE-2025-38445, CVE-2025-38448,\nCVE-2025-38449, CVE-2025-38455, CVE-2025-38456, CVE-2025-38457,\nCVE-2025-38458, CVE-2025-38459, CVE-2025-38460, CVE-2025-38461,\nCVE-2025-38462, CVE-2025-38463, CVE-2025-38464, CVE-2025-38465,\nCVE-2025-38466, CVE-2025-38467, CVE-2025-38468, CVE-2025-38469,\nCVE-2025-38470, CVE-2025-38471, CVE-2025-38472, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38485,\nCVE-2025-38487, CVE-2025-38488, CVE-2025-38489, CVE-2025-38490,\nCVE-2025-38491, CVE-2025-38493, CVE-2025-38494, CVE-2025-38495,\nCVE-2025-38496, CVE-2025-38497, CVE-2025-38499, CVE-2025-38501,\nCVE-2025-38503, CVE-2025-38506, CVE-2025-38507, CVE-2025-38510,\nCVE-2025-38511, CVE-2025-38512, CVE-2025-38513, CVE-2025-38514,\nCVE-2025-38515, CVE-2025-38516, CVE-2025-38520, CVE-2025-38521,\nCVE-2025-38524, CVE-2025-38526, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38531, CVE-2025-38532,\nCVE-2025-38533, CVE-2025-38535, CVE-2025-38537, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38540, CVE-2025-38542, CVE-2025-38543,\nCVE-2025-38544, CVE-2025-38546, CVE-2025-38548, CVE-2025-38549,\nCVE-2025-38550, CVE-2025-38551, CVE-2025-38552, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38560, CVE-2025-38561, CVE-2025-38562,\nCVE-2025-38566, CVE-2025-38568, CVE-2025-38569, CVE-2025-38571,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38582,\nCVE-2025-38583, CVE-2025-38584, CVE-2025-38585, CVE-2025-38587,\nCVE-2025-38588, CVE-2025-38590, CVE-2025-38593, CVE-2025-38595,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38610, CVE-2025-38612, CVE-2025-38614,\nCVE-2025-38615, CVE-2025-38619, CVE-2025-38622, CVE-2025-38623,\nCVE-2025-38624, CVE-2025-38625, CVE-2025-38626, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38644, CVE-2025-38645, CVE-2025-38646,\nCVE-2025-38648, CVE-2025-38650, CVE-2025-38652, CVE-2025-38653,\nCVE-2025-38659, CVE-2025-38660, CVE-2025-38663, CVE-2025-38664,\nCVE-2025-38665, CVE-2025-38668, CVE-2025-38670, CVE-2025-38671,\nCVE-2025-38675, CVE-2025-38676, CVE-2025-38677, CVE-2025-38679,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38684, CVE-2025-38685,\nCVE-2025-38686, CVE-2025-38687, CVE-2025-38688, CVE-2025-38691,\nCVE-2025-38692, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38702, CVE-2025-38703,\nCVE-2025-38704, CVE-2025-38705, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38710, CVE-2025-38711, CVE-2025-38712,\nCVE-2025-38713, CVE-2025-38714, CVE-2025-38715, CVE-2025-38716,\nCVE-2025-38718, CVE-2025-38721, CVE-2025-38722, CVE-2025-38724,\nCVE-2025-38725, CVE-2025-38728, CVE-2025-38729, CVE-2025-38730,\nCVE-2025-38732, CVE-2025-38734, CVE-2025-38735, CVE-2025-39673,\nCVE-2025-39675, CVE-2025-39676, CVE-2025-39679, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39692,\nCVE-2025-39693, CVE-2025-39694, CVE-2025-39698, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39889, CVE-2025-39890,\nCVE-2025-39946, CVE-2025-39989, CVE-2025-40019, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-03-04T15:34:29Z","modified":"2026-11-03T14:35:09.454915937Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8074-2","title":"linux-azure-fips vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37956, CVE-2025-37957,\nCVE-2025-37959, CVE-2025-37960, CVE-2025-37961, CVE-2025-37962,\nCVE-2025-37963, CVE-2025-37967, CVE-2025-37968, CVE-2025-37969,\nCVE-2025-37970, CVE-2025-37972, CVE-2025-37973, CVE-2025-37975,\nCVE-2025-37977, CVE-2025-37978, CVE-2025-37979, CVE-2025-37980,\nCVE-2025-37982, CVE-2025-37983, CVE-2025-37984, CVE-2025-37985,\nCVE-2025-37986, CVE-2025-37987, CVE-2025-37988, CVE-2025-37989,\nCVE-2025-37990, CVE-2025-37991, CVE-2025-37992, CVE-2025-37994,\nCVE-2025-37995, CVE-2025-37998, CVE-2025-38003, CVE-2025-38004,\nCVE-2025-38005, CVE-2025-38006, CVE-2025-38007, CVE-2025-38008,\nCVE-2025-38009, CVE-2025-38010, CVE-2025-38011, CVE-2025-38013,\nCVE-2025-38014, CVE-2025-38015, CVE-2025-38018, CVE-2025-38019,\nCVE-2025-38020, CVE-2025-38023, CVE-2025-38024, CVE-2025-38027,\nCVE-2025-38031, CVE-2025-38034, CVE-2025-38035, CVE-2025-38037,\nCVE-2025-38039, CVE-2025-38040, CVE-2025-38043, CVE-2025-38044,\nCVE-2025-38045, CVE-2025-38048, CVE-2025-38051, CVE-2025-38052,\nCVE-2025-38053, CVE-2025-38055, CVE-2025-38057, CVE-2025-38058,\nCVE-2025-38059, CVE-2025-38060, CVE-2025-38061, CVE-2025-38062,\nCVE-2025-38063, CVE-2025-38065, CVE-2025-38066, CVE-2025-38067,\nCVE-2025-38068, CVE-2025-38071, CVE-2025-38072, CVE-2025-38074,\nCVE-2025-38075, CVE-2025-38077, CVE-2025-38078, CVE-2025-38079,\nCVE-2025-38080, CVE-2025-38081, CVE-2025-38084, CVE-2025-38085,\nCVE-2025-38086, CVE-2025-38087, CVE-2025-38088, CVE-2025-38089,\nCVE-2025-38090, CVE-2025-38094, CVE-2025-38095, CVE-2025-38097,\nCVE-2025-38098, CVE-2025-38099, CVE-2025-38100, CVE-2025-38101,\nCVE-2025-38102, CVE-2025-38103, CVE-2025-38104, CVE-2025-38107,\nCVE-2025-38108, CVE-2025-38109, CVE-2025-38110, CVE-2025-38111,\nCVE-2025-38112, CVE-2025-38113, CVE-2025-38115, CVE-2025-38117,\nCVE-2025-38119, CVE-2025-38120, CVE-2025-38122, CVE-2025-38123,\nCVE-2025-38124, CVE-2025-38125, CVE-2025-38126, CVE-2025-38127,\nCVE-2025-38129, CVE-2025-38131, CVE-2025-38135, CVE-2025-38136,\nCVE-2025-38138, CVE-2025-38142, CVE-2025-38143, CVE-2025-38145,\nCVE-2025-38146, CVE-2025-38147, CVE-2025-38148, CVE-2025-38149,\nCVE-2025-38153, CVE-2025-38154, CVE-2025-38155, CVE-2025-38156,\nCVE-2025-38157, CVE-2025-38158, CVE-2025-38159, CVE-2025-38160,\nCVE-2025-38161, CVE-2025-38162, CVE-2025-38163, CVE-2025-38164,\nCVE-2025-38165, CVE-2025-38166, CVE-2025-38167, CVE-2025-38169,\nCVE-2025-38170, CVE-2025-38173, CVE-2025-38174, CVE-2025-38180,\nCVE-2025-38181, CVE-2025-38182, CVE-2025-38183, CVE-2025-38184,\nCVE-2025-38185, CVE-2025-38190, CVE-2025-38191, CVE-2025-38192,\nCVE-2025-38193, CVE-2025-38194, CVE-2025-38197, CVE-2025-38198,\nCVE-2025-38200, CVE-2025-38202, CVE-2025-38208, CVE-2025-38210,\nCVE-2025-38211, CVE-2025-38212, CVE-2025-38214, CVE-2025-38215,\nCVE-2025-38217, CVE-2025-38218, CVE-2025-38219, CVE-2025-38220,\nCVE-2025-38222, CVE-2025-38225, CVE-2025-38226, CVE-2025-38229,\nCVE-2025-38230, CVE-2025-38231, CVE-2025-38232, CVE-2025-38236,\nCVE-2025-38239, CVE-2025-38245, CVE-2025-38246, CVE-2025-38248,\nCVE-2025-38249, CVE-2025-38250, CVE-2025-38251, CVE-2025-38253,\nCVE-2025-38255, CVE-2025-38257, CVE-2025-38258, CVE-2025-38259,\nCVE-2025-38260, CVE-2025-38262, CVE-2025-38263, CVE-2025-38264,\nCVE-2025-38265, CVE-2025-38269, CVE-2025-38274, CVE-2025-38275,\nCVE-2025-38277, CVE-2025-38278, CVE-2025-38279, CVE-2025-38280,\nCVE-2025-38282, CVE-2025-38283, CVE-2025-38285, CVE-2025-38286,\nCVE-2025-38289, CVE-2025-38290, CVE-2025-38292, CVE-2025-38293,\nCVE-2025-38295, CVE-2025-38298, CVE-2025-38299, CVE-2025-38300,\nCVE-2025-38303, CVE-2025-38304, CVE-2025-38305, CVE-2025-38307,\nCVE-2025-38310, CVE-2025-38312, CVE-2025-38313, CVE-2025-38319,\nCVE-2025-38320, CVE-2025-38321, CVE-2025-38322, CVE-2025-38323,\nCVE-2025-38324, CVE-2025-38326, CVE-2025-38328, CVE-2025-38331,\nCVE-2025-38332, CVE-2025-38333, CVE-2025-38334, CVE-2025-38335,\nCVE-2025-38336, CVE-2025-38337, CVE-2025-38338, CVE-2025-38342,\nCVE-2025-38343, CVE-2025-38344, CVE-2025-38345, CVE-2025-38346,\nCVE-2025-38347, CVE-2025-38348, CVE-2025-38349, CVE-2025-38351,\nCVE-2025-38354, CVE-2025-38361, CVE-2025-38362, CVE-2025-38363,\nCVE-2025-38364, CVE-2025-38365, CVE-2025-38368, CVE-2025-38369,\nCVE-2025-38371, CVE-2025-38373, CVE-2025-38374, CVE-2025-38375,\nCVE-2025-38376, CVE-2025-38377, CVE-2025-38382, CVE-2025-38384,\nCVE-2025-38385, CVE-2025-38386, CVE-2025-38387, CVE-2025-38388,\nCVE-2025-38389, CVE-2025-38390, CVE-2025-38391, CVE-2025-38392,\nCVE-2025-38393, CVE-2025-38395, CVE-2025-38396, CVE-2025-38399,\nCVE-2025-38400, CVE-2025-38401, CVE-2025-38402, CVE-2025-38403,\nCVE-2025-38405, CVE-2025-38406, CVE-2025-38407, CVE-2025-38408,\nCVE-2025-38409, CVE-2025-38410, CVE-2025-38412, CVE-2025-38414,\nCVE-2025-38415, CVE-2025-38416, CVE-2025-38418, CVE-2025-38419,\nCVE-2025-38420, CVE-2025-38422, CVE-2025-38424, CVE-2025-38425,\nCVE-2025-38427, CVE-2025-38428, CVE-2025-38429, CVE-2025-38430,\nCVE-2025-38436, CVE-2025-38437, CVE-2025-38439, CVE-2025-38441,\nCVE-2025-38443, CVE-2025-38444, CVE-2025-38445, CVE-2025-38448,\nCVE-2025-38449, CVE-2025-38455, CVE-2025-38456, CVE-2025-38457,\nCVE-2025-38458, CVE-2025-38459, CVE-2025-38460, CVE-2025-38461,\nCVE-2025-38462, CVE-2025-38463, CVE-2025-38464, CVE-2025-38465,\nCVE-2025-38466, CVE-2025-38467, CVE-2025-38468, CVE-2025-38469,\nCVE-2025-38470, CVE-2025-38471, CVE-2025-38472, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38485,\nCVE-2025-38487, CVE-2025-38488, CVE-2025-38489, CVE-2025-38490,\nCVE-2025-38491, CVE-2025-38493, CVE-2025-38494, CVE-2025-38495,\nCVE-2025-38496, CVE-2025-38497, CVE-2025-38499, CVE-2025-38501,\nCVE-2025-38503, CVE-2025-38506, CVE-2025-38507, CVE-2025-38510,\nCVE-2025-38511, CVE-2025-38512, CVE-2025-38513, CVE-2025-38514,\nCVE-2025-38515, CVE-2025-38516, CVE-2025-38520, CVE-2025-38521,\nCVE-2025-38524, CVE-2025-38526, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38531, CVE-2025-38532,\nCVE-2025-38533, CVE-2025-38535, CVE-2025-38537, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38540, CVE-2025-38542, CVE-2025-38543,\nCVE-2025-38544, CVE-2025-38546, CVE-2025-38548, CVE-2025-38549,\nCVE-2025-38550, CVE-2025-38551, CVE-2025-38552, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38560, CVE-2025-38561, CVE-2025-38562,\nCVE-2025-38566, CVE-2025-38568, CVE-2025-38569, CVE-2025-38571,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38582,\nCVE-2025-38583, CVE-2025-38584, CVE-2025-38585, CVE-2025-38587,\nCVE-2025-38588, CVE-2025-38590, CVE-2025-38593, CVE-2025-38595,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38610, CVE-2025-38612, CVE-2025-38614,\nCVE-2025-38615, CVE-2025-38619, CVE-2025-38622, CVE-2025-38623,\nCVE-2025-38624, CVE-2025-38625, CVE-2025-38626, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38644, CVE-2025-38645, CVE-2025-38646,\nCVE-2025-38648, CVE-2025-38650, CVE-2025-38652, CVE-2025-38653,\nCVE-2025-38659, CVE-2025-38660, CVE-2025-38663, CVE-2025-38664,\nCVE-2025-38665, CVE-2025-38668, CVE-2025-38670, CVE-2025-38671,\nCVE-2025-38675, CVE-2025-38676, CVE-2025-38677, CVE-2025-38679,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38684, CVE-2025-38685,\nCVE-2025-38686, CVE-2025-38687, CVE-2025-38688, CVE-2025-38691,\nCVE-2025-38692, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38702, CVE-2025-38703,\nCVE-2025-38704, CVE-2025-38705, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38710, CVE-2025-38711, CVE-2025-38712,\nCVE-2025-38713, CVE-2025-38714, CVE-2025-38715, CVE-2025-38716,\nCVE-2025-38718, CVE-2025-38721, CVE-2025-38722, CVE-2025-38724,\nCVE-2025-38725, CVE-2025-38728, CVE-2025-38729, CVE-2025-38730,\nCVE-2025-38732, CVE-2025-38734, CVE-2025-38735, CVE-2025-39673,\nCVE-2025-39675, CVE-2025-39676, CVE-2025-39679, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39692,\nCVE-2025-39693, CVE-2025-39694, CVE-2025-39698, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39889, CVE-2025-39890,\nCVE-2025-39946, CVE-2025-39989, CVE-2025-40019, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-03-04T15:48:10Z","modified":"2026-11-03T14:35:09.926921525Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8126-1","title":"linux-azure-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nIt was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Fastrpc Driver;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Amlogic Meson DDR PMU;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFFS2 file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - padata parallel execution mechanism;\n  - Memory management;\n  - Networking subsytem;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Network traffic control;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel futex primitives;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - PID allocator;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Maple Tree data structure library;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - RF switch subsystem;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21833, CVE-2025-21884, CVE-2025-21931, CVE-2025-22026,\nCVE-2025-22037, CVE-2025-22101, CVE-2025-22102, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22113,\nCVE-2025-22115, CVE-2025-22120, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-22126, CVE-2025-22128, CVE-2025-23129,\nCVE-2025-23130, CVE-2025-23133, CVE-2025-23140, CVE-2025-23141,\nCVE-2025-23142, CVE-2025-23143, CVE-2025-23144, CVE-2025-23145,\nCVE-2025-23146, CVE-2025-23147, CVE-2025-23148, CVE-2025-23149,\nCVE-2025-23150, CVE-2025-23151, CVE-2025-23155, CVE-2025-23156,\nCVE-2025-23157, CVE-2025-23158, CVE-2025-23159, CVE-2025-23160,\nCVE-2025-23161, CVE-2025-23163, CVE-2025-37738, CVE-2025-37739,\nCVE-2025-37740, CVE-2025-37741, CVE-2025-37742, CVE-2025-37744,\nCVE-2025-37745, CVE-2025-37748, CVE-2025-37749, CVE-2025-37754,\nCVE-2025-37755, CVE-2025-37757, CVE-2025-37758, CVE-2025-37759,\nCVE-2025-37761, CVE-2025-37763, CVE-2025-37764, CVE-2025-37765,\nCVE-2025-37766, CVE-2025-37767, CVE-2025-37768, CVE-2025-37769,\nCVE-2025-37770, CVE-2025-37771, CVE-2025-37772, CVE-2025-37773,\nCVE-2025-37775, CVE-2025-37777, CVE-2025-37778, CVE-2025-37780,\nCVE-2025-37781, CVE-2025-37784, CVE-2025-37786, CVE-2025-37787,\nCVE-2025-37788, CVE-2025-37789, CVE-2025-37790, CVE-2025-37792,\nCVE-2025-37793, CVE-2025-37794, CVE-2025-37796, CVE-2025-37799,\nCVE-2025-37800, CVE-2025-37801, CVE-2025-37803, CVE-2025-37805,\nCVE-2025-37808, CVE-2025-37809, CVE-2025-37810, CVE-2025-37811,\nCVE-2025-37812, CVE-2025-37813, CVE-2025-37815, CVE-2025-37816,\nCVE-2025-37817, CVE-2025-37819, CVE-2025-37820, CVE-2025-37822,\nCVE-2025-37823, CVE-2025-37824, CVE-2025-37826, CVE-2025-37827,\nCVE-2025-37828, CVE-2025-37829, CVE-2025-37830, CVE-2025-37831,\nCVE-2025-37836, CVE-2025-37839, CVE-2025-37840, CVE-2025-37841,\nCVE-2025-37842, CVE-2025-37844, CVE-2025-37846, CVE-2025-37849,\nCVE-2025-37850, CVE-2025-37851, CVE-2025-37852, CVE-2025-37853,\nCVE-2025-37854, CVE-2025-37856, CVE-2025-37857, CVE-2025-37858,\nCVE-2025-37859, CVE-2025-37860, CVE-2025-37861, CVE-2025-37862,\nCVE-2025-37863, CVE-2025-37864, CVE-2025-37865, CVE-2025-37867,\nCVE-2025-37869, CVE-2025-37871, CVE-2025-37872, CVE-2025-37873,\nCVE-2025-37874, CVE-2025-37875, CVE-2025-37878, CVE-2025-37879,\nCVE-2025-37881, CVE-2025-37883, CVE-2025-37884, CVE-2025-37885,\nCVE-2025-37886, CVE-2025-37887, CVE-2025-37891, CVE-2025-37892,\nCVE-2025-37897, CVE-2025-37899, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37956, CVE-2025-37957,\nCVE-2025-37959, CVE-2025-37960, CVE-2025-37961, CVE-2025-37962,\nCVE-2025-37963, CVE-2025-37967, CVE-2025-37968, CVE-2025-37969,\nCVE-2025-37970, CVE-2025-37972, CVE-2025-37973, CVE-2025-37975,\nCVE-2025-37977, CVE-2025-37978, CVE-2025-37979, CVE-2025-37980,\nCVE-2025-37982, CVE-2025-37983, CVE-2025-37984, CVE-2025-37985,\nCVE-2025-37986, CVE-2025-37987, CVE-2025-37988, CVE-2025-37989,\nCVE-2025-37990, CVE-2025-37991, CVE-2025-37992, CVE-2025-37994,\nCVE-2025-37995, CVE-2025-37998, CVE-2025-38003, CVE-2025-38004,\nCVE-2025-38005, CVE-2025-38006, CVE-2025-38007, CVE-2025-38008,\nCVE-2025-38009, CVE-2025-38010, CVE-2025-38011, CVE-2025-38013,\nCVE-2025-38014, CVE-2025-38015, CVE-2025-38018, CVE-2025-38019,\nCVE-2025-38020, CVE-2025-38023, CVE-2025-38024, CVE-2025-38027,\nCVE-2025-38031, CVE-2025-38034, CVE-2025-38035, CVE-2025-38037,\nCVE-2025-38039, CVE-2025-38040, CVE-2025-38043, CVE-2025-38044,\nCVE-2025-38045, CVE-2025-38048, CVE-2025-38051, CVE-2025-38052,\nCVE-2025-38053, CVE-2025-38055, CVE-2025-38057, CVE-2025-38058,\nCVE-2025-38059, CVE-2025-38060, CVE-2025-38061, CVE-2025-38062,\nCVE-2025-38063, CVE-2025-38065, CVE-2025-38066, CVE-2025-38067,\nCVE-2025-38068, CVE-2025-38071, CVE-2025-38072, CVE-2025-38074,\nCVE-2025-38075, CVE-2025-38077, CVE-2025-38078, CVE-2025-38079,\nCVE-2025-38080, CVE-2025-38081, CVE-2025-38084, CVE-2025-38085,\nCVE-2025-38086, CVE-2025-38087, CVE-2025-38088, CVE-2025-38089,\nCVE-2025-38090, CVE-2025-38094, CVE-2025-38095, CVE-2025-38097,\nCVE-2025-38098, CVE-2025-38099, CVE-2025-38100, CVE-2025-38101,\nCVE-2025-38102, CVE-2025-38103, CVE-2025-38104, CVE-2025-38105,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38245, CVE-2025-38246,\nCVE-2025-38248, CVE-2025-38249, CVE-2025-38250, CVE-2025-38251,\nCVE-2025-38253, CVE-2025-38255, CVE-2025-38257, CVE-2025-38258,\nCVE-2025-38259, CVE-2025-38260, CVE-2025-38262, CVE-2025-38263,\nCVE-2025-38264, CVE-2025-38265, CVE-2025-38269, CVE-2025-38274,\nCVE-2025-38275, CVE-2025-38277, CVE-2025-38278, CVE-2025-38279,\nCVE-2025-38280, CVE-2025-38282, CVE-2025-38283, CVE-2025-38285,\nCVE-2025-38286, CVE-2025-38289, CVE-2025-38290, CVE-2025-38292,\nCVE-2025-38293, CVE-2025-38295, CVE-2025-38298, CVE-2025-38299,\nCVE-2025-38300, CVE-2025-38303, CVE-2025-38304, CVE-2025-38305,\nCVE-2025-38307, CVE-2025-38310, CVE-2025-38312, CVE-2025-38313,\nCVE-2025-38319, CVE-2025-38320, CVE-2025-38321, CVE-2025-38322,\nCVE-2025-38323, CVE-2025-38324, CVE-2025-38326, CVE-2025-38328,\nCVE-2025-38331, CVE-2025-38332, CVE-2025-38333, CVE-2025-38334,\nCVE-2025-38335, CVE-2025-38336, CVE-2025-38337, CVE-2025-38338,\nCVE-2025-38342, CVE-2025-38343, CVE-2025-38344, CVE-2025-38345,\nCVE-2025-38346, CVE-2025-38347, CVE-2025-38348, CVE-2025-38349,\nCVE-2025-38351, CVE-2025-38354, CVE-2025-38361, CVE-2025-38362,\nCVE-2025-38363, CVE-2025-38364, CVE-2025-38365, CVE-2025-38368,\nCVE-2025-38369, CVE-2025-38371, CVE-2025-38373, CVE-2025-38374,\nCVE-2025-38375, CVE-2025-38376, CVE-2025-38377, CVE-2025-38382,\nCVE-2025-38384, CVE-2025-38385, CVE-2025-38386, CVE-2025-38387,\nCVE-2025-38388, CVE-2025-38389, CVE-2025-38390, CVE-2025-38391,\nCVE-2025-38392, CVE-2025-38393, CVE-2025-38395, CVE-2025-38396,\nCVE-2025-38399, CVE-2025-38400, CVE-2025-38401, CVE-2025-38402,\nCVE-2025-38403, CVE-2025-38405, CVE-2025-38406, CVE-2025-38407,\nCVE-2025-38408, CVE-2025-38409, CVE-2025-38410, CVE-2025-38412,\nCVE-2025-38414, CVE-2025-38415, CVE-2025-38416, CVE-2025-38418,\nCVE-2025-38419, CVE-2025-38420, CVE-2025-38422, CVE-2025-38424,\nCVE-2025-38425, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38502, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38556,\nCVE-2025-38560, CVE-2025-38561, CVE-2025-38562, CVE-2025-38566,\nCVE-2025-38568, CVE-2025-38569, CVE-2025-38571, CVE-2025-38572,\nCVE-2025-38574, CVE-2025-38576, CVE-2025-38577, CVE-2025-38578,\nCVE-2025-38579, CVE-2025-38581, CVE-2025-38582, CVE-2025-38583,\nCVE-2025-38584, CVE-2025-38585, CVE-2025-38587, CVE-2025-38588,\nCVE-2025-38590, CVE-2025-38593, CVE-2025-38595, CVE-2025-38601,\nCVE-2025-38602, CVE-2025-38604, CVE-2025-38608, CVE-2025-38609,\nCVE-2025-38610, CVE-2025-38612, CVE-2025-38614, CVE-2025-38615,\nCVE-2025-38619, CVE-2025-38622, CVE-2025-38623, CVE-2025-38624,\nCVE-2025-38625, CVE-2025-38626, CVE-2025-38627, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38643, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38709, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39678, CVE-2025-39679, CVE-2025-39681, CVE-2025-39683,\nCVE-2025-39684, CVE-2025-39685, CVE-2025-39686, CVE-2025-39687,\nCVE-2025-39689, CVE-2025-39691, CVE-2025-39692, CVE-2025-39693,\nCVE-2025-39694, CVE-2025-39697, CVE-2025-39698, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39889, CVE-2025-39890, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39895, CVE-2025-39897, CVE-2025-39899,\nCVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39914, CVE-2025-39916,\nCVE-2025-39920, CVE-2025-39923, CVE-2025-39927, CVE-2025-39929,\nCVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937,\nCVE-2025-39938, CVE-2025-39940, CVE-2025-39942, CVE-2025-39943,\nCVE-2025-39944, CVE-2025-39945, CVE-2025-39946, CVE-2025-39947,\nCVE-2025-39948, CVE-2025-39949, CVE-2025-39950, CVE-2025-39951,\nCVE-2025-39952, CVE-2025-39953, CVE-2025-39955, CVE-2025-39957,\nCVE-2025-39961, CVE-2025-39965, CVE-2025-39967, CVE-2025-39968,\nCVE-2025-39969, CVE-2025-39970, CVE-2025-39971, CVE-2025-39972,\nCVE-2025-39973, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980,\nCVE-2025-39981, CVE-2025-39982, CVE-2025-39985, CVE-2025-39986,\nCVE-2025-39987, CVE-2025-39988, CVE-2025-39989, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40019, CVE-2025-40020,\nCVE-2025-40021, CVE-2025-40024, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40035, CVE-2025-40036, CVE-2025-40037,\nCVE-2025-40038, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40047, CVE-2025-40048, CVE-2025-40049, CVE-2025-40051,\nCVE-2025-40052, CVE-2025-40053, CVE-2025-40055, CVE-2025-40056,\nCVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,\nCVE-2025-40061, CVE-2025-40062, CVE-2025-40067, CVE-2025-40068,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40077, CVE-2025-40078,\nCVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40083,\nCVE-2025-40084, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101,\nCVE-2025-40103, CVE-2025-40104, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40107, CVE-2025-40109, CVE-2025-40110, CVE-2025-40111,\nCVE-2025-40112, CVE-2025-40115, CVE-2025-40116, CVE-2025-40118,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40123, CVE-2025-40124,\nCVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40129,\nCVE-2025-40134, CVE-2025-40137, CVE-2025-40140, CVE-2025-40141,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156,\nCVE-2025-40159, CVE-2025-40160, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40215, CVE-2025-40218, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40221, CVE-2025-40223, CVE-2025-40226,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237,\nCVE-2025-40238, CVE-2025-40240, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40250,\nCVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40266,\nCVE-2025-40268, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40297, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734, CVE-2025-68750)\n","status":"published","published":"2026-03-25T19:13:52Z","modified":"2026-11-03T14:35:29.863770912Z","updated_at":"2026-11-03T15:16:14.724953Z"}]}}