{"id":"CVE-2025-40038","aliases":["BELL-CVE-2025-40038","DEBIAN-CVE-2025-40038","EUVD-2025-36490","GHSA-c4m5-3mj6-4mp6","MGASA-2025-0309","MGASA-2025-0310","OESA-2025-2695","OESA-2025-2696","OESA-2025-2700","ROOT-OS-UBUNTU-2404-CVE-2025-40038","SUSE-SU-2025:4393-1","SUSE-SU-2025:4422-1","SUSE-SU-2025:4505-1","SUSE-SU-2025:4516-1","SUSE-SU-2025:4517-1","SUSE-SU-2025:4521-1","SUSE-SU-2026:20012-1","SUSE-SU-2026:20015-1","SUSE-SU-2026:20021-1","SUSE-SU-2026:20039-1","SUSE-SU-2026:20059-1","SUSE-SU-2026:20473-1","SUSE-SU-2026:20496-1","SUSE-SU-2026:20562-1","UBUNTU-CVE-2025-40038","USN-8029-1","USN-8029-2","USN-8029-3","USN-8030-1","USN-8048-1","USN-8095-1","USN-8095-2","USN-8095-3","USN-8095-4","USN-8095-5","USN-8100-1","USN-8125-1","USN-8126-1","USN-8165-1","USN-8261-1","openSUSE-SU-2025:15702-1","openSUSE-SU-2025:20172-1","openSUSE-SU-2026:10301-1"],"status":"published","title":"KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00177,"percentile":0.07374,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-10-28T11:48:18Z","modified":"2026-11-06T16:17:02Z","fixes":[{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.53-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.6.113","6.12.53","6.17.3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.57-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.17.6-1"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1050.53~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1051.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1058.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1052.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-106.106~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1049.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-106.106.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1049.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1047.48~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-106.106~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1045.46~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-106.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1050.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","fixed_in":["6.17.0-1007.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1051.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1058.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1052.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1008.8~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1048.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1035.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1049.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-106.106.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1049.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1049.52.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1011.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1047.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1007.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1050.54"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1028.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1017.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2040.41"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1006.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1050.53+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1052.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-106.106+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1052.55+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux","fixed_in":["6.17.0-14.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-aws","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-azure","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-gcp","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-oracle","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-raspi","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-realtime","fixed_in":["6.17.0-1006.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-riscv","fixed_in":["6.17.0-14.14.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.52-r0"},{"fixed":"6.12.53-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.5.0"},{"fixed":"6.6.113"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.53"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.3"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.57-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.6-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.2-1~exp1","6.17.5-1~exp1"]},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.116-1.mga9"}]}],"bundled":119},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-87.mga9"}]}],"bundled":119},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-13.mga9"}]}],"bundled":119},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.116-1.mga9"}]}],"bundled":119},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-119.0.0.122.oe2403sp1"}]}],"bundled":35},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-119.0.0.123.oe2403sp2"}]}],"bundled":35},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-119.0.0.110.oe2403"}]}],"bundled":34},{"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 Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1.150700.17.17.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.2"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.81.3"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"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.81.3.150600.12.36.3"}]}],"bundled":65},{"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.81.2"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"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.81.1"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"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.81.2"}]}],"bundled":65},{"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.81.1"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.3"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"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.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3.150600.12.36.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.2"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.81.3"}]}],"bundled":65},{"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.58.1"}]}],"bundled":65},{"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.58.1"}]}],"bundled":65},{"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.58.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.58.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.58.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.58.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_7","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.1"}]}],"bundled":69},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.25.1"}]}],"bundled":69},{"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.21.1"}]}],"bundled":70},{"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.21.1"}]}],"bundled":70},{"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.21.1"}]}],"bundled":70},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.61.1"}]}],"bundled":65},{"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.61.1"}]}],"bundled":65},{"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.61.1"}]}],"bundled":65},{"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.61.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.61.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.61.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.61.1"}]}],"bundled":65},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.61.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1.160000.2.5"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1.160000.2.5"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1.160000.2.5"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1.21.15"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1.21.15"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-38.1"}]}],"bundled":65},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-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-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32","6.8.0-1039.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1048.53"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1035.38"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"versions":["6.17.0-1004.4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.20"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.54"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.29"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.21"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2040.41"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.7~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.58+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.7"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14.1"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.7"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6"],"bundled":366},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10"],"bundled":366},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1048.53"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1035.38"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.54"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2040.41"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52"],"bundled":426},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1"],"bundled":1179},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.58+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1"],"bundled":438},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.30"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29"],"bundled":609},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.7-1.1"}]}],"bundled":83},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1.160000.2.5"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.8.1"}]}],"bundled":100},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source-longterm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.16-1.1"}]}],"bundled":199}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/cd3efb93677c4b0cf76348882fb429165fee33fd","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/f994e9c790ce97d3cf01af4d0a1b9add0c955aee","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/da2a3c231f7f2a5ac146d972b8c1d7d84aff6d70","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/0910dd7c9ad45a2605c45fd2bf3d1bcac087687c","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40038","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-c4m5-3mj6-4mp6"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-40038","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40038.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-40038","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0309.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34713","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.106","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.107","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.108","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.109","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.110","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.111","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.112","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.113","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.114","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.115","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.116","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2025-0310.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34721","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2695","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38326","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39716","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39767","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39842","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39909","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40207","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2696","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2700","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254393-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1235463","tags":["report"]},{"url":"https://bugzilla.suse.com/1236743","tags":["report"]},{"url":"https://bugzilla.suse.com/1237888","tags":["report"]},{"url":"https://bugzilla.suse.com/1241166","tags":["report"]},{"url":"https://bugzilla.suse.com/1243474","tags":["report"]},{"url":"https://bugzilla.suse.com/1245193","tags":["report"]},{"url":"https://bugzilla.suse.com/1247076","tags":["report"]},{"url":"https://bugzilla.suse.com/1247500","tags":["report"]},{"url":"https://bugzilla.suse.com/1247509","tags":["report"]},{"url":"https://bugzilla.suse.com/1247683","tags":["report"]},{"url":"https://bugzilla.suse.com/1249547","tags":["report"]},{"url":"https://bugzilla.suse.com/1249912","tags":["report"]},{"url":"https://bugzilla.suse.com/1249982","tags":["report"]},{"url":"https://bugzilla.suse.com/1250034","tags":["report"]},{"url":"https://bugzilla.suse.com/1250176","tags":["report"]},{"url":"https://bugzilla.suse.com/1250237","tags":["report"]},{"url":"https://bugzilla.suse.com/1250252","tags":["report"]},{"url":"https://bugzilla.suse.com/1250705","tags":["report"]},{"url":"https://bugzilla.suse.com/1251120","tags":["report"]},{"url":"https://bugzilla.suse.com/1251786","tags":["report"]},{"url":"https://bugzilla.suse.com/1252063","tags":["report"]},{"url":"https://bugzilla.suse.com/1252267","tags":["report"]},{"url":"https://bugzilla.suse.com/1252269","tags":["report"]},{"url":"https://bugzilla.suse.com/1252303","tags":["report"]},{"url":"https://bugzilla.suse.com/1252352","tags":["report"]},{"url":"https://bugzilla.suse.com/1252353","tags":["report"]},{"url":"https://bugzilla.suse.com/1252365","tags":["report"]},{"url":"https://bugzilla.suse.com/1252366","tags":["report"]},{"url":"https://bugzilla.suse.com/1252368","tags":["report"]},{"url":"https://bugzilla.suse.com/1252370","tags":["report"]},{"url":"https://bugzilla.suse.com/1252681","tags":["report"]},{"url":"https://bugzilla.suse.com/1252763","tags":["report"]},{"url":"https://bugzilla.suse.com/1252773","tags":["report"]},{"url":"https://bugzilla.suse.com/1252774","tags":["report"]},{"url":"https://bugzilla.suse.com/1252780","tags":["report"]},{"url":"https://bugzilla.suse.com/1252790","tags":["report"]},{"url":"https://bugzilla.suse.com/1252794","tags":["report"]},{"url":"https://bugzilla.suse.com/1252795","tags":["report"]},{"url":"https://bugzilla.suse.com/1252809","tags":["report"]},{"url":"https://bugzilla.suse.com/1252817","tags":["report"]},{"url":"https://bugzilla.suse.com/1252821","tags":["report"]},{"url":"https://bugzilla.suse.com/1252836","tags":["report"]},{"url":"https://bugzilla.suse.com/1252845","tags":["report"]},{"url":"https://bugzilla.suse.com/1252862","tags":["report"]},{"url":"https://bugzilla.suse.com/1252912","tags":["report"]},{"url":"https://bugzilla.suse.com/1252917","tags":["report"]},{"url":"https://bugzilla.suse.com/1252923","tags":["report"]},{"url":"https://bugzilla.suse.com/1252928","tags":["report"]},{"url":"https://bugzilla.suse.com/1253018","tags":["report"]},{"url":"https://bugzilla.suse.com/1253176","tags":["report"]},{"url":"https://bugzilla.suse.com/1253275","tags":["report"]},{"url":"https://bugzilla.suse.com/1253318","tags":["report"]},{"url":"https://bugzilla.suse.com/1253324","tags":["report"]},{"url":"https://bugzilla.suse.com/1253349","tags":["report"]},{"url":"https://bugzilla.suse.com/1253352","tags":["report"]},{"url":"https://bugzilla.suse.com/1253355","tags":["report"]},{"url":"https://bugzilla.suse.com/1253360","tags":["report"]},{"url":"https://bugzilla.suse.com/1253362","tags":["report"]},{"url":"https://bugzilla.suse.com/1253363","tags":["report"]},{"url":"https://bugzilla.suse.com/1253367","tags":["report"]},{"url":"https://bugzilla.suse.com/1253369","tags":["report"]},{"url":"https://bugzilla.suse.com/1253393","tags":["report"]},{"url":"https://bugzilla.suse.com/1253394","tags":["report"]},{"url":"https://bugzilla.suse.com/1253395","tags":["report"]},{"url":"https://bugzilla.suse.com/1253403","tags":["report"]},{"url":"https://bugzilla.suse.com/1253407","tags":["report"]},{"url":"https://bugzilla.suse.com/1253409","tags":["report"]},{"url":"https://bugzilla.suse.com/1253412","tags":["report"]},{"url":"https://bugzilla.suse.com/1253416","tags":["report"]},{"url":"https://bugzilla.suse.com/1253421","tags":["report"]},{"url":"https://bugzilla.suse.com/1253423","tags":["report"]},{"url":"https://bugzilla.suse.com/1253424","tags":["report"]},{"url":"https://bugzilla.suse.com/1253425","tags":["report"]},{"url":"https://bugzilla.suse.com/1253427","tags":["report"]},{"url":"https://bugzilla.suse.com/1253428","tags":["report"]},{"url":"https://bugzilla.suse.com/1253431","tags":["report"]},{"url":"https://bugzilla.suse.com/1253436","tags":["report"]},{"url":"https://bugzilla.suse.com/1253438","tags":["report"]},{"url":"https://bugzilla.suse.com/1253440","tags":["report"]},{"url":"https://bugzilla.suse.com/1253441","tags":["report"]},{"url":"https://bugzilla.suse.com/1253445","tags":["report"]},{"url":"https://bugzilla.suse.com/1253448","tags":["report"]},{"url":"https://bugzilla.suse.com/1253449","tags":["report"]},{"url":"https://bugzilla.suse.com/1253453","tags":["report"]},{"url":"https://bugzilla.suse.com/1253456","tags":["report"]},{"url":"https://bugzilla.suse.com/1253472","tags":["report"]},{"url":"https://bugzilla.suse.com/1253648","tags":["report"]},{"url":"https://bugzilla.suse.com/1253779","tags":["report"]},{"url":"https://bugzilla.suse.com/1254181","tags":["report"]},{"url":"https://bugzilla.suse.com/1254221","tags":["report"]},{"url":"https://bugzilla.suse.com/1254235","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37916","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40207","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254422-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1232223","tags":["report"]},{"url":"https://bugzilla.suse.com/1247079","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38361","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254505-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254516-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254517-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1247078","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38360","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254521-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620012-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1245431","tags":["report"]},{"url":"https://bugzilla.suse.com/1245498","tags":["report"]},{"url":"https://bugzilla.suse.com/1245499","tags":["report"]},{"url":"https://bugzilla.suse.com/1246328","tags":["report"]},{"url":"https://bugzilla.suse.com/1246843","tags":["report"]},{"url":"https://bugzilla.suse.com/1248792","tags":["report"]},{"url":"https://bugzilla.suse.com/1249256","tags":["report"]},{"url":"https://bugzilla.suse.com/1249397","tags":["report"]},{"url":"https://bugzilla.suse.com/1249977","tags":["report"]},{"url":"https://bugzilla.suse.com/1250723","tags":["report"]},{"url":"https://bugzilla.suse.com/1250746","tags":["report"]},{"url":"https://bugzilla.suse.com/1251817","tags":["report"]},{"url":"https://bugzilla.suse.com/1252054","tags":["report"]},{"url":"https://bugzilla.suse.com/1252301","tags":["report"]},{"url":"https://bugzilla.suse.com/1252342","tags":["report"]},{"url":"https://bugzilla.suse.com/1252357","tags":["report"]},{"url":"https://bugzilla.suse.com/1252686","tags":["report"]},{"url":"https://bugzilla.suse.com/1252776","tags":["report"]},{"url":"https://bugzilla.suse.com/1252779","tags":["report"]},{"url":"https://bugzilla.suse.com/1252808","tags":["report"]},{"url":"https://bugzilla.suse.com/1252824","tags":["report"]},{"url":"https://bugzilla.suse.com/1252901","tags":["report"]},{"url":"https://bugzilla.suse.com/1252919","tags":["report"]},{"url":"https://bugzilla.suse.com/1253155","tags":["report"]},{"url":"https://bugzilla.suse.com/1253238","tags":["report"]},{"url":"https://bugzilla.suse.com/1253328","tags":["report"]},{"url":"https://bugzilla.suse.com/1253330","tags":["report"]},{"url":"https://bugzilla.suse.com/1253342","tags":["report"]},{"url":"https://bugzilla.suse.com/1253348","tags":["report"]},{"url":"https://bugzilla.suse.com/1253386","tags":["report"]},{"url":"https://bugzilla.suse.com/1253402","tags":["report"]},{"url":"https://bugzilla.suse.com/1253405","tags":["report"]},{"url":"https://bugzilla.suse.com/1253408","tags":["report"]},{"url":"https://bugzilla.suse.com/1253410","tags":["report"]},{"url":"https://bugzilla.suse.com/1253422","tags":["report"]},{"url":"https://bugzilla.suse.com/1253426","tags":["report"]},{"url":"https://bugzilla.suse.com/1253433","tags":["report"]},{"url":"https://bugzilla.suse.com/1253443","tags":["report"]},{"url":"https://bugzilla.suse.com/1253450","tags":["report"]},{"url":"https://bugzilla.suse.com/1253451","tags":["report"]},{"url":"https://bugzilla.suse.com/1253455","tags":["report"]},{"url":"https://bugzilla.suse.com/1253457","tags":["report"]},{"url":"https://bugzilla.suse.com/1253463","tags":["report"]},{"url":"https://bugzilla.suse.com/1253622","tags":["report"]},{"url":"https://bugzilla.suse.com/1253624","tags":["report"]},{"url":"https://bugzilla.suse.com/1253635","tags":["report"]},{"url":"https://bugzilla.suse.com/1253643","tags":["report"]},{"url":"https://bugzilla.suse.com/1253647","tags":["report"]},{"url":"https://bugzilla.suse.com/1254119","tags":["report"]},{"url":"https://bugzilla.suse.com/1254308","tags":["report"]},{"url":"https://bugzilla.suse.com/1254315","tags":["report"]},{"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-38321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40203","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620015-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620021-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620039-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620059-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620473-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620496-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620562-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-40038","tags":["report"]},{"url":"https://git.kernel.org/linus/0910dd7c9ad45a2605c45fd2bf3d1bcac087687c","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8029-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8030-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8029-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8048-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8029-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8100-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8125-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8126-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8165-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8261-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23273","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-28956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68766","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2025-40038","title":"KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","status":"published","published":"2025-10-28T11:48:18.889Z","modified":"2026-10-15T22:02:36.482Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:32:34.773122Z"}],"euvd":[{"id":"EUVD-2025-36490","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","status":"published","published":"2025-10-28T11:48:18Z","modified":"2026-10-15T22:02:36Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T17:00:07.847263Z"}],"ghsa":[{"id":"GHSA-c4m5-3mj6-4mp6","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","status":"published","published":"2025-10-28T12:30:16Z","modified":"2026-07-30T06:33:15Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:09:55.621217Z"}],"nvd":[{"id":"CVE-2025-40038","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","status":"published","published":"2025-10-28T12:15:37.733Z","modified":"2026-10-19T21:10:00.16Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"secondary"}],"updated_at":"2026-11-02T14:11:40.754193Z"}],"osv":[{"id":"BELL-CVE-2025-40038","status":"published","published":"2025-10-29T10:53:56.782989Z","modified":"2026-07-31T07:18:26.218962575Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:22.246535Z"},{"id":"CVE-2025-40038","title":"KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid\n\nSkip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP\nisn't valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn't provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u003c/TASK\u003e\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).","status":"published","published":"2025-10-28T11:48:18.889Z","modified":"2026-10-28T02:30:45.819149033Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:49.052395Z"},{"id":"DEBIAN-CVE-2025-40038","description":"In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid Skip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP isn't valid, e.g. because KVM is running with nrips=false. SVM must decode and emulate to skip the instruction if the CPU doesn't provide the next RIP, and getting the instruction bytes to decode requires reading guest memory. Reading guest memory through the emulator can fault, i.e. can sleep, which is disallowed since the fastpath handlers run with IRQs disabled. BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu preempt_count: 1, expected: 0 INFO: lockdep is turned off. irq event stamp: 30580 hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm] hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0 softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210 softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210 CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE Tainted: [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025 Call Trace: \u003cTASK\u003e dump_stack_lvl+0x7d/0xb0 __might_resched+0x271/0x290 __might_fault+0x28/0x80 kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm] kvm_fetch_guest_virt+0x92/0xc0 [kvm] __do_insn_fetch_bytes+0xf3/0x1e0 [kvm] x86_decode_insn+0xd1/0x1010 [kvm] x86_emulate_instruction+0x105/0x810 [kvm] __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd] handle_fastpath_invd+0xc4/0x1a0 [kvm] vcpu_run+0x11a1/0x1db0 [kvm] kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm] kvm_vcpu_ioctl+0x578/0x6a0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x8a/0x2c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f479d57a94b \u003c/TASK\u003e Note, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with different justification (KVM now grabs SRCU when skipping the instruction for other reasons).","status":"published","published":"2025-10-28T12:15:37.733Z","modified":"2026-10-23T18:04:35.861939324Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:46.998514Z"},{"id":"OESA-2025-2695","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\nmisc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error\n\nAfter devm_request_irq() fails with error in pci_endpoint_test_request_irq(),\nthe pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs\nhave been released.\n\nHowever, some requested IRQs remain unreleased, so there are still\n/proc/irq/* entries remaining, and this results in WARN() with the\nfollowing message:\n\n remove_proc_entry: removing non-empty directory \u0026apos;irq/30\u0026apos;, leaking at least \u0026apos;pci-endpoint-test.0\u0026apos;\n WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c\n\nTo solve this issue, set the number of remaining IRQs to test-\u0026gt;num_irqs,\nand release IRQs in advance by calling pci_endpoint_test_release_irq().\n\n[kwilczynski: commit log](CVE-2025-23140)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: csa unmap use uninterruptible lock\n\nAfter process exit to unmap csa and free GPU vm, if signal is accepted\nand then waiting to take vm lock is interrupted and return, it causes\nmemory leaking and below warning backtrace.\n\nChange to use uninterruptible wait lock fix the issue.\n\nWARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525\n amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n drm_file_free.part.0+0x1da/0x230 [drm]\n drm_close_helper.isra.0+0x65/0x70 [drm]\n drm_release+0x6a/0x120 [drm]\n amdgpu_drm_release+0x51/0x60 [amdgpu]\n __fput+0x9f/0x280\n ____fput+0xe/0x20\n task_work_run+0x67/0xa0\n do_exit+0x217/0x3c0\n do_group_exit+0x3b/0xb0\n get_signal+0x14a/0x8d0\n arch_do_signal_or_restart+0xde/0x100\n exit_to_user_mode_loop+0xc1/0x1a0\n exit_to_user_mode_prepare+0xf4/0x100\n syscall_exit_to_user_mode+0x17/0x40\n do_syscall_64+0x69/0xc0\n\n(cherry picked from commit 7dbbfb3c171a6f63b01165958629c9c26abf38ab)(CVE-2025-38011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: avoid NULL pointer dereference if no valid csum tree\n\n[BUG]\nWhen trying read-only scrub on a btrfs with rescue=idatacsums mount\noption, it will crash with the following call trace:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000208\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n CPU: 1 UID: 0 PID: 835 Comm: btrfs Tainted: G O 6.15.0-rc3-custom+ #236 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022\n RIP: 0010:btrfs_lookup_csums_bitmap+0x49/0x480 [btrfs]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n scrub_find_fill_first_stripe+0x35b/0x3d0 [btrfs]\n scrub_simple_mirror+0x175/0x290 [btrfs]\n scrub_stripe+0x5f7/0x6f0 [btrfs]\n scrub_chunk+0x9a/0x150 [btrfs]\n scrub_enumerate_chunks+0x333/0x660 [btrfs]\n btrfs_scrub_dev+0x23e/0x600 [btrfs]\n btrfs_ioctl+0x1dcf/0x2f80 [btrfs]\n __x64_sys_ioctl+0x97/0xc0\n do_syscall_64+0x4f/0x120\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n[CAUSE]\nMount option \u0026quot;rescue=idatacsums\u0026quot; will completely skip loading the csum\ntree, so that any data read will not find any data csum thus we will\nignore data checksum verification.\n\nNormally call sites utilizing csum tree will check the fs state flag\nNO_DATA_CSUMS bit, but unfortunately scrub does not check that bit at all.\n\nThis results in scrub to call btrfs_search_slot() on a NULL pointer\nand triggered above crash.\n\n[FIX]\nCheck both extent and csum tree root before doing any tree search.(CVE-2025-38059)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: holding cscfg_csdev_lock while removing cscfg from csdev\n\nThere\u0026apos;ll be possible race scenario for coresight config:\n\nCPU0 CPU1\n(perf enable) load module\n cscfg_load_config_sets()\n activate config. // sysfs\n (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\n lock(csdev-\u0026gt;cscfg_csdev_lock)\n deactivate config // sysfs\n (sys_activec_cnt == 0)\n cscfg_unload_config_sets()\n \u0026lt;iterating config_csdev_list\u0026gt; cscfg_remove_owned_csdev_configs()\n // here load config activate by CPU1\n unlock(csdev-\u0026gt;cscfg_csdev_lock)\n\niterating config_csdev_list could be raced with config_csdev_list\u0026apos;s\nentry delete.\n\nTo resolve this race , hold csdev-\u0026gt;cscfg_csdev_lock() while\ncscfg_remove_owned_csdev_configs()(CVE-2025-38132)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init()\n\ndevm_ioremap() returns NULL on error. Currently, mt7915_mmio_wed_init()\ndoes not check for this case, which results in a NULL pointer\ndereference.\n\nPrevent null pointer dereference in mt7915_mmio_wed_init().(CVE-2025-38155)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: handle hdr_first_de() return value\n\nThe hdr_first_de() function returns a pointer to a struct NTFS_DE. This\npointer may be NULL. To handle the NULL error effectively, it is important\nto implement an error handler. This will help manage potential errors\nconsistently.\n\nAdditionally, error handling for the return value already exists at other\npoints where this function is called.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-38167)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nexfat: fix double free in delayed_free\n\nThe double free could happen in the following path.\n\nexfat_create_upcase_table()\n exfat_create_upcase_table() : return error\n exfat_free_upcase_table() : free -\u0026gt;vol_utbl\n exfat_load_default_upcase_table : return error\n exfat_kill_sb()\n delayed_free()\n exfat_free_upcase_table() \u0026lt;--------- double free\nThis patch set -\u0026gt;vol_util as NULL after freeing it.(CVE-2025-38206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naoe: clean device rq_list in aoedev_downdev()\n\nAn aoe device\u0026apos;s rq_list contains accepted block requests that are\nwaiting to be transmitted to the aoe target. This queue was added as\npart of the conversion to blk_mq. However, the queue was not cleaned out\nwhen an aoe device is downed which caused blk_mq_freeze_queue() to sleep\nindefinitely waiting for those requests to complete, causing a hang. This\nfix cleans out the queue before calling blk_mq_freeze_queue().(CVE-2025-38326)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n\nRobert Morris reported:\n\n|If a malicious USB device pretends to be an Intersil p54 wifi\n|interface and generates an eeprom_readback message with a large\n|eeprom-\u0026gt;v1.len, p54_rx_eeprom_readback() will copy data from the\n|message beyond the end of priv-\u0026gt;eeprom.\n|\n|static void p54_rx_eeprom_readback(struct p54_common *priv,\n| struct sk_buff *skb)\n|{\n| struct p54_hdr *hdr = (struct p54_hdr *) skb-\u0026gt;data;\n| struct p54_eeprom_lm86 *eeprom = (struct p54_eeprom_lm86 *) hdr-\u0026gt;data;\n|\n| if (priv-\u0026gt;fw_var \u0026gt;= 0x509) {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v2.data,\n| le16_to_cpu(eeprom-\u0026gt;v2.len));\n| } else {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v1.data,\n| le16_to_cpu(eeprom-\u0026gt;v1.len));\n| }\n| [...]\n\nThe eeprom-\u0026gt;v{1,2}.len is set by the driver in p54_download_eeprom().\nThe device is supposed to provide the same length back to the driver.\nBut yes, it\u0026apos;s possible (like shown in the report) to alter the value\nto something that causes a crash/panic due to overrun.\n\nThis patch addresses the issue by adding the size to the common device\ncontext, so p54_rx_eeprom_readback no longer relies on possibly tampered\nvalues... That said, it also checks if the \u0026quot;firmware\u0026quot; altered the value\nand no longer copies them.\n\nThe one, small saving grace is: Before the driver tries to read the eeprom,\nit needs to upload \u0026gt;a\u0026lt; firmware. the vendor firmware has a proprietary\nlicense and as a reason, it is not present on most distributions by\ndefault.(CVE-2025-38348)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Disable migration in nf_hook_run_bpf().\n\nsyzbot reported that the netfilter bpf prog can be called without\nmigration disabled in xmit path.\n\nThen the assertion in __bpf_prog_run() fails, triggering the splat\nbelow. [0]\n\nLet\u0026apos;s use bpf_prog_run_pin_on_cpu() in nf_hook_run_bpf().\n\n[0]:\nBUG: assuming non migratable context at ./include/linux/filter.h:703\nin_atomic(): 0, irqs_disabled(): 0, migration_disabled() 0 pid: 5829, name: sshd-session\n3 locks held by sshd-session/5829:\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1667 [inline]\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: tcp_sendmsg+0x20/0x50 net/ipv4/tcp.c:1395\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: __ip_queue_xmit+0x69/0x26c0 net/ipv4/ip_output.c:470\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: nf_hook+0xb2/0x680 include/linux/netfilter.h:241\nCPU: 0 UID: 0 PID: 5829 Comm: sshd-session Not tainted 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n __cant_migrate kernel/sched/core.c:8860 [inline]\n __cant_migrate+0x1c7/0x250 kernel/sched/core.c:8834\n __bpf_prog_run include/linux/filter.h:703 [inline]\n bpf_prog_run include/linux/filter.h:725 [inline]\n nf_hook_run_bpf+0x83/0x1e0 net/netfilter/nf_bpf_link.c:20\n nf_hook_entry_hookfn include/linux/netfilter.h:157 [inline]\n nf_hook_slow+0xbb/0x200 net/netfilter/core.c:623\n nf_hook+0x370/0x680 include/linux/netfilter.h:272\n NF_HOOK_COND include/linux/netfilter.h:305 [inline]\n ip_output+0x1bc/0x2a0 net/ipv4/ip_output.c:433\n dst_output include/net/dst.h:459 [inline]\n ip_local_out net/ipv4/ip_output.c:129 [inline]\n __ip_queue_xmit+0x1d7d/0x26c0 net/ipv4/ip_output.c:527\n __tcp_transmit_skb+0x2686/0x3e90 net/ipv4/tcp_output.c:1479\n tcp_transmit_skb net/ipv4/tcp_output.c:1497 [inline]\n tcp_write_xmit+0x1274/0x84e0 net/ipv4/tcp_output.c:2838\n __tcp_push_pending_frames+0xaf/0x390 net/ipv4/tcp_output.c:3021\n tcp_push+0x225/0x700 net/ipv4/tcp.c:759\n tcp_sendmsg_locked+0x1870/0x42b0 net/ipv4/tcp.c:1359\n tcp_sendmsg+0x2e/0x50 net/ipv4/tcp.c:1396\n inet_sendmsg+0xb9/0x140 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n __sock_sendmsg net/socket.c:727 [inline]\n sock_write_iter+0x4aa/0x5b0 net/socket.c:1131\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0x6c7/0x1150 fs/read_write.c:686\n ksys_write+0x1f8/0x250 fs/read_write.c:738\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fe7d365d407\nCode: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 \u0026lt;5b\u0026gt; c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff\nRSP:(CVE-2025-38640)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: Don\u0026apos;t crash in stack_top() for tasks without ABI or vDSO\n\nNot all tasks have an ABI associated or vDSO mapped,\nfor example kthreads never do.\nIf such a task ever ends up calling stack_top(), it will derefence the\nNULL ABI pointer and crash.\n\nThis can for example happen when using kunit:\n\n mips_stack_top+0x28/0xc0\n arch_pick_mmap_layout+0x190/0x220\n kunit_vm_mmap_init+0xf8/0x138\n __kunit_add_resource+0x40/0xa8\n kunit_vm_mmap+0x88/0xd8\n usercopy_test_init+0xb8/0x240\n kunit_try_run_case+0x5c/0x1a8\n kunit_generic_run_threadfn_adapter+0x28/0x50\n kthread+0x118/0x240\n ret_from_kernel_thread+0x14/0x1c\n\nOnly dereference the ABI point if it is set.\n\nThe GIC page is also included as it is specific to the vDSO.\nAlso move the randomization adjustment into the same conditional.(CVE-2025-38696)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: linearize cloned gso packets in sctp_rcv\n\nA cloned head skb still shares these frag skbs in fraglist with the\noriginal head skb. It\u0026apos;s not safe to access these frag skbs.\n\nsyzbot reported two use-of-uninitialized-memory bugs caused by this:\n\n BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998\n sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331\n sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122\n __release_sock+0x1da/0x330 net/core/sock.c:3106\n release_sock+0x6b/0x250 net/core/sock.c:3660\n sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360\n sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885\n sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031\n inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:718 [inline]\n\nand\n\n BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331\n sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148\n __release_sock+0x1d3/0x330 net/core/sock.c:3213\n release_sock+0x6b/0x270 net/core/sock.c:3767\n sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367\n sctp_sendmsg_to_asoc+0x223a/0x2260 net/sctp/socket.c:1886\n sctp_sendmsg+0x3910/0x49f0 net/sctp/socket.c:2032\n inet_sendmsg+0x269/0x2a0 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n\nThis patch fixes it by linearizing cloned gso packets in sctp_rcv().(CVE-2025-38718)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix UAF on smcsk after smc_listen_out()\n\nBPF CI testing report a UAF issue:\n\n [ 16.446633] BUG: kernel NULL pointer dereference, address: 000000000000003 0\n [ 16.447134] #PF: supervisor read access in kernel mod e\n [ 16.447516] #PF: error_code(0x0000) - not-present pag e\n [ 16.447878] PGD 0 P4D 0\n [ 16.448063] Oops: Oops: 0000 [#1] PREEMPT SMP NOPT I\n [ 16.448409] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Tainted: G OE 6.13.0-rc3-g89e8a75fda73-dirty #4 2\n [ 16.449124] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODUL E\n [ 16.449502] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/201 4\n [ 16.450201] Workqueue: smc_hs_wq smc_listen_wor k\n [ 16.450531] RIP: 0010:smc_listen_work+0xc02/0x159 0\n [ 16.452158] RSP: 0018:ffffb5ab40053d98 EFLAGS: 0001024 6\n [ 16.452526] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 000000000000030 0\n [ 16.452994] RDX: 0000000000000280 RSI: 00003513840053f0 RDI: 000000000000000 0\n [ 16.453492] RBP: ffffa097808e3800 R08: ffffa09782dba1e0 R09: 000000000000000 5\n [ 16.453987] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa0978274640 0\n [ 16.454497] R13: 0000000000000000 R14: 0000000000000000 R15: ffffa09782d4092 0\n [ 16.454996] FS: 0000000000000000(0000) GS:ffffa097bbc00000(0000) knlGS:000000000000000 0\n [ 16.455557] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003 3\n [ 16.455961] CR2: 0000000000000030 CR3: 0000000102788004 CR4: 0000000000770ef 0\n [ 16.456459] PKRU: 5555555 4\n [ 16.456654] Call Trace :\n [ 16.456832] \u0026lt;TASK \u0026gt;\n [ 16.456989] ? __die+0x23/0x7 0\n [ 16.457215] ? page_fault_oops+0x180/0x4c 0\n [ 16.457508] ? __lock_acquire+0x3e6/0x249 0\n [ 16.457801] ? exc_page_fault+0x68/0x20 0\n [ 16.458080] ? asm_exc_page_fault+0x26/0x3 0\n [ 16.458389] ? smc_listen_work+0xc02/0x159 0\n [ 16.458689] ? smc_listen_work+0xc02/0x159 0\n [ 16.458987] ? lock_is_held_type+0x8f/0x10 0\n [ 16.459284] process_one_work+0x1ea/0x6d 0\n [ 16.459570] worker_thread+0x1c3/0x38 0\n [ 16.459839] ? __pfx_worker_thread+0x10/0x1 0\n [ 16.460144] kthread+0xe0/0x11 0\n [ 16.460372] ? __pfx_kthread+0x10/0x1 0\n [ 16.460640] ret_from_fork+0x31/0x5 0\n [ 16.460896] ? __pfx_kthread+0x10/0x1 0\n [ 16.461166] ret_from_fork_asm+0x1a/0x3 0\n [ 16.461453] \u0026lt;/TASK \u0026gt;\n [ 16.461616] Modules linked in: bpf_testmod(OE) [last unloaded: bpf_testmod(OE) ]\n [ 16.462134] CR2: 000000000000003 0\n [ 16.462380] ---[ end trace 0000000000000000 ]---\n [ 16.462710] RIP: 0010:smc_listen_work+0xc02/0x1590\n\nThe direct cause of this issue is that after smc_listen_out_connected(),\nnewclcsock-\u0026gt;sk may be NULL since it will releases the smcsk. Therefore,\nif the application closes the socket immediately after accept,\nnewclcsock-\u0026gt;sk can be NULL. A possible execution order could be as\nfollows:\n\nsmc_listen_work | userspace\n-----------------------------------------------------------------\nlock_sock(sk) |\nsmc_listen_out_connected() |\n| \\- smc_listen_out |\n| | \\- release_sock |\n | |- sk-\u0026gt;sk_data_ready() |\n | fd = accept();\n | close(fd);\n | \\- socket-\u0026gt;sk = NULL;\n/* newclcsock-\u0026gt;sk is NULL now */\nSMC_STAT_SERV_SUCC_INC(sock_net(newclcsock-\u0026gt;sk))\n\nSince smc_listen_out_connected() will not fail, simply swapping the order\nof the code can easily fix this issue.(CVE-2025-38734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Avoid a NULL pointer dereference\n\n[WHY]\nAlthough unlikely drm_atomic_get_new_connector_state() or\ndrm_atomic_get_old_connector_state() can return NULL.\n\n[HOW]\nCheck returns before dereference.\n\n(cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9)(CVE-2025-39693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls\n\nBoth the ACE and CSI driver are missing a mei_cldev_disable() call in\ntheir remove() function.\n\nThis causes the mei_cl client to stay part of the mei_device-\u0026gt;file_list\nlist even though its memory is freed by mei_cl_bus_dev_release() calling\nkfree(cldev-\u0026gt;cl).\n\nThis leads to a use-after-free when mei_vsc_remove() runs mei_stop()\nwhich first removes all mei bus devices calling mei_ace_remove() and\nmei_csi_remove() followed by mei_cl_bus_dev_release() and then calls\nmei_cl_all_disconnect() which walks over mei_device-\u0026gt;file_list dereferecing\nthe just freed cldev-\u0026gt;cl.\n\nAnd mei_vsc_remove() it self is run at shutdown because of the\nplatform_device_unregister(tp-\u0026gt;pdev) in vsc_tp_shutdown()\n\nWhen building a kernel with KASAN this leads to the following KASAN report:\n\n[ 106.634504] ==================================================================\n[ 106.634623] BUG: KASAN: slab-use-after-free in mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634683] Read of size 4 at addr ffff88819cb62018 by task systemd-shutdow/1\n[ 106.634729]\n[ 106.634767] Tainted: [E]=UNSIGNED_MODULE\n[ 106.634770] Hardware name: Dell Inc. XPS 16 9640/09CK4V, BIOS 1.12.0 02/10/2025\n[ 106.634773] Call Trace:\n[ 106.634777] \u0026lt;TASK\u0026gt;\n...\n[ 106.634871] kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:636)\n[ 106.634901] mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634921] mei_cl_all_disconnect (drivers/misc/mei/client.c:2165 (discriminator 4)) mei\n[ 106.634941] mei_reset (drivers/misc/mei/init.c:163) mei\n...\n[ 106.635042] mei_stop (drivers/misc/mei/init.c:348) mei\n[ 106.635062] mei_vsc_remove (drivers/misc/mei/mei_dev.h:784 drivers/misc/mei/platform-vsc.c:393) mei_vsc\n[ 106.635066] platform_remove (drivers/base/platform.c:1424)\n\nAdd the missing mei_cldev_disable() calls so that the mei_cl gets removed\nfrom mei_device-\u0026gt;file_list before it is freed to fix this.(CVE-2025-39711)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Revise __get_user() to probe user read access\n\nBecause of the way read access support is implemented, read access\ninterruptions are only triggered at privilege levels 2 and 3. The\nkernel executes at privilege level 0, so __get_user() never triggers\na read access interruption (code 26). Thus, it is currently possible\nfor user code to access a read protected address via a system call.\n\nFix this by probing read access rights at privilege level 3 (PRIV_USER)\nand setting __gu_err to -EFAULT (-14) if access isn\u0026apos;t allowed.\n\nNote the cmpiclr instruction does a 32-bit compare because COND macro\ndoesn\u0026apos;t work inside asm.(CVE-2025-39716)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: bno055: fix OOB access of hw_xlate array\n\nFix a potential out-of-bounds array access of the hw_xlate array in\nbno055.c.\n\nIn bno055_get_regmask(), hw_xlate was iterated over the length of the\nvals array instead of the length of the hw_xlate array. In the case of\nbno055_gyr_scale, the vals array is larger than the hw_xlate array,\nso this could result in an out-of-bounds access. In practice, this\nshouldn\u0026apos;t happen though because a match should always be found which\nbreaks out of the for loop before it iterates beyond the end of the\nhw_xlate array.\n\nBy adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be\nsure we are iterating over the correct length.(CVE-2025-39719)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/ism: fix concurrency management in ism_cmd()\n\nThe s390x ISM device data sheet clearly states that only one\nrequest-response sequence is allowable per ISM function at any point in\ntime. Unfortunately as of today the s390/ism driver in Linux does not\nhonor that requirement. This patch aims to rectify that.\n\nThis problem was discovered based on Aliaksei\u0026apos;s bug report which states\nthat for certain workloads the ISM functions end up entering error state\n(with PEC 2 as seen from the logs) after a while and as a consequence\nconnections handled by the respective function break, and for future\nconnection requests the ISM device is not considered -- given it is in a\ndysfunctional state. During further debugging PEC 3A was observed as\nwell.\n\nA kernel message like\n[ 1211.244319] zpci: 061a:00:00.0: Event 0x2 reports an error for PCI function 0x61a\nis a reliable indicator of the stated function entering error state\nwith PEC 2. Let me also point out that a kernel message like\n[ 1211.244325] zpci: 061a:00:00.0: The ism driver bound to the device does not support error recovery\nis a reliable indicator that the ISM function won\u0026apos;t be auto-recovered\nbecause the ISM driver currently lacks support for it.\n\nOn a technical level, without this synchronization, commands (inputs to\nthe FW) may be partially or fully overwritten (corrupted) by another CPU\ntrying to issue commands on the same function. There is hard evidence that\nthis can lead to DMB token values being used as DMB IOVAs, leading to\nPEC 2 PCI events indicating invalid DMA. But this is only one of the\nfailure modes imaginable. In theory even completely losing one command\nand executing another one twice and then trying to interpret the outputs\nas if the command we intended to execute was actually executed and not\nthe other one is also possible. Frankly, I don\u0026apos;t feel confident about\nproviding an exhaustive list of possible consequences.(CVE-2025-39726)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Optimize module load time by optimizing PLT/GOT counting\n\nWhen enabling CONFIG_KASAN, CONFIG_PREEMPT_VOLUNTARY_BUILD and\nCONFIG_PREEMPT_VOLUNTARY at the same time, there will be soft deadlock,\nthe relevant logs are as follows:\n\nrcu: INFO: rcu_sched self-detected stall on CPU\n...\nCall Trace:\n[\u0026lt;900000000024f9e4\u0026gt;] show_stack+0x5c/0x180\n[\u0026lt;90000000002482f4\u0026gt;] dump_stack_lvl+0x94/0xbc\n[\u0026lt;9000000000224544\u0026gt;] rcu_dump_cpu_stacks+0x1fc/0x280\n[\u0026lt;900000000037ac80\u0026gt;] rcu_sched_clock_irq+0x720/0xf88\n[\u0026lt;9000000000396c34\u0026gt;] update_process_times+0xb4/0x150\n[\u0026lt;90000000003b2474\u0026gt;] tick_nohz_handler+0xf4/0x250\n[\u0026lt;9000000000397e28\u0026gt;] __hrtimer_run_queues+0x1d0/0x428\n[\u0026lt;9000000000399b2c\u0026gt;] hrtimer_interrupt+0x214/0x538\n[\u0026lt;9000000000253634\u0026gt;] constant_timer_interrupt+0x64/0x80\n[\u0026lt;9000000000349938\u0026gt;] __handle_irq_event_percpu+0x78/0x1a0\n[\u0026lt;9000000000349a78\u0026gt;] handle_irq_event_percpu+0x18/0x88\n[\u0026lt;9000000000354c00\u0026gt;] handle_percpu_irq+0x90/0xf0\n[\u0026lt;9000000000348c74\u0026gt;] handle_irq_desc+0x94/0xb8\n[\u0026lt;9000000001012b28\u0026gt;] handle_cpu_irq+0x68/0xa0\n[\u0026lt;9000000001def8c0\u0026gt;] handle_loongarch_irq+0x30/0x48\n[\u0026lt;9000000001def958\u0026gt;] do_vint+0x80/0xd0\n[\u0026lt;9000000000268a0c\u0026gt;] kasan_mem_to_shadow.part.0+0x2c/0x2a0\n[\u0026lt;90000000006344f4\u0026gt;] __asan_load8+0x4c/0x120\n[\u0026lt;900000000025c0d0\u0026gt;] module_frob_arch_sections+0x5c8/0x6b8\n[\u0026lt;90000000003895f0\u0026gt;] load_module+0x9e0/0x2958\n[\u0026lt;900000000038b770\u0026gt;] __do_sys_init_module+0x208/0x2d0\n[\u0026lt;9000000001df0c34\u0026gt;] do_syscall+0x94/0x190\n[\u0026lt;900000000024d6fc\u0026gt;] handle_syscall+0xbc/0x158\n\nAfter analysis, this is because the slow speed of loading the amdgpu\nmodule leads to the long time occupation of the cpu and then the soft\ndeadlock.\n\nWhen loading a module, module_frob_arch_sections() tries to figure out\nthe number of PLTs/GOTs that will be needed to handle all the RELAs. It\nwill call the count_max_entries() to find in an out-of-order date which\ncounting algorithm has O(n^2) complexity.\n\nTo make it faster, we sort the relocation list by info and addend. That\nway, to check for a duplicate relocation, it just needs to compare with\nthe previous entry. This reduces the complexity of the algorithm to O(n\n log n), as done in commit d4e0340919fb (\u0026quot;arm64/module: Optimize module\nload time by optimizing PLT counting\u0026quot;). This gives sinificant reduction\nin module load time for modules with large number of relocations.\n\nAfter applying this patch, the soft deadlock problem has been solved,\nand the kernel starts normally without \u0026quot;Call Trace\u0026quot;.\n\nUsing the default configuration to test some modules, the results are as\nfollows:\n\nModule Size\nip_tables 36K\nfat 143K\nradeon 2.5MB\namdgpu 16MB\n\nWithout this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 54\t\t\t\t1221/84\namdgpu 1411\t\t\t4525/1098\n\nWith this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 22\t\t\t\t1221/84\namdgpu 45\t\t\t\t4525/1098(CVE-2025-39767)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Drop WARN_ON_ONCE() from flush_cache_vmap\n\nI have observed warning to occassionally trigger.(CVE-2025-39781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nARM: tegra: Use I/O memcpy to write to IRAM\n\nKasan crashes the kernel trying to check boundaries when using the\nnormal memcpy.(CVE-2025-39794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: hid-ntrig: fix unable to handle page fault in ntrig_report_version()\n\nin ntrig_report_version(), hdev parameter passed from hid_probe().\nsending descriptor to /dev/uhid can make hdev-\u0026gt;dev.parent-\u0026gt;parent to null\nif hdev-\u0026gt;dev.parent-\u0026gt;parent is null, usb_dev has\ninvalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned\nwhen usb_rcvctrlpipe() use usb_dev,it trigger\npage fault error for address(0xffffffffffffff58)\n\nadd null check logic to ntrig_report_version()\nbefore calling hid_to_usb_dev()(CVE-2025-39808)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: prevent release journal inode after journal shutdown\n\nBefore calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already\nbeen executed in ocfs2_dismount_volume(), so osb-\u0026gt;journal must be NULL. \nTherefore, the following calltrace will inevitably fail when it reaches\njbd2_journal_release_jbd_inode().\n\nocfs2_dismount_volume()-\u0026gt;\n ocfs2_delete_osb()-\u0026gt;\n ocfs2_free_slot_info()-\u0026gt;\n __ocfs2_free_slot_info()-\u0026gt;\n evict()-\u0026gt;\n ocfs2_evict_inode()-\u0026gt;\n ocfs2_clear_inode()-\u0026gt;\n\t jbd2_journal_release_jbd_inode(osb-\u0026gt;journal-\u0026gt;j_journal,\n\nAdding osb-\u0026gt;journal checks will prevent null-ptr-deref during the above\nexecution path.(CVE-2025-39842)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region()\n\nIn __iodyn_find_io_region(), pcmcia_make_resource() is assigned to\nres and used in pci_bus_alloc_resource(). There is a dereference of res\nin pci_bus_alloc_resource(), which could lead to a NULL pointer\ndereference on failure of pcmcia_make_resource().\n\nFix this bug by adding a check of res.(CVE-2025-39846)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: vhci: Prevent use-after-free by removing debugfs files early\n\nMove the creation of debugfs files into a dedicated function, and ensure\nthey are explicitly removed during vhci_release(), before associated\ndata structures are freed.\n\nPreviously, debugfs files such as \u0026quot;force_suspend\u0026quot;, \u0026quot;force_wakeup\u0026quot;, and\nothers were created under hdev-\u0026gt;debugfs but not removed in\nvhci_release(). Since vhci_release() frees the backing vhci_data\nstructure, any access to these files after release would result in\nuse-after-free errors.\n\nAlthough hdev-\u0026gt;debugfs is later freed in hci_release_dev(), user can\naccess files after vhci_data is freed but before hdev-\u0026gt;debugfs is\nreleased.(CVE-2025-39861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work\n\nThe brcmf_btcoex_detach() only shuts down the btcoex timer, if the\nflag timer_on is false. However, the brcmf_btcoex_timerfunc(), which\nruns as timer handler, sets timer_on to false. This creates critical\nrace conditions:\n\n1.If brcmf_btcoex_detach() is called while brcmf_btcoex_timerfunc()\nis executing, it may observe timer_on as false and skip the call to\ntimer_shutdown_sync().\n\n2.The brcmf_btcoex_timerfunc() may then reschedule the brcmf_btcoex_info\nworker after the cancel_work_sync() has been executed, resulting in\nuse-after-free bugs.\n\nThe use-after-free bugs occur in two distinct scenarios, depending on\nthe timing of when the brcmf_btcoex_info struct is freed relative to\nthe execution of its worker thread.\n\nScenario 1: Freed before the worker is scheduled\n\nThe brcmf_btcoex_info is deallocated before the worker is scheduled.\nA race condition can occur when schedule_work(\u0026amp;bt_local-\u0026gt;work) is\ncalled after the target memory has been freed. The sequence of events\nis detailed below:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... |\n kfree(cfg-\u0026gt;btcoex); // FREE |\n | schedule_work(\u0026amp;bt_local-\u0026gt;work); // USE\n\nScenario 2: Freed after the worker is scheduled\n\nThe brcmf_btcoex_info is freed after the worker has been scheduled\nbut before or during its execution. In this case, statements within\nthe brcmf_btcoex_handler() — such as the container_of macro and\nsubsequent dereferences of the brcmf_btcoex_info object will cause\na use-after-free access. The following timeline illustrates this\nscenario:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... | schedule_work(); // Reschedule\n |\n kfree(cfg-\u0026gt;btcoex); // FREE | brcmf_btcoex_handler() // Worker\n /* | btci = container_of(....); // USE\n The kfree() above could | ...\n also occur at any point | btci-\u0026gt; // USE\n during the worker\u0026apos;s execution|\n */ |\n\nTo resolve the race conditions, drop the conditional check and call\ntimer_shutdown_sync() directly. It can deactivate the timer reliably,\nregardless of its current state. Once stopped, the timer_on state is\nthen set to false.(CVE-2025-39863)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()\n\nPatch series \u0026quot;mm/damon: avoid divide-by-zero in DAMON module\u0026apos;s parameters\napplication\u0026quot;.\n\nDAMON\u0026apos;s RECLAIM and LRU_SORT modules perform no validation on\nuser-configured parameters during application, which may lead to\ndivision-by-zero errors.\n\nAvoid the divide-by-zero by adding validation checks when DAMON modules\nattempt to apply the parameters.\n\n\nThis patch (of 2):\n\nDuring the calculation of \u0026apos;hot_thres\u0026apos; and \u0026apos;cold_thres\u0026apos;, either\n\u0026apos;sample_interval\u0026apos; or \u0026apos;aggr_interval\u0026apos; is used as the divisor, which may\nlead to division-by-zero errors. Fix it by directly returning -EINVAL\nwhen such a case occurs. Additionally, since \u0026apos;aggr_interval\u0026apos; is already\nrequired to be set no smaller than \u0026apos;sample_interval\u0026apos; in damon_set_attrs(),\nonly the case where \u0026apos;sample_interval\u0026apos; is zero needs to be checked.(CVE-2025-39909)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()\n\nWhen creating a new scheme of DAMON_RECLAIM, the calculation of\n\u0026apos;min_age_region\u0026apos; uses \u0026apos;aggr_interval\u0026apos; as the divisor, which may lead to\ndivision-by-zero errors. Fix it by directly returning -EINVAL when such a\ncase occurs.(CVE-2025-39916)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm: bridge: anx7625: Fix NULL pointer dereference with early IRQ\n\nIf the interrupt occurs before resource initialization is complete, the\ninterrupt handler/worker may access uninitialized data such as the I2C\ntcpc_client device, potentially leading to NULL pointer dereference.(CVE-2025-39934)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: avoid buffer overflow in WID string configuration\n\nFix the following copy overflow warning identified by Smatch checker.\n\n drivers/net/wireless/microchip/wilc1000/wlan_cfg.c:184 wilc_wlan_parse_response_frame()\n error: \u0026apos;__memcpy()\u0026apos; \u0026apos;cfg-\u0026gt;s[i]-\u0026gt;str\u0026apos; copy overflow (512 vs 65537)\n\nThis patch introduces size check before accessing the memory buffer.\nThe checks are base on the WID type of received data from the firmware.\nFor WID string configuration, the size limit is determined by individual\nelement size in \u0026apos;struct wilc_cfg_str_vals\u0026apos; that is maintained in \u0026apos;len\u0026apos; field\nof \u0026apos;struct wilc_cfg_str\u0026apos;.(CVE-2025-39952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn\u0026apos;t valid\n\nSkip the WRMSR and HLT fastpaths in SVM\u0026apos;s VM-Exit handler if the next RIP\nisn\u0026apos;t valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn\u0026apos;t provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u0026lt;ffffffffc08b2527\u0026gt;] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u0026lt;ffffffffb4f62e32\u0026gt;] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u0026lt;/TASK\u0026gt;\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\u0026quot;KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn\u0026apos;t valid\u0026quot;), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).(CVE-2025-40038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix potential null deref in ext4_mb_init()\n\nIn ext4_mb_init(), ext4_mb_avg_fragment_size_destroy() may be called\nwhen sbi-\u0026gt;s_mb_avg_fragment_size remains uninitialized (e.g., if groupinfo\nslab cache allocation fails). Since ext4_mb_avg_fragment_size_destroy()\nlacks null pointer checking, this leads to a null pointer dereference.\n\n==================================================================\nEXT4-fs: no memory for groupinfo slab cache\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPGD 0 P4D 0\nOops: Oops: 0002 [#1] SMP PTI\nCPU:2 UID: 0 PID: 87 Comm:mount Not tainted 6.17.0-rc2 #1134 PREEMPT(none)\nRIP: 0010:_raw_spin_lock_irqsave+0x1b/0x40\nCall Trace:\n \u0026lt;TASK\u0026gt;\n xa_destroy+0x61/0x130\n ext4_mb_init+0x483/0x540\n __ext4_fill_super+0x116d/0x17b0\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n do_new_mount+0x197/0x300\n __x64_sys_mount+0x116/0x150\n do_syscall_64+0x50/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nTherefore, add necessary null check to ext4_mb_avg_fragment_size_destroy()\nto prevent this issue. The same fix is also applied to\next4_mb_largest_free_orders_destroy().(CVE-2025-40119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/i10nm: Skip DIMM enumeration on a disabled memory controller\n\nWhen loading the i10nm_edac driver on some Intel Granite Rapids servers,\na call trace may appear as follows:\n\n UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:453:16\n shift exponent -66 is negative\n ...\n __ubsan_handle_shift_out_of_bounds+0x1e3/0x390\n skx_get_dimm_info.cold+0x47/0xd40 [skx_edac_common]\n i10nm_get_dimm_config+0x23e/0x390 [i10nm_edac]\n skx_register_mci+0x159/0x220 [skx_edac_common]\n i10nm_init+0xcb0/0x1ff0 [i10nm_edac]\n ...\n\nThis occurs because some BIOS may disable a memory controller if there\naren\u0026apos;t any memory DIMMs populated on this memory controller. The DIMMMTR\nregister of this disabled memory controller contains the invalid value\n~0, resulting in the call trace above.\n\nFix this call trace by skipping DIMM enumeration on a disabled memory\ncontroller.(CVE-2025-40157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: quota: create dedicated workqueue for quota_release_work\n\nThere is a kernel panic due to WARN_ONCE when panic_on_warn is set.\n\nThis issue occurs when writeback is triggered due to sync call for an\nopened file(ie, writeback reason is WB_REASON_SYNC). When f2fs balance\nis needed at sync path, flush for quota_release_work is triggered.\nBy default quota_release_work is queued to \u0026quot;events_unbound\u0026quot; queue which\ndoes not have WQ_MEM_RECLAIM flag. During f2fs balance \u0026quot;writeback\u0026quot;\nworkqueue tries to flush quota_release_work causing kernel panic due to\nMEM_RECLAIM flag mismatch errors.\n\nThis patch creates dedicated workqueue with WQ_MEM_RECLAIM flag\nfor work quota_release_work.\n\n------------[ cut here ]------------\nWARNING: CPU: 4 PID: 14867 at kernel/workqueue.c:3721 check_flush_dependency+0x13c/0x148\nCall trace:\n check_flush_dependency+0x13c/0x148\n __flush_work+0xd0/0x398\n flush_delayed_work+0x44/0x5c\n dquot_writeback_dquots+0x54/0x318\n f2fs_do_quota_sync+0xb8/0x1a8\n f2fs_write_checkpoint+0x3cc/0x99c\n f2fs_gc+0x190/0x750\n f2fs_balance_fs+0x110/0x168\n f2fs_write_single_data_page+0x474/0x7dc\n f2fs_write_data_pages+0x7d0/0xd0c\n do_writepages+0xe0/0x2f4\n __writeback_single_inode+0x44/0x4ac\n writeback_sb_inodes+0x30c/0x538\n wb_writeback+0xf4/0x440\n wb_workfn+0x128/0x5d4\n process_scheduled_works+0x1c4/0x45c\n worker_thread+0x32c/0x3e8\n kthread+0x11c/0x1b0\n ret_from_fork+0x10/0x20\nKernel panic - not syncing: kernel: panic_on_warn set ...(CVE-2025-40196)\n\nIn the Linux kernel, the following vulnerability has been resolved: media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try(). v4l2_subdev_call_state_try() macro allocates a subdev state with __v4l2_subdev_state_alloc(), but does not check the returned value. If __v4l2_subdev_state_alloc fails, it returns an ERR_PTR, and that would cause v4l2_subdev_call_state_try() to crash. Add proper error handling to v4l2_subdev_call_state_try().(CVE-2025-40207)","status":"published","published":"2025-11-22T11:09:49Z","modified":"2026-08-18T01:19:20.918160913Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:44.957082Z"},{"id":"OESA-2025-2696","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\nmisc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error\n\nAfter devm_request_irq() fails with error in pci_endpoint_test_request_irq(),\nthe pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs\nhave been released.\n\nHowever, some requested IRQs remain unreleased, so there are still\n/proc/irq/* entries remaining, and this results in WARN() with the\nfollowing message:\n\n remove_proc_entry: removing non-empty directory \u0026apos;irq/30\u0026apos;, leaking at least \u0026apos;pci-endpoint-test.0\u0026apos;\n WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c\n\nTo solve this issue, set the number of remaining IRQs to test-\u0026gt;num_irqs,\nand release IRQs in advance by calling pci_endpoint_test_release_irq().\n\n[kwilczynski: commit log](CVE-2025-23140)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: csa unmap use uninterruptible lock\n\nAfter process exit to unmap csa and free GPU vm, if signal is accepted\nand then waiting to take vm lock is interrupted and return, it causes\nmemory leaking and below warning backtrace.\n\nChange to use uninterruptible wait lock fix the issue.\n\nWARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525\n amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n drm_file_free.part.0+0x1da/0x230 [drm]\n drm_close_helper.isra.0+0x65/0x70 [drm]\n drm_release+0x6a/0x120 [drm]\n amdgpu_drm_release+0x51/0x60 [amdgpu]\n __fput+0x9f/0x280\n ____fput+0xe/0x20\n task_work_run+0x67/0xa0\n do_exit+0x217/0x3c0\n do_group_exit+0x3b/0xb0\n get_signal+0x14a/0x8d0\n arch_do_signal_or_restart+0xde/0x100\n exit_to_user_mode_loop+0xc1/0x1a0\n exit_to_user_mode_prepare+0xf4/0x100\n syscall_exit_to_user_mode+0x17/0x40\n do_syscall_64+0x69/0xc0\n\n(cherry picked from commit 7dbbfb3c171a6f63b01165958629c9c26abf38ab)(CVE-2025-38011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: avoid NULL pointer dereference if no valid csum tree\n\n[BUG]\nWhen trying read-only scrub on a btrfs with rescue=idatacsums mount\noption, it will crash with the following call trace:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000208\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n CPU: 1 UID: 0 PID: 835 Comm: btrfs Tainted: G O 6.15.0-rc3-custom+ #236 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022\n RIP: 0010:btrfs_lookup_csums_bitmap+0x49/0x480 [btrfs]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n scrub_find_fill_first_stripe+0x35b/0x3d0 [btrfs]\n scrub_simple_mirror+0x175/0x290 [btrfs]\n scrub_stripe+0x5f7/0x6f0 [btrfs]\n scrub_chunk+0x9a/0x150 [btrfs]\n scrub_enumerate_chunks+0x333/0x660 [btrfs]\n btrfs_scrub_dev+0x23e/0x600 [btrfs]\n btrfs_ioctl+0x1dcf/0x2f80 [btrfs]\n __x64_sys_ioctl+0x97/0xc0\n do_syscall_64+0x4f/0x120\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n[CAUSE]\nMount option \u0026quot;rescue=idatacsums\u0026quot; will completely skip loading the csum\ntree, so that any data read will not find any data csum thus we will\nignore data checksum verification.\n\nNormally call sites utilizing csum tree will check the fs state flag\nNO_DATA_CSUMS bit, but unfortunately scrub does not check that bit at all.\n\nThis results in scrub to call btrfs_search_slot() on a NULL pointer\nand triggered above crash.\n\n[FIX]\nCheck both extent and csum tree root before doing any tree search.(CVE-2025-38059)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: holding cscfg_csdev_lock while removing cscfg from csdev\n\nThere\u0026apos;ll be possible race scenario for coresight config:\n\nCPU0 CPU1\n(perf enable) load module\n cscfg_load_config_sets()\n activate config. // sysfs\n (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\n lock(csdev-\u0026gt;cscfg_csdev_lock)\n deactivate config // sysfs\n (sys_activec_cnt == 0)\n cscfg_unload_config_sets()\n \u0026lt;iterating config_csdev_list\u0026gt; cscfg_remove_owned_csdev_configs()\n // here load config activate by CPU1\n unlock(csdev-\u0026gt;cscfg_csdev_lock)\n\niterating config_csdev_list could be raced with config_csdev_list\u0026apos;s\nentry delete.\n\nTo resolve this race , hold csdev-\u0026gt;cscfg_csdev_lock() while\ncscfg_remove_owned_csdev_configs()(CVE-2025-38132)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init()\n\ndevm_ioremap() returns NULL on error. Currently, mt7915_mmio_wed_init()\ndoes not check for this case, which results in a NULL pointer\ndereference.\n\nPrevent null pointer dereference in mt7915_mmio_wed_init().(CVE-2025-38155)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: handle hdr_first_de() return value\n\nThe hdr_first_de() function returns a pointer to a struct NTFS_DE. This\npointer may be NULL. To handle the NULL error effectively, it is important\nto implement an error handler. This will help manage potential errors\nconsistently.\n\nAdditionally, error handling for the return value already exists at other\npoints where this function is called.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-38167)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nexfat: fix double free in delayed_free\n\nThe double free could happen in the following path.\n\nexfat_create_upcase_table()\n exfat_create_upcase_table() : return error\n exfat_free_upcase_table() : free -\u0026gt;vol_utbl\n exfat_load_default_upcase_table : return error\n exfat_kill_sb()\n delayed_free()\n exfat_free_upcase_table() \u0026lt;--------- double free\nThis patch set -\u0026gt;vol_util as NULL after freeing it.(CVE-2025-38206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naoe: clean device rq_list in aoedev_downdev()\n\nAn aoe device\u0026apos;s rq_list contains accepted block requests that are\nwaiting to be transmitted to the aoe target. This queue was added as\npart of the conversion to blk_mq. However, the queue was not cleaned out\nwhen an aoe device is downed which caused blk_mq_freeze_queue() to sleep\nindefinitely waiting for those requests to complete, causing a hang. This\nfix cleans out the queue before calling blk_mq_freeze_queue().(CVE-2025-38326)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n\nRobert Morris reported:\n\n|If a malicious USB device pretends to be an Intersil p54 wifi\n|interface and generates an eeprom_readback message with a large\n|eeprom-\u0026gt;v1.len, p54_rx_eeprom_readback() will copy data from the\n|message beyond the end of priv-\u0026gt;eeprom.\n|\n|static void p54_rx_eeprom_readback(struct p54_common *priv,\n| struct sk_buff *skb)\n|{\n| struct p54_hdr *hdr = (struct p54_hdr *) skb-\u0026gt;data;\n| struct p54_eeprom_lm86 *eeprom = (struct p54_eeprom_lm86 *) hdr-\u0026gt;data;\n|\n| if (priv-\u0026gt;fw_var \u0026gt;= 0x509) {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v2.data,\n| le16_to_cpu(eeprom-\u0026gt;v2.len));\n| } else {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v1.data,\n| le16_to_cpu(eeprom-\u0026gt;v1.len));\n| }\n| [...]\n\nThe eeprom-\u0026gt;v{1,2}.len is set by the driver in p54_download_eeprom().\nThe device is supposed to provide the same length back to the driver.\nBut yes, it\u0026apos;s possible (like shown in the report) to alter the value\nto something that causes a crash/panic due to overrun.\n\nThis patch addresses the issue by adding the size to the common device\ncontext, so p54_rx_eeprom_readback no longer relies on possibly tampered\nvalues... That said, it also checks if the \u0026quot;firmware\u0026quot; altered the value\nand no longer copies them.\n\nThe one, small saving grace is: Before the driver tries to read the eeprom,\nit needs to upload \u0026gt;a\u0026lt; firmware. the vendor firmware has a proprietary\nlicense and as a reason, it is not present on most distributions by\ndefault.(CVE-2025-38348)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Disable migration in nf_hook_run_bpf().\n\nsyzbot reported that the netfilter bpf prog can be called without\nmigration disabled in xmit path.\n\nThen the assertion in __bpf_prog_run() fails, triggering the splat\nbelow. [0]\n\nLet\u0026apos;s use bpf_prog_run_pin_on_cpu() in nf_hook_run_bpf().\n\n[0]:\nBUG: assuming non migratable context at ./include/linux/filter.h:703\nin_atomic(): 0, irqs_disabled(): 0, migration_disabled() 0 pid: 5829, name: sshd-session\n3 locks held by sshd-session/5829:\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1667 [inline]\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: tcp_sendmsg+0x20/0x50 net/ipv4/tcp.c:1395\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: __ip_queue_xmit+0x69/0x26c0 net/ipv4/ip_output.c:470\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: nf_hook+0xb2/0x680 include/linux/netfilter.h:241\nCPU: 0 UID: 0 PID: 5829 Comm: sshd-session Not tainted 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n __cant_migrate kernel/sched/core.c:8860 [inline]\n __cant_migrate+0x1c7/0x250 kernel/sched/core.c:8834\n __bpf_prog_run include/linux/filter.h:703 [inline]\n bpf_prog_run include/linux/filter.h:725 [inline]\n nf_hook_run_bpf+0x83/0x1e0 net/netfilter/nf_bpf_link.c:20\n nf_hook_entry_hookfn include/linux/netfilter.h:157 [inline]\n nf_hook_slow+0xbb/0x200 net/netfilter/core.c:623\n nf_hook+0x370/0x680 include/linux/netfilter.h:272\n NF_HOOK_COND include/linux/netfilter.h:305 [inline]\n ip_output+0x1bc/0x2a0 net/ipv4/ip_output.c:433\n dst_output include/net/dst.h:459 [inline]\n ip_local_out net/ipv4/ip_output.c:129 [inline]\n __ip_queue_xmit+0x1d7d/0x26c0 net/ipv4/ip_output.c:527\n __tcp_transmit_skb+0x2686/0x3e90 net/ipv4/tcp_output.c:1479\n tcp_transmit_skb net/ipv4/tcp_output.c:1497 [inline]\n tcp_write_xmit+0x1274/0x84e0 net/ipv4/tcp_output.c:2838\n __tcp_push_pending_frames+0xaf/0x390 net/ipv4/tcp_output.c:3021\n tcp_push+0x225/0x700 net/ipv4/tcp.c:759\n tcp_sendmsg_locked+0x1870/0x42b0 net/ipv4/tcp.c:1359\n tcp_sendmsg+0x2e/0x50 net/ipv4/tcp.c:1396\n inet_sendmsg+0xb9/0x140 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n __sock_sendmsg net/socket.c:727 [inline]\n sock_write_iter+0x4aa/0x5b0 net/socket.c:1131\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0x6c7/0x1150 fs/read_write.c:686\n ksys_write+0x1f8/0x250 fs/read_write.c:738\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fe7d365d407\nCode: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 \u0026lt;5b\u0026gt; c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff\nRSP:(CVE-2025-38640)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: Don\u0026apos;t crash in stack_top() for tasks without ABI or vDSO\n\nNot all tasks have an ABI associated or vDSO mapped,\nfor example kthreads never do.\nIf such a task ever ends up calling stack_top(), it will derefence the\nNULL ABI pointer and crash.\n\nThis can for example happen when using kunit:\n\n mips_stack_top+0x28/0xc0\n arch_pick_mmap_layout+0x190/0x220\n kunit_vm_mmap_init+0xf8/0x138\n __kunit_add_resource+0x40/0xa8\n kunit_vm_mmap+0x88/0xd8\n usercopy_test_init+0xb8/0x240\n kunit_try_run_case+0x5c/0x1a8\n kunit_generic_run_threadfn_adapter+0x28/0x50\n kthread+0x118/0x240\n ret_from_kernel_thread+0x14/0x1c\n\nOnly dereference the ABI point if it is set.\n\nThe GIC page is also included as it is specific to the vDSO.\nAlso move the randomization adjustment into the same conditional.(CVE-2025-38696)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: linearize cloned gso packets in sctp_rcv\n\nA cloned head skb still shares these frag skbs in fraglist with the\noriginal head skb. It\u0026apos;s not safe to access these frag skbs.\n\nsyzbot reported two use-of-uninitialized-memory bugs caused by this:\n\n BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998\n sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331\n sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122\n __release_sock+0x1da/0x330 net/core/sock.c:3106\n release_sock+0x6b/0x250 net/core/sock.c:3660\n sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360\n sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885\n sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031\n inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:718 [inline]\n\nand\n\n BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331\n sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148\n __release_sock+0x1d3/0x330 net/core/sock.c:3213\n release_sock+0x6b/0x270 net/core/sock.c:3767\n sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367\n sctp_sendmsg_to_asoc+0x223a/0x2260 net/sctp/socket.c:1886\n sctp_sendmsg+0x3910/0x49f0 net/sctp/socket.c:2032\n inet_sendmsg+0x269/0x2a0 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n\nThis patch fixes it by linearizing cloned gso packets in sctp_rcv().(CVE-2025-38718)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix UAF on smcsk after smc_listen_out()\n\nBPF CI testing report a UAF issue:\n\n [ 16.446633] BUG: kernel NULL pointer dereference, address: 000000000000003 0\n [ 16.447134] #PF: supervisor read access in kernel mod e\n [ 16.447516] #PF: error_code(0x0000) - not-present pag e\n [ 16.447878] PGD 0 P4D 0\n [ 16.448063] Oops: Oops: 0000 [#1] PREEMPT SMP NOPT I\n [ 16.448409] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Tainted: G OE 6.13.0-rc3-g89e8a75fda73-dirty #4 2\n [ 16.449124] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODUL E\n [ 16.449502] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/201 4\n [ 16.450201] Workqueue: smc_hs_wq smc_listen_wor k\n [ 16.450531] RIP: 0010:smc_listen_work+0xc02/0x159 0\n [ 16.452158] RSP: 0018:ffffb5ab40053d98 EFLAGS: 0001024 6\n [ 16.452526] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 000000000000030 0\n [ 16.452994] RDX: 0000000000000280 RSI: 00003513840053f0 RDI: 000000000000000 0\n [ 16.453492] RBP: ffffa097808e3800 R08: ffffa09782dba1e0 R09: 000000000000000 5\n [ 16.453987] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa0978274640 0\n [ 16.454497] R13: 0000000000000000 R14: 0000000000000000 R15: ffffa09782d4092 0\n [ 16.454996] FS: 0000000000000000(0000) GS:ffffa097bbc00000(0000) knlGS:000000000000000 0\n [ 16.455557] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003 3\n [ 16.455961] CR2: 0000000000000030 CR3: 0000000102788004 CR4: 0000000000770ef 0\n [ 16.456459] PKRU: 5555555 4\n [ 16.456654] Call Trace :\n [ 16.456832] \u0026lt;TASK \u0026gt;\n [ 16.456989] ? __die+0x23/0x7 0\n [ 16.457215] ? page_fault_oops+0x180/0x4c 0\n [ 16.457508] ? __lock_acquire+0x3e6/0x249 0\n [ 16.457801] ? exc_page_fault+0x68/0x20 0\n [ 16.458080] ? asm_exc_page_fault+0x26/0x3 0\n [ 16.458389] ? smc_listen_work+0xc02/0x159 0\n [ 16.458689] ? smc_listen_work+0xc02/0x159 0\n [ 16.458987] ? lock_is_held_type+0x8f/0x10 0\n [ 16.459284] process_one_work+0x1ea/0x6d 0\n [ 16.459570] worker_thread+0x1c3/0x38 0\n [ 16.459839] ? __pfx_worker_thread+0x10/0x1 0\n [ 16.460144] kthread+0xe0/0x11 0\n [ 16.460372] ? __pfx_kthread+0x10/0x1 0\n [ 16.460640] ret_from_fork+0x31/0x5 0\n [ 16.460896] ? __pfx_kthread+0x10/0x1 0\n [ 16.461166] ret_from_fork_asm+0x1a/0x3 0\n [ 16.461453] \u0026lt;/TASK \u0026gt;\n [ 16.461616] Modules linked in: bpf_testmod(OE) [last unloaded: bpf_testmod(OE) ]\n [ 16.462134] CR2: 000000000000003 0\n [ 16.462380] ---[ end trace 0000000000000000 ]---\n [ 16.462710] RIP: 0010:smc_listen_work+0xc02/0x1590\n\nThe direct cause of this issue is that after smc_listen_out_connected(),\nnewclcsock-\u0026gt;sk may be NULL since it will releases the smcsk. Therefore,\nif the application closes the socket immediately after accept,\nnewclcsock-\u0026gt;sk can be NULL. A possible execution order could be as\nfollows:\n\nsmc_listen_work | userspace\n-----------------------------------------------------------------\nlock_sock(sk) |\nsmc_listen_out_connected() |\n| \\- smc_listen_out |\n| | \\- release_sock |\n | |- sk-\u0026gt;sk_data_ready() |\n | fd = accept();\n | close(fd);\n | \\- socket-\u0026gt;sk = NULL;\n/* newclcsock-\u0026gt;sk is NULL now */\nSMC_STAT_SERV_SUCC_INC(sock_net(newclcsock-\u0026gt;sk))\n\nSince smc_listen_out_connected() will not fail, simply swapping the order\nof the code can easily fix this issue.(CVE-2025-38734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Avoid a NULL pointer dereference\n\n[WHY]\nAlthough unlikely drm_atomic_get_new_connector_state() or\ndrm_atomic_get_old_connector_state() can return NULL.\n\n[HOW]\nCheck returns before dereference.\n\n(cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9)(CVE-2025-39693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls\n\nBoth the ACE and CSI driver are missing a mei_cldev_disable() call in\ntheir remove() function.\n\nThis causes the mei_cl client to stay part of the mei_device-\u0026gt;file_list\nlist even though its memory is freed by mei_cl_bus_dev_release() calling\nkfree(cldev-\u0026gt;cl).\n\nThis leads to a use-after-free when mei_vsc_remove() runs mei_stop()\nwhich first removes all mei bus devices calling mei_ace_remove() and\nmei_csi_remove() followed by mei_cl_bus_dev_release() and then calls\nmei_cl_all_disconnect() which walks over mei_device-\u0026gt;file_list dereferecing\nthe just freed cldev-\u0026gt;cl.\n\nAnd mei_vsc_remove() it self is run at shutdown because of the\nplatform_device_unregister(tp-\u0026gt;pdev) in vsc_tp_shutdown()\n\nWhen building a kernel with KASAN this leads to the following KASAN report:\n\n[ 106.634504] ==================================================================\n[ 106.634623] BUG: KASAN: slab-use-after-free in mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634683] Read of size 4 at addr ffff88819cb62018 by task systemd-shutdow/1\n[ 106.634729]\n[ 106.634767] Tainted: [E]=UNSIGNED_MODULE\n[ 106.634770] Hardware name: Dell Inc. XPS 16 9640/09CK4V, BIOS 1.12.0 02/10/2025\n[ 106.634773] Call Trace:\n[ 106.634777] \u0026lt;TASK\u0026gt;\n...\n[ 106.634871] kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:636)\n[ 106.634901] mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634921] mei_cl_all_disconnect (drivers/misc/mei/client.c:2165 (discriminator 4)) mei\n[ 106.634941] mei_reset (drivers/misc/mei/init.c:163) mei\n...\n[ 106.635042] mei_stop (drivers/misc/mei/init.c:348) mei\n[ 106.635062] mei_vsc_remove (drivers/misc/mei/mei_dev.h:784 drivers/misc/mei/platform-vsc.c:393) mei_vsc\n[ 106.635066] platform_remove (drivers/base/platform.c:1424)\n\nAdd the missing mei_cldev_disable() calls so that the mei_cl gets removed\nfrom mei_device-\u0026gt;file_list before it is freed to fix this.(CVE-2025-39711)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Revise __get_user() to probe user read access\n\nBecause of the way read access support is implemented, read access\ninterruptions are only triggered at privilege levels 2 and 3. The\nkernel executes at privilege level 0, so __get_user() never triggers\na read access interruption (code 26). Thus, it is currently possible\nfor user code to access a read protected address via a system call.\n\nFix this by probing read access rights at privilege level 3 (PRIV_USER)\nand setting __gu_err to -EFAULT (-14) if access isn\u0026apos;t allowed.\n\nNote the cmpiclr instruction does a 32-bit compare because COND macro\ndoesn\u0026apos;t work inside asm.(CVE-2025-39716)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: bno055: fix OOB access of hw_xlate array\n\nFix a potential out-of-bounds array access of the hw_xlate array in\nbno055.c.\n\nIn bno055_get_regmask(), hw_xlate was iterated over the length of the\nvals array instead of the length of the hw_xlate array. In the case of\nbno055_gyr_scale, the vals array is larger than the hw_xlate array,\nso this could result in an out-of-bounds access. In practice, this\nshouldn\u0026apos;t happen though because a match should always be found which\nbreaks out of the for loop before it iterates beyond the end of the\nhw_xlate array.\n\nBy adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be\nsure we are iterating over the correct length.(CVE-2025-39719)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/ism: fix concurrency management in ism_cmd()\n\nThe s390x ISM device data sheet clearly states that only one\nrequest-response sequence is allowable per ISM function at any point in\ntime. Unfortunately as of today the s390/ism driver in Linux does not\nhonor that requirement. This patch aims to rectify that.\n\nThis problem was discovered based on Aliaksei\u0026apos;s bug report which states\nthat for certain workloads the ISM functions end up entering error state\n(with PEC 2 as seen from the logs) after a while and as a consequence\nconnections handled by the respective function break, and for future\nconnection requests the ISM device is not considered -- given it is in a\ndysfunctional state. During further debugging PEC 3A was observed as\nwell.\n\nA kernel message like\n[ 1211.244319] zpci: 061a:00:00.0: Event 0x2 reports an error for PCI function 0x61a\nis a reliable indicator of the stated function entering error state\nwith PEC 2. Let me also point out that a kernel message like\n[ 1211.244325] zpci: 061a:00:00.0: The ism driver bound to the device does not support error recovery\nis a reliable indicator that the ISM function won\u0026apos;t be auto-recovered\nbecause the ISM driver currently lacks support for it.\n\nOn a technical level, without this synchronization, commands (inputs to\nthe FW) may be partially or fully overwritten (corrupted) by another CPU\ntrying to issue commands on the same function. There is hard evidence that\nthis can lead to DMB token values being used as DMB IOVAs, leading to\nPEC 2 PCI events indicating invalid DMA. But this is only one of the\nfailure modes imaginable. In theory even completely losing one command\nand executing another one twice and then trying to interpret the outputs\nas if the command we intended to execute was actually executed and not\nthe other one is also possible. Frankly, I don\u0026apos;t feel confident about\nproviding an exhaustive list of possible consequences.(CVE-2025-39726)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Optimize module load time by optimizing PLT/GOT counting\n\nWhen enabling CONFIG_KASAN, CONFIG_PREEMPT_VOLUNTARY_BUILD and\nCONFIG_PREEMPT_VOLUNTARY at the same time, there will be soft deadlock,\nthe relevant logs are as follows:\n\nrcu: INFO: rcu_sched self-detected stall on CPU\n...\nCall Trace:\n[\u0026lt;900000000024f9e4\u0026gt;] show_stack+0x5c/0x180\n[\u0026lt;90000000002482f4\u0026gt;] dump_stack_lvl+0x94/0xbc\n[\u0026lt;9000000000224544\u0026gt;] rcu_dump_cpu_stacks+0x1fc/0x280\n[\u0026lt;900000000037ac80\u0026gt;] rcu_sched_clock_irq+0x720/0xf88\n[\u0026lt;9000000000396c34\u0026gt;] update_process_times+0xb4/0x150\n[\u0026lt;90000000003b2474\u0026gt;] tick_nohz_handler+0xf4/0x250\n[\u0026lt;9000000000397e28\u0026gt;] __hrtimer_run_queues+0x1d0/0x428\n[\u0026lt;9000000000399b2c\u0026gt;] hrtimer_interrupt+0x214/0x538\n[\u0026lt;9000000000253634\u0026gt;] constant_timer_interrupt+0x64/0x80\n[\u0026lt;9000000000349938\u0026gt;] __handle_irq_event_percpu+0x78/0x1a0\n[\u0026lt;9000000000349a78\u0026gt;] handle_irq_event_percpu+0x18/0x88\n[\u0026lt;9000000000354c00\u0026gt;] handle_percpu_irq+0x90/0xf0\n[\u0026lt;9000000000348c74\u0026gt;] handle_irq_desc+0x94/0xb8\n[\u0026lt;9000000001012b28\u0026gt;] handle_cpu_irq+0x68/0xa0\n[\u0026lt;9000000001def8c0\u0026gt;] handle_loongarch_irq+0x30/0x48\n[\u0026lt;9000000001def958\u0026gt;] do_vint+0x80/0xd0\n[\u0026lt;9000000000268a0c\u0026gt;] kasan_mem_to_shadow.part.0+0x2c/0x2a0\n[\u0026lt;90000000006344f4\u0026gt;] __asan_load8+0x4c/0x120\n[\u0026lt;900000000025c0d0\u0026gt;] module_frob_arch_sections+0x5c8/0x6b8\n[\u0026lt;90000000003895f0\u0026gt;] load_module+0x9e0/0x2958\n[\u0026lt;900000000038b770\u0026gt;] __do_sys_init_module+0x208/0x2d0\n[\u0026lt;9000000001df0c34\u0026gt;] do_syscall+0x94/0x190\n[\u0026lt;900000000024d6fc\u0026gt;] handle_syscall+0xbc/0x158\n\nAfter analysis, this is because the slow speed of loading the amdgpu\nmodule leads to the long time occupation of the cpu and then the soft\ndeadlock.\n\nWhen loading a module, module_frob_arch_sections() tries to figure out\nthe number of PLTs/GOTs that will be needed to handle all the RELAs. It\nwill call the count_max_entries() to find in an out-of-order date which\ncounting algorithm has O(n^2) complexity.\n\nTo make it faster, we sort the relocation list by info and addend. That\nway, to check for a duplicate relocation, it just needs to compare with\nthe previous entry. This reduces the complexity of the algorithm to O(n\n log n), as done in commit d4e0340919fb (\u0026quot;arm64/module: Optimize module\nload time by optimizing PLT counting\u0026quot;). This gives sinificant reduction\nin module load time for modules with large number of relocations.\n\nAfter applying this patch, the soft deadlock problem has been solved,\nand the kernel starts normally without \u0026quot;Call Trace\u0026quot;.\n\nUsing the default configuration to test some modules, the results are as\nfollows:\n\nModule Size\nip_tables 36K\nfat 143K\nradeon 2.5MB\namdgpu 16MB\n\nWithout this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 54\t\t\t\t1221/84\namdgpu 1411\t\t\t4525/1098\n\nWith this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 22\t\t\t\t1221/84\namdgpu 45\t\t\t\t4525/1098(CVE-2025-39767)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Drop WARN_ON_ONCE() from flush_cache_vmap\n\nI have observed warning to occassionally trigger.(CVE-2025-39781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nARM: tegra: Use I/O memcpy to write to IRAM\n\nKasan crashes the kernel trying to check boundaries when using the\nnormal memcpy.(CVE-2025-39794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: hid-ntrig: fix unable to handle page fault in ntrig_report_version()\n\nin ntrig_report_version(), hdev parameter passed from hid_probe().\nsending descriptor to /dev/uhid can make hdev-\u0026gt;dev.parent-\u0026gt;parent to null\nif hdev-\u0026gt;dev.parent-\u0026gt;parent is null, usb_dev has\ninvalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned\nwhen usb_rcvctrlpipe() use usb_dev,it trigger\npage fault error for address(0xffffffffffffff58)\n\nadd null check logic to ntrig_report_version()\nbefore calling hid_to_usb_dev()(CVE-2025-39808)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: prevent release journal inode after journal shutdown\n\nBefore calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already\nbeen executed in ocfs2_dismount_volume(), so osb-\u0026gt;journal must be NULL. \nTherefore, the following calltrace will inevitably fail when it reaches\njbd2_journal_release_jbd_inode().\n\nocfs2_dismount_volume()-\u0026gt;\n ocfs2_delete_osb()-\u0026gt;\n ocfs2_free_slot_info()-\u0026gt;\n __ocfs2_free_slot_info()-\u0026gt;\n evict()-\u0026gt;\n ocfs2_evict_inode()-\u0026gt;\n ocfs2_clear_inode()-\u0026gt;\n\t jbd2_journal_release_jbd_inode(osb-\u0026gt;journal-\u0026gt;j_journal,\n\nAdding osb-\u0026gt;journal checks will prevent null-ptr-deref during the above\nexecution path.(CVE-2025-39842)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region()\n\nIn __iodyn_find_io_region(), pcmcia_make_resource() is assigned to\nres and used in pci_bus_alloc_resource(). There is a dereference of res\nin pci_bus_alloc_resource(), which could lead to a NULL pointer\ndereference on failure of pcmcia_make_resource().\n\nFix this bug by adding a check of res.(CVE-2025-39846)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: vhci: Prevent use-after-free by removing debugfs files early\n\nMove the creation of debugfs files into a dedicated function, and ensure\nthey are explicitly removed during vhci_release(), before associated\ndata structures are freed.\n\nPreviously, debugfs files such as \u0026quot;force_suspend\u0026quot;, \u0026quot;force_wakeup\u0026quot;, and\nothers were created under hdev-\u0026gt;debugfs but not removed in\nvhci_release(). Since vhci_release() frees the backing vhci_data\nstructure, any access to these files after release would result in\nuse-after-free errors.\n\nAlthough hdev-\u0026gt;debugfs is later freed in hci_release_dev(), user can\naccess files after vhci_data is freed but before hdev-\u0026gt;debugfs is\nreleased.(CVE-2025-39861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work\n\nThe brcmf_btcoex_detach() only shuts down the btcoex timer, if the\nflag timer_on is false. However, the brcmf_btcoex_timerfunc(), which\nruns as timer handler, sets timer_on to false. This creates critical\nrace conditions:\n\n1.If brcmf_btcoex_detach() is called while brcmf_btcoex_timerfunc()\nis executing, it may observe timer_on as false and skip the call to\ntimer_shutdown_sync().\n\n2.The brcmf_btcoex_timerfunc() may then reschedule the brcmf_btcoex_info\nworker after the cancel_work_sync() has been executed, resulting in\nuse-after-free bugs.\n\nThe use-after-free bugs occur in two distinct scenarios, depending on\nthe timing of when the brcmf_btcoex_info struct is freed relative to\nthe execution of its worker thread.\n\nScenario 1: Freed before the worker is scheduled\n\nThe brcmf_btcoex_info is deallocated before the worker is scheduled.\nA race condition can occur when schedule_work(\u0026amp;bt_local-\u0026gt;work) is\ncalled after the target memory has been freed. The sequence of events\nis detailed below:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... |\n kfree(cfg-\u0026gt;btcoex); // FREE |\n | schedule_work(\u0026amp;bt_local-\u0026gt;work); // USE\n\nScenario 2: Freed after the worker is scheduled\n\nThe brcmf_btcoex_info is freed after the worker has been scheduled\nbut before or during its execution. In this case, statements within\nthe brcmf_btcoex_handler() — such as the container_of macro and\nsubsequent dereferences of the brcmf_btcoex_info object will cause\na use-after-free access. The following timeline illustrates this\nscenario:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... | schedule_work(); // Reschedule\n |\n kfree(cfg-\u0026gt;btcoex); // FREE | brcmf_btcoex_handler() // Worker\n /* | btci = container_of(....); // USE\n The kfree() above could | ...\n also occur at any point | btci-\u0026gt; // USE\n during the worker\u0026apos;s execution|\n */ |\n\nTo resolve the race conditions, drop the conditional check and call\ntimer_shutdown_sync() directly. It can deactivate the timer reliably,\nregardless of its current state. Once stopped, the timer_on state is\nthen set to false.(CVE-2025-39863)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()\n\nPatch series \u0026quot;mm/damon: avoid divide-by-zero in DAMON module\u0026apos;s parameters\napplication\u0026quot;.\n\nDAMON\u0026apos;s RECLAIM and LRU_SORT modules perform no validation on\nuser-configured parameters during application, which may lead to\ndivision-by-zero errors.\n\nAvoid the divide-by-zero by adding validation checks when DAMON modules\nattempt to apply the parameters.\n\n\nThis patch (of 2):\n\nDuring the calculation of \u0026apos;hot_thres\u0026apos; and \u0026apos;cold_thres\u0026apos;, either\n\u0026apos;sample_interval\u0026apos; or \u0026apos;aggr_interval\u0026apos; is used as the divisor, which may\nlead to division-by-zero errors. Fix it by directly returning -EINVAL\nwhen such a case occurs. Additionally, since \u0026apos;aggr_interval\u0026apos; is already\nrequired to be set no smaller than \u0026apos;sample_interval\u0026apos; in damon_set_attrs(),\nonly the case where \u0026apos;sample_interval\u0026apos; is zero needs to be checked.(CVE-2025-39909)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()\n\nWhen creating a new scheme of DAMON_RECLAIM, the calculation of\n\u0026apos;min_age_region\u0026apos; uses \u0026apos;aggr_interval\u0026apos; as the divisor, which may lead to\ndivision-by-zero errors. Fix it by directly returning -EINVAL when such a\ncase occurs.(CVE-2025-39916)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm: bridge: anx7625: Fix NULL pointer dereference with early IRQ\n\nIf the interrupt occurs before resource initialization is complete, the\ninterrupt handler/worker may access uninitialized data such as the I2C\ntcpc_client device, potentially leading to NULL pointer dereference.(CVE-2025-39934)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: avoid buffer overflow in WID string configuration\n\nFix the following copy overflow warning identified by Smatch checker.\n\n drivers/net/wireless/microchip/wilc1000/wlan_cfg.c:184 wilc_wlan_parse_response_frame()\n error: \u0026apos;__memcpy()\u0026apos; \u0026apos;cfg-\u0026gt;s[i]-\u0026gt;str\u0026apos; copy overflow (512 vs 65537)\n\nThis patch introduces size check before accessing the memory buffer.\nThe checks are base on the WID type of received data from the firmware.\nFor WID string configuration, the size limit is determined by individual\nelement size in \u0026apos;struct wilc_cfg_str_vals\u0026apos; that is maintained in \u0026apos;len\u0026apos; field\nof \u0026apos;struct wilc_cfg_str\u0026apos;.(CVE-2025-39952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn\u0026apos;t valid\n\nSkip the WRMSR and HLT fastpaths in SVM\u0026apos;s VM-Exit handler if the next RIP\nisn\u0026apos;t valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn\u0026apos;t provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u0026lt;ffffffffc08b2527\u0026gt;] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u0026lt;ffffffffb4f62e32\u0026gt;] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u0026lt;/TASK\u0026gt;\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\u0026quot;KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn\u0026apos;t valid\u0026quot;), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).(CVE-2025-40038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix potential null deref in ext4_mb_init()\n\nIn ext4_mb_init(), ext4_mb_avg_fragment_size_destroy() may be called\nwhen sbi-\u0026gt;s_mb_avg_fragment_size remains uninitialized (e.g., if groupinfo\nslab cache allocation fails). Since ext4_mb_avg_fragment_size_destroy()\nlacks null pointer checking, this leads to a null pointer dereference.\n\n==================================================================\nEXT4-fs: no memory for groupinfo slab cache\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPGD 0 P4D 0\nOops: Oops: 0002 [#1] SMP PTI\nCPU:2 UID: 0 PID: 87 Comm:mount Not tainted 6.17.0-rc2 #1134 PREEMPT(none)\nRIP: 0010:_raw_spin_lock_irqsave+0x1b/0x40\nCall Trace:\n \u0026lt;TASK\u0026gt;\n xa_destroy+0x61/0x130\n ext4_mb_init+0x483/0x540\n __ext4_fill_super+0x116d/0x17b0\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n do_new_mount+0x197/0x300\n __x64_sys_mount+0x116/0x150\n do_syscall_64+0x50/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nTherefore, add necessary null check to ext4_mb_avg_fragment_size_destroy()\nto prevent this issue. The same fix is also applied to\next4_mb_largest_free_orders_destroy().(CVE-2025-40119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/i10nm: Skip DIMM enumeration on a disabled memory controller\n\nWhen loading the i10nm_edac driver on some Intel Granite Rapids servers,\na call trace may appear as follows:\n\n UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:453:16\n shift exponent -66 is negative\n ...\n __ubsan_handle_shift_out_of_bounds+0x1e3/0x390\n skx_get_dimm_info.cold+0x47/0xd40 [skx_edac_common]\n i10nm_get_dimm_config+0x23e/0x390 [i10nm_edac]\n skx_register_mci+0x159/0x220 [skx_edac_common]\n i10nm_init+0xcb0/0x1ff0 [i10nm_edac]\n ...\n\nThis occurs because some BIOS may disable a memory controller if there\naren\u0026apos;t any memory DIMMs populated on this memory controller. The DIMMMTR\nregister of this disabled memory controller contains the invalid value\n~0, resulting in the call trace above.\n\nFix this call trace by skipping DIMM enumeration on a disabled memory\ncontroller.(CVE-2025-40157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: quota: create dedicated workqueue for quota_release_work\n\nThere is a kernel panic due to WARN_ONCE when panic_on_warn is set.\n\nThis issue occurs when writeback is triggered due to sync call for an\nopened file(ie, writeback reason is WB_REASON_SYNC). When f2fs balance\nis needed at sync path, flush for quota_release_work is triggered.\nBy default quota_release_work is queued to \u0026quot;events_unbound\u0026quot; queue which\ndoes not have WQ_MEM_RECLAIM flag. During f2fs balance \u0026quot;writeback\u0026quot;\nworkqueue tries to flush quota_release_work causing kernel panic due to\nMEM_RECLAIM flag mismatch errors.\n\nThis patch creates dedicated workqueue with WQ_MEM_RECLAIM flag\nfor work quota_release_work.\n\n------------[ cut here ]------------\nWARNING: CPU: 4 PID: 14867 at kernel/workqueue.c:3721 check_flush_dependency+0x13c/0x148\nCall trace:\n check_flush_dependency+0x13c/0x148\n __flush_work+0xd0/0x398\n flush_delayed_work+0x44/0x5c\n dquot_writeback_dquots+0x54/0x318\n f2fs_do_quota_sync+0xb8/0x1a8\n f2fs_write_checkpoint+0x3cc/0x99c\n f2fs_gc+0x190/0x750\n f2fs_balance_fs+0x110/0x168\n f2fs_write_single_data_page+0x474/0x7dc\n f2fs_write_data_pages+0x7d0/0xd0c\n do_writepages+0xe0/0x2f4\n __writeback_single_inode+0x44/0x4ac\n writeback_sb_inodes+0x30c/0x538\n wb_writeback+0xf4/0x440\n wb_workfn+0x128/0x5d4\n process_scheduled_works+0x1c4/0x45c\n worker_thread+0x32c/0x3e8\n kthread+0x11c/0x1b0\n ret_from_fork+0x10/0x20\nKernel panic - not syncing: kernel: panic_on_warn set ...(CVE-2025-40196)\n\nIn the Linux kernel, the following vulnerability has been resolved: media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try(). v4l2_subdev_call_state_try() macro allocates a subdev state with __v4l2_subdev_state_alloc(), but does not check the returned value. If __v4l2_subdev_state_alloc fails, it returns an ERR_PTR, and that would cause v4l2_subdev_call_state_try() to crash. Add proper error handling to v4l2_subdev_call_state_try().(CVE-2025-40207)","status":"published","published":"2025-11-22T11:09:49Z","modified":"2026-08-18T01:19:20.918260397Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:44.957082Z"},{"id":"OESA-2025-2700","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\nmisc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error\n\nAfter devm_request_irq() fails with error in pci_endpoint_test_request_irq(),\nthe pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs\nhave been released.\n\nHowever, some requested IRQs remain unreleased, so there are still\n/proc/irq/* entries remaining, and this results in WARN() with the\nfollowing message:\n\n remove_proc_entry: removing non-empty directory \u0026apos;irq/30\u0026apos;, leaking at least \u0026apos;pci-endpoint-test.0\u0026apos;\n WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c\n\nTo solve this issue, set the number of remaining IRQs to test-\u0026gt;num_irqs,\nand release IRQs in advance by calling pci_endpoint_test_release_irq().\n\n[kwilczynski: commit log](CVE-2025-23140)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: avoid NULL pointer dereference if no valid csum tree\n\n[BUG]\nWhen trying read-only scrub on a btrfs with rescue=idatacsums mount\noption, it will crash with the following call trace:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000208\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n CPU: 1 UID: 0 PID: 835 Comm: btrfs Tainted: G O 6.15.0-rc3-custom+ #236 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022\n RIP: 0010:btrfs_lookup_csums_bitmap+0x49/0x480 [btrfs]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n scrub_find_fill_first_stripe+0x35b/0x3d0 [btrfs]\n scrub_simple_mirror+0x175/0x290 [btrfs]\n scrub_stripe+0x5f7/0x6f0 [btrfs]\n scrub_chunk+0x9a/0x150 [btrfs]\n scrub_enumerate_chunks+0x333/0x660 [btrfs]\n btrfs_scrub_dev+0x23e/0x600 [btrfs]\n btrfs_ioctl+0x1dcf/0x2f80 [btrfs]\n __x64_sys_ioctl+0x97/0xc0\n do_syscall_64+0x4f/0x120\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n[CAUSE]\nMount option \u0026quot;rescue=idatacsums\u0026quot; will completely skip loading the csum\ntree, so that any data read will not find any data csum thus we will\nignore data checksum verification.\n\nNormally call sites utilizing csum tree will check the fs state flag\nNO_DATA_CSUMS bit, but unfortunately scrub does not check that bit at all.\n\nThis results in scrub to call btrfs_search_slot() on a NULL pointer\nand triggered above crash.\n\n[FIX]\nCheck both extent and csum tree root before doing any tree search.(CVE-2025-38059)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: holding cscfg_csdev_lock while removing cscfg from csdev\n\nThere\u0026apos;ll be possible race scenario for coresight config:\n\nCPU0 CPU1\n(perf enable) load module\n cscfg_load_config_sets()\n activate config. // sysfs\n (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\n lock(csdev-\u0026gt;cscfg_csdev_lock)\n deactivate config // sysfs\n (sys_activec_cnt == 0)\n cscfg_unload_config_sets()\n \u0026lt;iterating config_csdev_list\u0026gt; cscfg_remove_owned_csdev_configs()\n // here load config activate by CPU1\n unlock(csdev-\u0026gt;cscfg_csdev_lock)\n\niterating config_csdev_list could be raced with config_csdev_list\u0026apos;s\nentry delete.\n\nTo resolve this race , hold csdev-\u0026gt;cscfg_csdev_lock() while\ncscfg_remove_owned_csdev_configs()(CVE-2025-38132)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7915: Fix null-ptr-deref in mt7915_mmio_wed_init()\n\ndevm_ioremap() returns NULL on error. Currently, mt7915_mmio_wed_init()\ndoes not check for this case, which results in a NULL pointer\ndereference.\n\nPrevent null pointer dereference in mt7915_mmio_wed_init().(CVE-2025-38155)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: handle hdr_first_de() return value\n\nThe hdr_first_de() function returns a pointer to a struct NTFS_DE. This\npointer may be NULL. To handle the NULL error effectively, it is important\nto implement an error handler. This will help manage potential errors\nconsistently.\n\nAdditionally, error handling for the return value already exists at other\npoints where this function is called.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-38167)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nexfat: fix double free in delayed_free\n\nThe double free could happen in the following path.\n\nexfat_create_upcase_table()\n exfat_create_upcase_table() : return error\n exfat_free_upcase_table() : free -\u0026gt;vol_utbl\n exfat_load_default_upcase_table : return error\n exfat_kill_sb()\n delayed_free()\n exfat_free_upcase_table() \u0026lt;--------- double free\nThis patch set -\u0026gt;vol_util as NULL after freeing it.(CVE-2025-38206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naoe: clean device rq_list in aoedev_downdev()\n\nAn aoe device\u0026apos;s rq_list contains accepted block requests that are\nwaiting to be transmitted to the aoe target. This queue was added as\npart of the conversion to blk_mq. However, the queue was not cleaned out\nwhen an aoe device is downed which caused blk_mq_freeze_queue() to sleep\nindefinitely waiting for those requests to complete, causing a hang. This\nfix cleans out the queue before calling blk_mq_freeze_queue().(CVE-2025-38326)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n\nRobert Morris reported:\n\n|If a malicious USB device pretends to be an Intersil p54 wifi\n|interface and generates an eeprom_readback message with a large\n|eeprom-\u0026gt;v1.len, p54_rx_eeprom_readback() will copy data from the\n|message beyond the end of priv-\u0026gt;eeprom.\n|\n|static void p54_rx_eeprom_readback(struct p54_common *priv,\n| struct sk_buff *skb)\n|{\n| struct p54_hdr *hdr = (struct p54_hdr *) skb-\u0026gt;data;\n| struct p54_eeprom_lm86 *eeprom = (struct p54_eeprom_lm86 *) hdr-\u0026gt;data;\n|\n| if (priv-\u0026gt;fw_var \u0026gt;= 0x509) {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v2.data,\n| le16_to_cpu(eeprom-\u0026gt;v2.len));\n| } else {\n| memcpy(priv-\u0026gt;eeprom, eeprom-\u0026gt;v1.data,\n| le16_to_cpu(eeprom-\u0026gt;v1.len));\n| }\n| [...]\n\nThe eeprom-\u0026gt;v{1,2}.len is set by the driver in p54_download_eeprom().\nThe device is supposed to provide the same length back to the driver.\nBut yes, it\u0026apos;s possible (like shown in the report) to alter the value\nto something that causes a crash/panic due to overrun.\n\nThis patch addresses the issue by adding the size to the common device\ncontext, so p54_rx_eeprom_readback no longer relies on possibly tampered\nvalues... That said, it also checks if the \u0026quot;firmware\u0026quot; altered the value\nand no longer copies them.\n\nThe one, small saving grace is: Before the driver tries to read the eeprom,\nit needs to upload \u0026gt;a\u0026lt; firmware. the vendor firmware has a proprietary\nlicense and as a reason, it is not present on most distributions by\ndefault.(CVE-2025-38348)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Disable migration in nf_hook_run_bpf().\n\nsyzbot reported that the netfilter bpf prog can be called without\nmigration disabled in xmit path.\n\nThen the assertion in __bpf_prog_run() fails, triggering the splat\nbelow. [0]\n\nLet\u0026apos;s use bpf_prog_run_pin_on_cpu() in nf_hook_run_bpf().\n\n[0]:\nBUG: assuming non migratable context at ./include/linux/filter.h:703\nin_atomic(): 0, irqs_disabled(): 0, migration_disabled() 0 pid: 5829, name: sshd-session\n3 locks held by sshd-session/5829:\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1667 [inline]\n #0: ffff88807b4e4218 (sk_lock-AF_INET){+.+.}-{0:0}, at: tcp_sendmsg+0x20/0x50 net/ipv4/tcp.c:1395\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #1: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: __ip_queue_xmit+0x69/0x26c0 net/ipv4/ip_output.c:470\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]\n #2: ffffffff8e5c4e00 (rcu_read_lock){....}-{1:3}, at: nf_hook+0xb2/0x680 include/linux/netfilter.h:241\nCPU: 0 UID: 0 PID: 5829 Comm: sshd-session Not tainted 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n __cant_migrate kernel/sched/core.c:8860 [inline]\n __cant_migrate+0x1c7/0x250 kernel/sched/core.c:8834\n __bpf_prog_run include/linux/filter.h:703 [inline]\n bpf_prog_run include/linux/filter.h:725 [inline]\n nf_hook_run_bpf+0x83/0x1e0 net/netfilter/nf_bpf_link.c:20\n nf_hook_entry_hookfn include/linux/netfilter.h:157 [inline]\n nf_hook_slow+0xbb/0x200 net/netfilter/core.c:623\n nf_hook+0x370/0x680 include/linux/netfilter.h:272\n NF_HOOK_COND include/linux/netfilter.h:305 [inline]\n ip_output+0x1bc/0x2a0 net/ipv4/ip_output.c:433\n dst_output include/net/dst.h:459 [inline]\n ip_local_out net/ipv4/ip_output.c:129 [inline]\n __ip_queue_xmit+0x1d7d/0x26c0 net/ipv4/ip_output.c:527\n __tcp_transmit_skb+0x2686/0x3e90 net/ipv4/tcp_output.c:1479\n tcp_transmit_skb net/ipv4/tcp_output.c:1497 [inline]\n tcp_write_xmit+0x1274/0x84e0 net/ipv4/tcp_output.c:2838\n __tcp_push_pending_frames+0xaf/0x390 net/ipv4/tcp_output.c:3021\n tcp_push+0x225/0x700 net/ipv4/tcp.c:759\n tcp_sendmsg_locked+0x1870/0x42b0 net/ipv4/tcp.c:1359\n tcp_sendmsg+0x2e/0x50 net/ipv4/tcp.c:1396\n inet_sendmsg+0xb9/0x140 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n __sock_sendmsg net/socket.c:727 [inline]\n sock_write_iter+0x4aa/0x5b0 net/socket.c:1131\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0x6c7/0x1150 fs/read_write.c:686\n ksys_write+0x1f8/0x250 fs/read_write.c:738\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fe7d365d407\nCode: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 \u0026lt;5b\u0026gt; c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff\nRSP:(CVE-2025-38640)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: Don\u0026apos;t crash in stack_top() for tasks without ABI or vDSO\n\nNot all tasks have an ABI associated or vDSO mapped,\nfor example kthreads never do.\nIf such a task ever ends up calling stack_top(), it will derefence the\nNULL ABI pointer and crash.\n\nThis can for example happen when using kunit:\n\n mips_stack_top+0x28/0xc0\n arch_pick_mmap_layout+0x190/0x220\n kunit_vm_mmap_init+0xf8/0x138\n __kunit_add_resource+0x40/0xa8\n kunit_vm_mmap+0x88/0xd8\n usercopy_test_init+0xb8/0x240\n kunit_try_run_case+0x5c/0x1a8\n kunit_generic_run_threadfn_adapter+0x28/0x50\n kthread+0x118/0x240\n ret_from_kernel_thread+0x14/0x1c\n\nOnly dereference the ABI point if it is set.\n\nThe GIC page is also included as it is specific to the vDSO.\nAlso move the randomization adjustment into the same conditional.(CVE-2025-38696)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: linearize cloned gso packets in sctp_rcv\n\nA cloned head skb still shares these frag skbs in fraglist with the\noriginal head skb. It\u0026apos;s not safe to access these frag skbs.\n\nsyzbot reported two use-of-uninitialized-memory bugs caused by this:\n\n BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211\n sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998\n sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331\n sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122\n __release_sock+0x1da/0x330 net/core/sock.c:3106\n release_sock+0x6b/0x250 net/core/sock.c:3660\n sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360\n sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885\n sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031\n inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:718 [inline]\n\nand\n\n BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987\n sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88\n sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331\n sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148\n __release_sock+0x1d3/0x330 net/core/sock.c:3213\n release_sock+0x6b/0x270 net/core/sock.c:3767\n sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367\n sctp_sendmsg_to_asoc+0x223a/0x2260 net/sctp/socket.c:1886\n sctp_sendmsg+0x3910/0x49f0 net/sctp/socket.c:2032\n inet_sendmsg+0x269/0x2a0 net/ipv4/af_inet.c:851\n sock_sendmsg_nosec net/socket.c:712 [inline]\n\nThis patch fixes it by linearizing cloned gso packets in sctp_rcv().(CVE-2025-38718)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix UAF on smcsk after smc_listen_out()\n\nBPF CI testing report a UAF issue:\n\n [ 16.446633] BUG: kernel NULL pointer dereference, address: 000000000000003 0\n [ 16.447134] #PF: supervisor read access in kernel mod e\n [ 16.447516] #PF: error_code(0x0000) - not-present pag e\n [ 16.447878] PGD 0 P4D 0\n [ 16.448063] Oops: Oops: 0000 [#1] PREEMPT SMP NOPT I\n [ 16.448409] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Tainted: G OE 6.13.0-rc3-g89e8a75fda73-dirty #4 2\n [ 16.449124] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODUL E\n [ 16.449502] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/201 4\n [ 16.450201] Workqueue: smc_hs_wq smc_listen_wor k\n [ 16.450531] RIP: 0010:smc_listen_work+0xc02/0x159 0\n [ 16.452158] RSP: 0018:ffffb5ab40053d98 EFLAGS: 0001024 6\n [ 16.452526] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 000000000000030 0\n [ 16.452994] RDX: 0000000000000280 RSI: 00003513840053f0 RDI: 000000000000000 0\n [ 16.453492] RBP: ffffa097808e3800 R08: ffffa09782dba1e0 R09: 000000000000000 5\n [ 16.453987] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa0978274640 0\n [ 16.454497] R13: 0000000000000000 R14: 0000000000000000 R15: ffffa09782d4092 0\n [ 16.454996] FS: 0000000000000000(0000) GS:ffffa097bbc00000(0000) knlGS:000000000000000 0\n [ 16.455557] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003 3\n [ 16.455961] CR2: 0000000000000030 CR3: 0000000102788004 CR4: 0000000000770ef 0\n [ 16.456459] PKRU: 5555555 4\n [ 16.456654] Call Trace :\n [ 16.456832] \u0026lt;TASK \u0026gt;\n [ 16.456989] ? __die+0x23/0x7 0\n [ 16.457215] ? page_fault_oops+0x180/0x4c 0\n [ 16.457508] ? __lock_acquire+0x3e6/0x249 0\n [ 16.457801] ? exc_page_fault+0x68/0x20 0\n [ 16.458080] ? asm_exc_page_fault+0x26/0x3 0\n [ 16.458389] ? smc_listen_work+0xc02/0x159 0\n [ 16.458689] ? smc_listen_work+0xc02/0x159 0\n [ 16.458987] ? lock_is_held_type+0x8f/0x10 0\n [ 16.459284] process_one_work+0x1ea/0x6d 0\n [ 16.459570] worker_thread+0x1c3/0x38 0\n [ 16.459839] ? __pfx_worker_thread+0x10/0x1 0\n [ 16.460144] kthread+0xe0/0x11 0\n [ 16.460372] ? __pfx_kthread+0x10/0x1 0\n [ 16.460640] ret_from_fork+0x31/0x5 0\n [ 16.460896] ? __pfx_kthread+0x10/0x1 0\n [ 16.461166] ret_from_fork_asm+0x1a/0x3 0\n [ 16.461453] \u0026lt;/TASK \u0026gt;\n [ 16.461616] Modules linked in: bpf_testmod(OE) [last unloaded: bpf_testmod(OE) ]\n [ 16.462134] CR2: 000000000000003 0\n [ 16.462380] ---[ end trace 0000000000000000 ]---\n [ 16.462710] RIP: 0010:smc_listen_work+0xc02/0x1590\n\nThe direct cause of this issue is that after smc_listen_out_connected(),\nnewclcsock-\u0026gt;sk may be NULL since it will releases the smcsk. Therefore,\nif the application closes the socket immediately after accept,\nnewclcsock-\u0026gt;sk can be NULL. A possible execution order could be as\nfollows:\n\nsmc_listen_work | userspace\n-----------------------------------------------------------------\nlock_sock(sk) |\nsmc_listen_out_connected() |\n| \\- smc_listen_out |\n| | \\- release_sock |\n | |- sk-\u0026gt;sk_data_ready() |\n | fd = accept();\n | close(fd);\n | \\- socket-\u0026gt;sk = NULL;\n/* newclcsock-\u0026gt;sk is NULL now */\nSMC_STAT_SERV_SUCC_INC(sock_net(newclcsock-\u0026gt;sk))\n\nSince smc_listen_out_connected() will not fail, simply swapping the order\nof the code can easily fix this issue.(CVE-2025-38734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Avoid a NULL pointer dereference\n\n[WHY]\nAlthough unlikely drm_atomic_get_new_connector_state() or\ndrm_atomic_get_old_connector_state() can return NULL.\n\n[HOW]\nCheck returns before dereference.\n\n(cherry picked from commit 1e5e8d672fec9f2ab352be121be971877bff2af9)(CVE-2025-39693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ivsc: Fix crash at shutdown due to missing mei_cldev_disable() calls\n\nBoth the ACE and CSI driver are missing a mei_cldev_disable() call in\ntheir remove() function.\n\nThis causes the mei_cl client to stay part of the mei_device-\u0026gt;file_list\nlist even though its memory is freed by mei_cl_bus_dev_release() calling\nkfree(cldev-\u0026gt;cl).\n\nThis leads to a use-after-free when mei_vsc_remove() runs mei_stop()\nwhich first removes all mei bus devices calling mei_ace_remove() and\nmei_csi_remove() followed by mei_cl_bus_dev_release() and then calls\nmei_cl_all_disconnect() which walks over mei_device-\u0026gt;file_list dereferecing\nthe just freed cldev-\u0026gt;cl.\n\nAnd mei_vsc_remove() it self is run at shutdown because of the\nplatform_device_unregister(tp-\u0026gt;pdev) in vsc_tp_shutdown()\n\nWhen building a kernel with KASAN this leads to the following KASAN report:\n\n[ 106.634504] ==================================================================\n[ 106.634623] BUG: KASAN: slab-use-after-free in mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634683] Read of size 4 at addr ffff88819cb62018 by task systemd-shutdow/1\n[ 106.634729]\n[ 106.634767] Tainted: [E]=UNSIGNED_MODULE\n[ 106.634770] Hardware name: Dell Inc. XPS 16 9640/09CK4V, BIOS 1.12.0 02/10/2025\n[ 106.634773] Call Trace:\n[ 106.634777] \u0026lt;TASK\u0026gt;\n...\n[ 106.634871] kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:636)\n[ 106.634901] mei_cl_set_disconnected (drivers/misc/mei/client.c:783) mei\n[ 106.634921] mei_cl_all_disconnect (drivers/misc/mei/client.c:2165 (discriminator 4)) mei\n[ 106.634941] mei_reset (drivers/misc/mei/init.c:163) mei\n...\n[ 106.635042] mei_stop (drivers/misc/mei/init.c:348) mei\n[ 106.635062] mei_vsc_remove (drivers/misc/mei/mei_dev.h:784 drivers/misc/mei/platform-vsc.c:393) mei_vsc\n[ 106.635066] platform_remove (drivers/base/platform.c:1424)\n\nAdd the missing mei_cldev_disable() calls so that the mei_cl gets removed\nfrom mei_device-\u0026gt;file_list before it is freed to fix this.(CVE-2025-39711)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Revise __get_user() to probe user read access\n\nBecause of the way read access support is implemented, read access\ninterruptions are only triggered at privilege levels 2 and 3. The\nkernel executes at privilege level 0, so __get_user() never triggers\na read access interruption (code 26). Thus, it is currently possible\nfor user code to access a read protected address via a system call.\n\nFix this by probing read access rights at privilege level 3 (PRIV_USER)\nand setting __gu_err to -EFAULT (-14) if access isn\u0026apos;t allowed.\n\nNote the cmpiclr instruction does a 32-bit compare because COND macro\ndoesn\u0026apos;t work inside asm.(CVE-2025-39716)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: imu: bno055: fix OOB access of hw_xlate array\n\nFix a potential out-of-bounds array access of the hw_xlate array in\nbno055.c.\n\nIn bno055_get_regmask(), hw_xlate was iterated over the length of the\nvals array instead of the length of the hw_xlate array. In the case of\nbno055_gyr_scale, the vals array is larger than the hw_xlate array,\nso this could result in an out-of-bounds access. In practice, this\nshouldn\u0026apos;t happen though because a match should always be found which\nbreaks out of the for loop before it iterates beyond the end of the\nhw_xlate array.\n\nBy adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be\nsure we are iterating over the correct length.(CVE-2025-39719)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/ism: fix concurrency management in ism_cmd()\n\nThe s390x ISM device data sheet clearly states that only one\nrequest-response sequence is allowable per ISM function at any point in\ntime. Unfortunately as of today the s390/ism driver in Linux does not\nhonor that requirement. This patch aims to rectify that.\n\nThis problem was discovered based on Aliaksei\u0026apos;s bug report which states\nthat for certain workloads the ISM functions end up entering error state\n(with PEC 2 as seen from the logs) after a while and as a consequence\nconnections handled by the respective function break, and for future\nconnection requests the ISM device is not considered -- given it is in a\ndysfunctional state. During further debugging PEC 3A was observed as\nwell.\n\nA kernel message like\n[ 1211.244319] zpci: 061a:00:00.0: Event 0x2 reports an error for PCI function 0x61a\nis a reliable indicator of the stated function entering error state\nwith PEC 2. Let me also point out that a kernel message like\n[ 1211.244325] zpci: 061a:00:00.0: The ism driver bound to the device does not support error recovery\nis a reliable indicator that the ISM function won\u0026apos;t be auto-recovered\nbecause the ISM driver currently lacks support for it.\n\nOn a technical level, without this synchronization, commands (inputs to\nthe FW) may be partially or fully overwritten (corrupted) by another CPU\ntrying to issue commands on the same function. There is hard evidence that\nthis can lead to DMB token values being used as DMB IOVAs, leading to\nPEC 2 PCI events indicating invalid DMA. But this is only one of the\nfailure modes imaginable. In theory even completely losing one command\nand executing another one twice and then trying to interpret the outputs\nas if the command we intended to execute was actually executed and not\nthe other one is also possible. Frankly, I don\u0026apos;t feel confident about\nproviding an exhaustive list of possible consequences.(CVE-2025-39726)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Optimize module load time by optimizing PLT/GOT counting\n\nWhen enabling CONFIG_KASAN, CONFIG_PREEMPT_VOLUNTARY_BUILD and\nCONFIG_PREEMPT_VOLUNTARY at the same time, there will be soft deadlock,\nthe relevant logs are as follows:\n\nrcu: INFO: rcu_sched self-detected stall on CPU\n...\nCall Trace:\n[\u0026lt;900000000024f9e4\u0026gt;] show_stack+0x5c/0x180\n[\u0026lt;90000000002482f4\u0026gt;] dump_stack_lvl+0x94/0xbc\n[\u0026lt;9000000000224544\u0026gt;] rcu_dump_cpu_stacks+0x1fc/0x280\n[\u0026lt;900000000037ac80\u0026gt;] rcu_sched_clock_irq+0x720/0xf88\n[\u0026lt;9000000000396c34\u0026gt;] update_process_times+0xb4/0x150\n[\u0026lt;90000000003b2474\u0026gt;] tick_nohz_handler+0xf4/0x250\n[\u0026lt;9000000000397e28\u0026gt;] __hrtimer_run_queues+0x1d0/0x428\n[\u0026lt;9000000000399b2c\u0026gt;] hrtimer_interrupt+0x214/0x538\n[\u0026lt;9000000000253634\u0026gt;] constant_timer_interrupt+0x64/0x80\n[\u0026lt;9000000000349938\u0026gt;] __handle_irq_event_percpu+0x78/0x1a0\n[\u0026lt;9000000000349a78\u0026gt;] handle_irq_event_percpu+0x18/0x88\n[\u0026lt;9000000000354c00\u0026gt;] handle_percpu_irq+0x90/0xf0\n[\u0026lt;9000000000348c74\u0026gt;] handle_irq_desc+0x94/0xb8\n[\u0026lt;9000000001012b28\u0026gt;] handle_cpu_irq+0x68/0xa0\n[\u0026lt;9000000001def8c0\u0026gt;] handle_loongarch_irq+0x30/0x48\n[\u0026lt;9000000001def958\u0026gt;] do_vint+0x80/0xd0\n[\u0026lt;9000000000268a0c\u0026gt;] kasan_mem_to_shadow.part.0+0x2c/0x2a0\n[\u0026lt;90000000006344f4\u0026gt;] __asan_load8+0x4c/0x120\n[\u0026lt;900000000025c0d0\u0026gt;] module_frob_arch_sections+0x5c8/0x6b8\n[\u0026lt;90000000003895f0\u0026gt;] load_module+0x9e0/0x2958\n[\u0026lt;900000000038b770\u0026gt;] __do_sys_init_module+0x208/0x2d0\n[\u0026lt;9000000001df0c34\u0026gt;] do_syscall+0x94/0x190\n[\u0026lt;900000000024d6fc\u0026gt;] handle_syscall+0xbc/0x158\n\nAfter analysis, this is because the slow speed of loading the amdgpu\nmodule leads to the long time occupation of the cpu and then the soft\ndeadlock.\n\nWhen loading a module, module_frob_arch_sections() tries to figure out\nthe number of PLTs/GOTs that will be needed to handle all the RELAs. It\nwill call the count_max_entries() to find in an out-of-order date which\ncounting algorithm has O(n^2) complexity.\n\nTo make it faster, we sort the relocation list by info and addend. That\nway, to check for a duplicate relocation, it just needs to compare with\nthe previous entry. This reduces the complexity of the algorithm to O(n\n log n), as done in commit d4e0340919fb (\u0026quot;arm64/module: Optimize module\nload time by optimizing PLT counting\u0026quot;). This gives sinificant reduction\nin module load time for modules with large number of relocations.\n\nAfter applying this patch, the soft deadlock problem has been solved,\nand the kernel starts normally without \u0026quot;Call Trace\u0026quot;.\n\nUsing the default configuration to test some modules, the results are as\nfollows:\n\nModule Size\nip_tables 36K\nfat 143K\nradeon 2.5MB\namdgpu 16MB\n\nWithout this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 54\t\t\t\t1221/84\namdgpu 1411\t\t\t4525/1098\n\nWith this patch:\nModule Module load time (ms)\tCount(PLTs/GOTs)\nip_tables 18\t\t\t\t59/6\nfat 0\t\t\t\t162/14\nradeon 22\t\t\t\t1221/84\namdgpu 45\t\t\t\t4525/1098(CVE-2025-39767)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nparisc: Drop WARN_ON_ONCE() from flush_cache_vmap\n\nI have observed warning to occassionally trigger.(CVE-2025-39781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nARM: tegra: Use I/O memcpy to write to IRAM\n\nKasan crashes the kernel trying to check boundaries when using the\nnormal memcpy.(CVE-2025-39794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: hid-ntrig: fix unable to handle page fault in ntrig_report_version()\n\nin ntrig_report_version(), hdev parameter passed from hid_probe().\nsending descriptor to /dev/uhid can make hdev-\u0026gt;dev.parent-\u0026gt;parent to null\nif hdev-\u0026gt;dev.parent-\u0026gt;parent is null, usb_dev has\ninvalid address(0xffffffffffffff58) that hid_to_usb_dev(hdev) returned\nwhen usb_rcvctrlpipe() use usb_dev,it trigger\npage fault error for address(0xffffffffffffff58)\n\nadd null check logic to ntrig_report_version()\nbefore calling hid_to_usb_dev()(CVE-2025-39808)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: prevent release journal inode after journal shutdown\n\nBefore calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already\nbeen executed in ocfs2_dismount_volume(), so osb-\u0026gt;journal must be NULL. \nTherefore, the following calltrace will inevitably fail when it reaches\njbd2_journal_release_jbd_inode().\n\nocfs2_dismount_volume()-\u0026gt;\n ocfs2_delete_osb()-\u0026gt;\n ocfs2_free_slot_info()-\u0026gt;\n __ocfs2_free_slot_info()-\u0026gt;\n evict()-\u0026gt;\n ocfs2_evict_inode()-\u0026gt;\n ocfs2_clear_inode()-\u0026gt;\n\t jbd2_journal_release_jbd_inode(osb-\u0026gt;journal-\u0026gt;j_journal,\n\nAdding osb-\u0026gt;journal checks will prevent null-ptr-deref during the above\nexecution path.(CVE-2025-39842)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region()\n\nIn __iodyn_find_io_region(), pcmcia_make_resource() is assigned to\nres and used in pci_bus_alloc_resource(). There is a dereference of res\nin pci_bus_alloc_resource(), which could lead to a NULL pointer\ndereference on failure of pcmcia_make_resource().\n\nFix this bug by adding a check of res.(CVE-2025-39846)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: vhci: Prevent use-after-free by removing debugfs files early\n\nMove the creation of debugfs files into a dedicated function, and ensure\nthey are explicitly removed during vhci_release(), before associated\ndata structures are freed.\n\nPreviously, debugfs files such as \u0026quot;force_suspend\u0026quot;, \u0026quot;force_wakeup\u0026quot;, and\nothers were created under hdev-\u0026gt;debugfs but not removed in\nvhci_release(). Since vhci_release() frees the backing vhci_data\nstructure, any access to these files after release would result in\nuse-after-free errors.\n\nAlthough hdev-\u0026gt;debugfs is later freed in hci_release_dev(), user can\naccess files after vhci_data is freed but before hdev-\u0026gt;debugfs is\nreleased.(CVE-2025-39861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work\n\nThe brcmf_btcoex_detach() only shuts down the btcoex timer, if the\nflag timer_on is false. However, the brcmf_btcoex_timerfunc(), which\nruns as timer handler, sets timer_on to false. This creates critical\nrace conditions:\n\n1.If brcmf_btcoex_detach() is called while brcmf_btcoex_timerfunc()\nis executing, it may observe timer_on as false and skip the call to\ntimer_shutdown_sync().\n\n2.The brcmf_btcoex_timerfunc() may then reschedule the brcmf_btcoex_info\nworker after the cancel_work_sync() has been executed, resulting in\nuse-after-free bugs.\n\nThe use-after-free bugs occur in two distinct scenarios, depending on\nthe timing of when the brcmf_btcoex_info struct is freed relative to\nthe execution of its worker thread.\n\nScenario 1: Freed before the worker is scheduled\n\nThe brcmf_btcoex_info is deallocated before the worker is scheduled.\nA race condition can occur when schedule_work(\u0026amp;bt_local-\u0026gt;work) is\ncalled after the target memory has been freed. The sequence of events\nis detailed below:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... |\n kfree(cfg-\u0026gt;btcoex); // FREE |\n | schedule_work(\u0026amp;bt_local-\u0026gt;work); // USE\n\nScenario 2: Freed after the worker is scheduled\n\nThe brcmf_btcoex_info is freed after the worker has been scheduled\nbut before or during its execution. In this case, statements within\nthe brcmf_btcoex_handler() — such as the container_of macro and\nsubsequent dereferences of the brcmf_btcoex_info object will cause\na use-after-free access. The following timeline illustrates this\nscenario:\n\nCPU0 | CPU1\nbrcmf_btcoex_detach | brcmf_btcoex_timerfunc\n | bt_local-\u0026gt;timer_on = false;\n if (cfg-\u0026gt;btcoex-\u0026gt;timer_on) |\n ... |\n cancel_work_sync(); |\n ... | schedule_work(); // Reschedule\n |\n kfree(cfg-\u0026gt;btcoex); // FREE | brcmf_btcoex_handler() // Worker\n /* | btci = container_of(....); // USE\n The kfree() above could | ...\n also occur at any point | btci-\u0026gt; // USE\n during the worker\u0026apos;s execution|\n */ |\n\nTo resolve the race conditions, drop the conditional check and call\ntimer_shutdown_sync() directly. It can deactivate the timer reliably,\nregardless of its current state. Once stopped, the timer_on state is\nthen set to false.(CVE-2025-39863)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()\n\nPatch series \u0026quot;mm/damon: avoid divide-by-zero in DAMON module\u0026apos;s parameters\napplication\u0026quot;.\n\nDAMON\u0026apos;s RECLAIM and LRU_SORT modules perform no validation on\nuser-configured parameters during application, which may lead to\ndivision-by-zero errors.\n\nAvoid the divide-by-zero by adding validation checks when DAMON modules\nattempt to apply the parameters.\n\n\nThis patch (of 2):\n\nDuring the calculation of \u0026apos;hot_thres\u0026apos; and \u0026apos;cold_thres\u0026apos;, either\n\u0026apos;sample_interval\u0026apos; or \u0026apos;aggr_interval\u0026apos; is used as the divisor, which may\nlead to division-by-zero errors. Fix it by directly returning -EINVAL\nwhen such a case occurs. Additionally, since \u0026apos;aggr_interval\u0026apos; is already\nrequired to be set no smaller than \u0026apos;sample_interval\u0026apos; in damon_set_attrs(),\nonly the case where \u0026apos;sample_interval\u0026apos; is zero needs to be checked.(CVE-2025-39909)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()\n\nWhen creating a new scheme of DAMON_RECLAIM, the calculation of\n\u0026apos;min_age_region\u0026apos; uses \u0026apos;aggr_interval\u0026apos; as the divisor, which may lead to\ndivision-by-zero errors. Fix it by directly returning -EINVAL when such a\ncase occurs.(CVE-2025-39916)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm: bridge: anx7625: Fix NULL pointer dereference with early IRQ\n\nIf the interrupt occurs before resource initialization is complete, the\ninterrupt handler/worker may access uninitialized data such as the I2C\ntcpc_client device, potentially leading to NULL pointer dereference.(CVE-2025-39934)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: wilc1000: avoid buffer overflow in WID string configuration\n\nFix the following copy overflow warning identified by Smatch checker.\n\n drivers/net/wireless/microchip/wilc1000/wlan_cfg.c:184 wilc_wlan_parse_response_frame()\n error: \u0026apos;__memcpy()\u0026apos; \u0026apos;cfg-\u0026gt;s[i]-\u0026gt;str\u0026apos; copy overflow (512 vs 65537)\n\nThis patch introduces size check before accessing the memory buffer.\nThe checks are base on the WID type of received data from the firmware.\nFor WID string configuration, the size limit is determined by individual\nelement size in \u0026apos;struct wilc_cfg_str_vals\u0026apos; that is maintained in \u0026apos;len\u0026apos; field\nof \u0026apos;struct wilc_cfg_str\u0026apos;.(CVE-2025-39952)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn\u0026apos;t valid\n\nSkip the WRMSR and HLT fastpaths in SVM\u0026apos;s VM-Exit handler if the next RIP\nisn\u0026apos;t valid, e.g. because KVM is running with nrips=false. SVM must\ndecode and emulate to skip the instruction if the CPU doesn\u0026apos;t provide the\nnext RIP, and getting the instruction bytes to decode requires reading\nguest memory. Reading guest memory through the emulator can fault, i.e.\ncan sleep, which is disallowed since the fastpath handlers run with IRQs\ndisabled.\n\n BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106\n in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu\n preempt_count: 1, expected: 0\n INFO: lockdep is turned off.\n irq event stamp: 30580\n hardirqs last enabled at (30579): [\u0026lt;ffffffffc08b2527\u0026gt;] vcpu_run+0x1787/0x1db0 [kvm]\n hardirqs last disabled at (30580): [\u0026lt;ffffffffb4f62e32\u0026gt;] __schedule+0x1e2/0xed0\n softirqs last enabled at (30570): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n softirqs last disabled at (30568): [\u0026lt;ffffffffb4247a64\u0026gt;] fpu_swap_kvm_fpstate+0x44/0x210\n CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE\n Tainted: [U]=USER\n Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x7d/0xb0\n __might_resched+0x271/0x290\n __might_fault+0x28/0x80\n kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm]\n kvm_fetch_guest_virt+0x92/0xc0 [kvm]\n __do_insn_fetch_bytes+0xf3/0x1e0 [kvm]\n x86_decode_insn+0xd1/0x1010 [kvm]\n x86_emulate_instruction+0x105/0x810 [kvm]\n __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd]\n handle_fastpath_invd+0xc4/0x1a0 [kvm]\n vcpu_run+0x11a1/0x1db0 [kvm]\n kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm]\n kvm_vcpu_ioctl+0x578/0x6a0 [kvm]\n __se_sys_ioctl+0x6d/0xb0\n do_syscall_64+0x8a/0x2c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f479d57a94b\n \u0026lt;/TASK\u0026gt;\n\nNote, this is essentially a reapply of commit 5c30e8101e8d (\u0026quot;KVM: SVM:\nSkip WRMSR fastpath on VM-Exit if next RIP isn\u0026apos;t valid\u0026quot;), but with\ndifferent justification (KVM now grabs SRCU when skipping the instruction\nfor other reasons).(CVE-2025-40038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix potential null deref in ext4_mb_init()\n\nIn ext4_mb_init(), ext4_mb_avg_fragment_size_destroy() may be called\nwhen sbi-\u0026gt;s_mb_avg_fragment_size remains uninitialized (e.g., if groupinfo\nslab cache allocation fails). Since ext4_mb_avg_fragment_size_destroy()\nlacks null pointer checking, this leads to a null pointer dereference.\n\n==================================================================\nEXT4-fs: no memory for groupinfo slab cache\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPGD 0 P4D 0\nOops: Oops: 0002 [#1] SMP PTI\nCPU:2 UID: 0 PID: 87 Comm:mount Not tainted 6.17.0-rc2 #1134 PREEMPT(none)\nRIP: 0010:_raw_spin_lock_irqsave+0x1b/0x40\nCall Trace:\n \u0026lt;TASK\u0026gt;\n xa_destroy+0x61/0x130\n ext4_mb_init+0x483/0x540\n __ext4_fill_super+0x116d/0x17b0\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n do_new_mount+0x197/0x300\n __x64_sys_mount+0x116/0x150\n do_syscall_64+0x50/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nTherefore, add necessary null check to ext4_mb_avg_fragment_size_destroy()\nto prevent this issue. The same fix is also applied to\next4_mb_largest_free_orders_destroy().(CVE-2025-40119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/i10nm: Skip DIMM enumeration on a disabled memory controller\n\nWhen loading the i10nm_edac driver on some Intel Granite Rapids servers,\na call trace may appear as follows:\n\n UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c:453:16\n shift exponent -66 is negative\n ...\n __ubsan_handle_shift_out_of_bounds+0x1e3/0x390\n skx_get_dimm_info.cold+0x47/0xd40 [skx_edac_common]\n i10nm_get_dimm_config+0x23e/0x390 [i10nm_edac]\n skx_register_mci+0x159/0x220 [skx_edac_common]\n i10nm_init+0xcb0/0x1ff0 [i10nm_edac]\n ...\n\nThis occurs because some BIOS may disable a memory controller if there\naren\u0026apos;t any memory DIMMs populated on this memory controller. The DIMMMTR\nregister of this disabled memory controller contains the invalid value\n~0, resulting in the call trace above.\n\nFix this call trace by skipping DIMM enumeration on a disabled memory\ncontroller.(CVE-2025-40157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: quota: create dedicated workqueue for quota_release_work\n\nThere is a kernel panic due to WARN_ONCE when panic_on_warn is set.\n\nThis issue occurs when writeback is triggered due to sync call for an\nopened file(ie, writeback reason is WB_REASON_SYNC). When f2fs balance\nis needed at sync path, flush for quota_release_work is triggered.\nBy default quota_release_work is queued to \u0026quot;events_unbound\u0026quot; queue which\ndoes not have WQ_MEM_RECLAIM flag. During f2fs balance \u0026quot;writeback\u0026quot;\nworkqueue tries to flush quota_release_work causing kernel panic due to\nMEM_RECLAIM flag mismatch errors.\n\nThis patch creates dedicated workqueue with WQ_MEM_RECLAIM flag\nfor work quota_release_work.\n\n------------[ cut here ]------------\nWARNING: CPU: 4 PID: 14867 at kernel/workqueue.c:3721 check_flush_dependency+0x13c/0x148\nCall trace:\n check_flush_dependency+0x13c/0x148\n __flush_work+0xd0/0x398\n flush_delayed_work+0x44/0x5c\n dquot_writeback_dquots+0x54/0x318\n f2fs_do_quota_sync+0xb8/0x1a8\n f2fs_write_checkpoint+0x3cc/0x99c\n f2fs_gc+0x190/0x750\n f2fs_balance_fs+0x110/0x168\n f2fs_write_single_data_page+0x474/0x7dc\n f2fs_write_data_pages+0x7d0/0xd0c\n do_writepages+0xe0/0x2f4\n __writeback_single_inode+0x44/0x4ac\n writeback_sb_inodes+0x30c/0x538\n wb_writeback+0xf4/0x440\n wb_workfn+0x128/0x5d4\n process_scheduled_works+0x1c4/0x45c\n worker_thread+0x32c/0x3e8\n kthread+0x11c/0x1b0\n ret_from_fork+0x10/0x20\nKernel panic - not syncing: kernel: panic_on_warn set ...(CVE-2025-40196)\n\nIn the Linux kernel, the following vulnerability has been resolved: media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try(). v4l2_subdev_call_state_try() macro allocates a subdev state with __v4l2_subdev_state_alloc(), but does not check the returned value. If __v4l2_subdev_state_alloc fails, it returns an ERR_PTR, and that would cause v4l2_subdev_call_state_try() to crash. Add proper error handling to v4l2_subdev_call_state_try().(CVE-2025-40207)","status":"published","published":"2025-11-22T11:09:49Z","modified":"2026-08-18T01:19:20.031037324Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:44.957082Z"},{"id":"UBUNTU-CVE-2025-40038","description":"In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid Skip the WRMSR and HLT fastpaths in SVM's VM-Exit handler if the next RIP isn't valid, e.g. because KVM is running with nrips=false. SVM must decode and emulate to skip the instruction if the CPU doesn't provide the next RIP, and getting the instruction bytes to decode requires reading guest memory. Reading guest memory through the emulator can fault, i.e. can sleep, which is disallowed since the fastpath handlers run with IRQs disabled. BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:106 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 32611, name: qemu preempt_count: 1, expected: 0 INFO: lockdep is turned off. irq event stamp: 30580 hardirqs last enabled at (30579): [\u003cffffffffc08b2527\u003e] vcpu_run+0x1787/0x1db0 [kvm] hardirqs last disabled at (30580): [\u003cffffffffb4f62e32\u003e] __schedule+0x1e2/0xed0 softirqs last enabled at (30570): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210 softirqs last disabled at (30568): [\u003cffffffffb4247a64\u003e] fpu_swap_kvm_fpstate+0x44/0x210 CPU: 298 UID: 0 PID: 32611 Comm: qemu Tainted: G U 6.16.0-smp--e6c618b51cfe-sleep #782 NONE Tainted: [U]=USER Hardware name: Google Astoria-Turin/astoria, BIOS 0.20241223.2-0 01/17/2025 Call Trace: \u003cTASK\u003e dump_stack_lvl+0x7d/0xb0 __might_resched+0x271/0x290 __might_fault+0x28/0x80 kvm_vcpu_read_guest_page+0x8d/0xc0 [kvm] kvm_fetch_guest_virt+0x92/0xc0 [kvm] __do_insn_fetch_bytes+0xf3/0x1e0 [kvm] x86_decode_insn+0xd1/0x1010 [kvm] x86_emulate_instruction+0x105/0x810 [kvm] __svm_skip_emulated_instruction+0xc4/0x140 [kvm_amd] handle_fastpath_invd+0xc4/0x1a0 [kvm] vcpu_run+0x11a1/0x1db0 [kvm] kvm_arch_vcpu_ioctl_run+0x5cc/0x730 [kvm] kvm_vcpu_ioctl+0x578/0x6a0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x8a/0x2c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f479d57a94b \u003c/TASK\u003e Note, this is essentially a reapply of commit 5c30e8101e8d (\"KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid\"), but with different justification (KVM now grabs SRCU when skipping the instruction for other reasons).","status":"published","published":"2025-10-28T12:15:00Z","modified":"2026-11-03T14:35:40.608325953Z","cvss":[{"version":"4.0","score":5.6,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-03T15:16:05.953168Z"},{"id":"MGASA-2025-0309","title":"Updated kernel, kmod-xtables-addons \u0026 kmod-virtualbox packages fix security vulnerabilities","description":"Upstream kernel version 6.6.116 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2025-11-22T20:20:19Z","modified":"2026-04-16T04:42:20.139370863Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2025-0310","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.116 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-11-22T20:20:19Z","modified":"2026-04-16T04:40:41.151011161Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2025:15702-1","title":"kernel-devel-6.17.7-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-6.17.7-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-11-04T00:00:00Z","modified":"2026-03-23T04:54:06.84922Z","updated_at":"2026-11-02T16:58:37.810934Z"},{"id":"openSUSE-SU-2025:20172-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431 bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39831: fbnic: Move phylink resume out of service_task and into open/close (bsc#1249977).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39897: net: xilinx: axienet: Add error handling for RX metadata pointer retrieval (bsc#1250746).\n- CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt (bsc#1250723).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39961: iommu/amd/pgtbl: Fix possible race while increase page table level (bsc#1251817).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-39990: bpf: Check the helper function is valid in get_helper_proto (bsc#1252054).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work (bsc#1252301).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40031: tee: fix register_shm_helper() (bsc#1252779).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: tcp: convert to dev_net_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (bsc#1252901).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40133: mptcp: Call dst_release() in mptcp_active_enable() (bsc#1253328).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (bsc#1253423).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40175: idpf: cleanup remaining SKBs in PTP flows (bsc#1253426).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40203: listmount: don't call path_put() under namespace semaphore (bsc#1253457).\n\nThe following non security issues were fixed:\n\n- ACPI: scan: Update honor list for RPMI System MSI (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Fix \"drm/xe: Don't allow evicting of BOs in same VM in array of VM binds\" (bsc#1252923)\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault (git-fixes).\n- PCI/ERR: Update device error_state already after reset (stable-fixes).\n- PM: EM: Slightly reduce em_check_capacity_update() overhead (stable-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon MTU set\" (git-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon port speed set\" (git-fixes).\n- Update config files: enable zstd module decompression (jsc#PED-14115).\n- bpf/selftests: Fix test_tcpnotify_user (bsc#1253635).\n- btrfs: do not clear read-only when adding sprout device (bsc#1253238).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- hwmon: (lenovo-ec-sensors) Update P8 supprt (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- mount: handle NULL values in mnt_ns_release() (bsc#1254308)\n- net/smc: Remove validation of reserved bits in CLC Decline (bsc#1252357).\n- net: phy: move realtek PHY driver to its own subdirectory (jsc#PED-14353).\n- net: phy: realtek: add defines for shadowed c45 standard registers (jsc#PED-14353).\n- net: phy: realtek: add helper RTL822X_VND2_C22_REG (jsc#PED-14353).\n- net: phy: realtek: change order of calls in C22 read_status() (jsc#PED-14353).\n- net: phy: realtek: clear 1000Base-T link partner advertisement (jsc#PED-14353).\n- net: phy: realtek: improve mmd register access for internal PHY's (jsc#PED-14353).\n- net: phy: realtek: read duplex and gbit master from PHYSR register (jsc#PED-14353).\n- net: phy: realtek: switch from paged to MMD ops in rtl822x functions (jsc#PED-14353).\n- net: phy: realtek: use string choices helpers (jsc#PED-14353).\n- net: xilinx: axienet: Fix IRQ coalescing packet count overflow (bsc#1250746)\n- net: xilinx: axienet: Fix RX skb ring management in DMAengine mode (bsc#1250746)\n- net: xilinx: axienet: Fix Tx skb circular buffer occupancy check in dmaengine xmit (bsc#1250746)\n- nvmet-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- perf list: Add IBM z17 event descriptions (jsc#PED-13611).\n- platform/x86:intel/pmc: Update Arrow Lake telemetry GUID (git-fixes).\n- powercap: intel_rapl: Add support for Panther Lake platform (jsc#PED-13949).\n- pwm: pca9685: Use bulk write to atomicially update registers (stable-fixes).\n- r8169: add PHY c45 ops for MDIO_MMD_VENDOR2 registers (jsc#PED-14353).\n- r8169: add support for Intel Killer E5000 (jsc#PED-14353).\n- r8169: add support for RTL8125BP rev.b (jsc#PED-14353).\n- r8169: add support for RTL8125D rev.b (jsc#PED-14353).\n- r8169: adjust version numbering for RTL8126 (jsc#PED-14353).\n- r8169: align RTL8125 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8125/RTL8126 PHY config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8126 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align WAKE_PHY handling with r8125/r8126 vendor drivers (jsc#PED-14353).\n- r8169: avoid duplicated messages if loading firmware fails and switch to warn level (jsc#PED-14353).\n- r8169: don't take RTNL lock in rtl_task() (jsc#PED-14353).\n- r8169: enable EEE at 2.5G per default on RTL8125B (jsc#PED-14353).\n- r8169: enable RTL8168H/RTL8168EP/RTL8168FP ASPM support (jsc#PED-14353).\n- r8169: fix inconsistent indenting in rtl8169_get_eth_mac_stats (jsc#PED-14353).\n- r8169: implement additional ethtool stats ops (jsc#PED-14353).\n- r8169: improve __rtl8169_set_wol (jsc#PED-14353).\n- r8169: improve initialization of RSS registers on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: improve rtl_set_d3_pll_down (jsc#PED-14353).\n- r8169: increase max jumbo packet size on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: remove leftover locks after reverted change (jsc#PED-14353).\n- r8169: remove original workaround for RTL8125 broken rx issue (jsc#PED-14353).\n- r8169: remove rtl_dash_loop_wait_high/low (jsc#PED-14353).\n- r8169: remove support for chip version 11 (jsc#PED-14353).\n- r8169: remove unused flag RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE (jsc#PED-14353).\n- r8169: replace custom flag with disable_work() et al (jsc#PED-14353).\n- r8169: switch away from deprecated pcim_iomap_table (jsc#PED-14353).\n- r8169: use helper r8169_mod_reg8_cond to simplify rtl_jumbo_config (jsc#PED-14353).\n- ring-buffer: Update pages_touched to reflect persistent buffer content (git-fixes).\n- s390/mm: Fix __ptep_rdp() inline assembly (bsc#1253643).\n- sched/fair: Get rid of sched_domains_curr_level hack for tl-\u003ecpumask() (bsc#1246843).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1248792).\n- sched/fair: Proportional newidle balance (bsc#1248792).\n- sched/fair: Proportional newidle balance -KABI (bsc#1248792).\n- sched/fair: Revert max_newidle_lb_cost bump (bsc#1248792).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1248792).\n- sched/fair: Small cleanup to sched_balance_newidle() (bsc#1248792).\n- sched/fair: Small cleanup to update_newidle_cost() (bsc#1248792).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- smpboot: introduce SDTL_INIT() helper to tidy sched topology setup (bsc#1246843).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: mt76: do not add wcid entries to sta poll list during MCU reset (bsc#1254315).\n- wifi: mt76: introduce mt792x_config_mac_addr_list routine (bsc#1254315).\n- wifi: mt76: mt7925: Fix logical vs bitwise typo (bsc#1254315).\n- wifi: mt76: mt7925: Remove unnecessary if-check (bsc#1254315).\n- wifi: mt76: mt7925: Simplify HIF suspend handling to avoid suspend fail (bsc#1254315).\n- wifi: mt76: mt7925: add EHT control support based on the CLC data (bsc#1254315).\n- wifi: mt76: mt7925: add handler to hif suspend/resume event (bsc#1254315).\n- wifi: mt76: mt7925: add pci restore for hibernate (bsc#1254315).\n- wifi: mt76: mt7925: config the dwell time by firmware (bsc#1254315).\n- wifi: mt76: mt7925: extend MCU support for testmode (bsc#1254315).\n- wifi: mt76: mt7925: fix CLC command timeout when suspend/resume (bsc#1254315).\n- wifi: mt76: mt7925: fix missing hdr_trans_tlv command for broadcast wtbl (bsc#1254315).\n- wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend (bsc#1254315).\n- wifi: mt76: mt7925: refine the txpower initialization flow (bsc#1254315).\n- wifi: mt76: mt7925: replace zero-length array with flexible-array member (bsc#1254315).\n- wifi: mt76: mt7925: update the channel usage when the regd domain changed (bsc#1254315).\n- wifi: mt76: mt7925e: fix too long of wifi resume time (bsc#1254315).\n- x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled (bsc#1246843).\n- x86/smpboot: moves x86_topology to static initialize and truncate (bsc#1246843).\n- x86/smpboot: remove redundant CONFIG_SCHED_SMT (bsc#1246843).\n","status":"published","published":"2025-12-19T17:38:16Z","modified":"2026-03-23T04:54:19.612473Z","updated_at":"2026-11-02T16:58:38.101535Z"},{"id":"openSUSE-SU-2026:10301-1","title":"kernel-devel-longterm-6.18.16-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-longterm-6.18.16-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-03-07T00:00:00Z","modified":"2026-03-08T15:45:06.717828Z","updated_at":"2026-11-02T16:58:38.101535Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-40038","title":"CVE-2025-40038 in linux - Patched by Root","description":"Root has patched CVE-2025-40038 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:02.663646068Z","updated_at":"2026-11-06T16:59:12.925458Z"},{"id":"SUSE-SU-2025:4393-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40080: nbd: restrict sockets to TCP and UDP (bsc#1252774).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n\nThe following non security issues were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: don't log messages meant for 1810c when initializing 1824c (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tas2781: fix getting the wrong device number (git-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Don't hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern() (git-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SEV: Enforce minimum GHCB version requirement for SEV-SNP guests (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Don't treat ENTER and LEAVE as branches, because they aren't (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- KVM: x86: Have all vendor neutral sub-configs depend on KVM_X86, not just KVM (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Don't fail destroy QP and cleanup debugfs earlier (git-fixes).\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes).\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- acpi/hmat: Fix lockdep warning for hmem_register_resource() (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- ata: libata-scsi: Add missing scsi_device_put() in ata_scsi_dev_rescan() (git-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19 (bsc#1252368).\n- bpf: improve error message for unsupported helper (bsc#1252370).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- cgroup/cpuset: Remove remote_partition_check() \u0026 make update_cpumasks_hier() handle remote partition (bsc#1241166).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cpuset: Use new excpus for nocpu error check when enabling root partition (bsc#1241166).\n- cpuset: fix failure to enable isolated partition when containing isolcpus (bsc#1241166).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/amdgpu: Release xcp drm memory after unplug (stable-fixes).\n- drm/amd/display/dml2: Guard dml21_map_dc_state_into_dml_display_cfg with DC_FP_START (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Add fallback path for YCBCR422 (stable-fixes).\n- drm/amd/display: Allow VRR params change if unsynced with the stream (git-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Enable mst when it's detected but yet to be initialized (git-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Fix for test crash due to power gating (stable-fixes).\n- drm/amd/display: Fix incorrect return of vblank enable on unconfigured crtc (stable-fixes).\n- drm/amd/display: Fix pbn_div Calculation Error (stable-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: Increase minimum clock for TMDS 420 with pipe splitting (stable-fixes).\n- drm/amd/display: Init dispclk from bootup clock for DCN314 (stable-fixes).\n- drm/amd/display: Move setup_stream_attribute (stable-fixes).\n- drm/amd/display: Reject modes with too high pixel clock on DCE6-10 (git-fixes).\n- drm/amd/display: Reset apply_eamless_boot_optimization when dpms_off (stable-fixes).\n- drm/amd/display: Set up pixel encoding for YCBCR422 (stable-fixes).\n- drm/amd/display: Support HW cursor 180 rot for any number of pipe splits (stable-fixes).\n- drm/amd/display: Wait until OTG enable state is cleared (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: change dc stream color settings only in atomic commit (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: fix condition for setting timing_adjust_pending (stable-fixes).\n- drm/amd/display: fix dml ms order of operations (stable-fixes).\n- drm/amd/display: incorrect conditions for failing dto calculations (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Check that VPE has reached DPM0 in idle handler (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu/smu: Handle S0ix for vangogh (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Check vcn sram load return value (stable-fixes).\n- drm/amdgpu: Correct the counts of nr_banks and nr_errors (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Fix function header names in amdgpu_connectors.c (git-fixes).\n- drm/amdgpu: Fix unintended error log in VCN5_0_0 (git-fixes).\n- drm/amdgpu: Respect max pixel clock for HDMI and DVI-D (v2) (stable-fixes).\n- drm/amdgpu: Skip poison aca bank from UE channel (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add range check for RAS bad page address (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: disable peer-to-peer access for DCC-enabled GC12 VRAM surfaces (stable-fixes).\n- drm/amdgpu: don't enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: fix nullptr err of vm_handle_moved (stable-fixes).\n- drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdgpu: remove two invalid BUG_ON()s (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: relax checks for over allocation of save area (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/ast: Blank with VGACR17 sync enable, always clear VGACRB6 sync off (git-fixes).\n- drm/bridge: cdns-dsi: Don't fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: don't set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/exynos: exynos7_drm_decon: remove ctx-\u003esuspended (git-fixes).\n- drm/i915/dp_mst: Work around Thunderbolt sink disconnect after SINK_COUNT_ESI read (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/mediatek: Add pm_runtime support for GCE power control (git-fixes).\n- drm/mediatek: Disable AFBC support on Mediatek DRM driver (git-fixes).\n- drm/msm/a6xx: Fix PDC sleep sequence (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm/registers: Generate _HI/LO builders for reg64 (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/panthor: Serialize GPU cache flush operations (stable-fixes).\n- drm/panthor: check bo offset alignment in vm bind (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/sched: Optimise drm_sched_entity_push_job (stable-fixes).\n- drm/sched: avoid killing parent entity on child SIGKILL (stable-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- drm/xe/guc: Add more GuC load error status codes (stable-fixes).\n- drm/xe/guc: Increase GuC crash dump buffer size (stable-fixes).\n- drm/xe/guc: Return an error code if the GuC load fails (stable-fixes).\n- drm/xe/guc: Set upper limit of H2G retries over CTB (stable-fixes).\n- drm/xe/guc: Synchronize Dead CT worker with unbind (git-fixes).\n- drm/xe: Do clean shutdown also when using flr (git-fixes).\n- drm/xe: Do not wake device during a GT reset (git-fixes).\n- drm/xe: Fix oops in xe_gem_fault when running core_hotunplug test (stable-fixes).\n- drm/xe: Move declarations under conditional branch (stable-fixes).\n- drm/xe: Remove duplicate DRM_EXEC selection from Kconfig (git-fixes).\n- drm: panel-backlight-quirks: Make EDID match optional (stable-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- hyperv: Remove the spurious null directive line (git-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- ixgbe: fix memory leak and use-after-free in ixgbe_recovery_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- media: videobuf2: forbid remove_bufs when legacy fileio is active (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- nvme-auth: add hkdf_expand_label() (bsc#1247683).\n- nvme-auth: use hkdf_expand_label() (bsc#1247683).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- powerpc: export MIN RMA size (bsc#1236743 ltc#211409).\n- powerpc: increase MIN RMA size for CAS negotiation (bsc#1236743 ltc#211409 bsc#1252269 ltc#215957).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Check for timeout in perf_link test (bsc#1253648).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Remove sockmap_ktls disconnect_after_delete test (bsc#1252365).\n- selftests/bpf: Remove tests for zeroed-array kptr (bsc#1252366).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- selftests/net/forwarding: add slowwait functions (bsc#1254235).\n- selftests/net/lib: no need to record ns name if it already exist (bsc#1254235).\n- selftests/net/lib: update busywait timeout value (bsc#1254235).\n- selftests/net: add lib.sh (bsc#1254235).\n- selftests/net: add variable NS_LIST for lib.sh (bsc#1254235).\n- selftests/net: use tc rule to filter the na packet (bsc#1254235).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- selftests: forwarding.config.sample: Move overrides to lib.sh (bsc#1254235).\n- selftests: forwarding: Add a test for testing lib.sh functionality (bsc#1254235).\n- selftests: forwarding: Avoid failures to source net/lib.sh (bsc#1254235).\n- selftests: forwarding: Change inappropriate log_test_skip() calls (bsc#1254235).\n- selftests: forwarding: Convert log_test() to recognize RET values (bsc#1254235).\n- selftests: forwarding: Have RET track kselftest framework constants (bsc#1254235).\n- selftests: forwarding: Parametrize mausezahn delay (bsc#1254235).\n- selftests: forwarding: Redefine relative_path variable (bsc#1254235).\n- selftests: forwarding: Remove duplicated lib.sh content (bsc#1254235).\n- selftests: forwarding: Support for performance sensitive tests (bsc#1254235).\n- selftests: lib: Define more kselftest exit codes (bsc#1254235).\n- selftests: lib: tc_rule_stats_get(): Move default to argument definition (bsc#1254235).\n- selftests: net: List helper scripts in TEST_FILES Makefile variable (bsc#1254235).\n- selftests: net: Unify code of busywait() and slowwait() (bsc#1254235).\n- selftests: net: add helper for checking if nettest is available (bsc#1254235).\n- selftests: net: lib: Do not overwrite error messages (bsc#1254235).\n- selftests: net: lib: Move logging from forwarding/lib.sh here (bsc#1254235).\n- selftests: net: lib: avoid error removing empty netns name (bsc#1254235).\n- selftests: net: lib: do not set ns var as readonly (bsc#1254235).\n- selftests: net: lib: fix shift count out of range (bsc#1254235).\n- selftests: net: lib: ignore possible errors (bsc#1254235).\n- selftests: net: lib: kill PIDs before del netns (bsc#1254235).\n- selftests: net: lib: remove 'ns' var in setup_ns (bsc#1254235).\n- selftests: net: lib: remove ns from list after clean-up (bsc#1254235).\n- selftests: net: lib: set 'i' as local (bsc#1254235).\n- selftests: net: lib: support errexit with busywait (bsc#1254235).\n- selftests: net: libs: Change variable fallback syntax (bsc#1254235).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Don't use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/hv: fcopy: Fix incorrect file path conversion (git-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: don't preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: iwlwifi: fw: Add ASUS to PPAG and TAS list (stable-fixes).\n- wifi: mac80211: Fix 6 GHz Band capabilities element advertisement in lower bands (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: Track NAN interface start/stop (stable-fixes).\n- wifi: mac80211: don't mark keys for inactive links as uploaded (stable-fixes).\n- wifi: mac80211: fix key tailroom accounting leak (git-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: rtw89: print just once for unknown C2H events (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xe/oa: Fix query mode of operation for OAR/OAC (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-15T11:09:08Z","modified":"2026-03-23T04:51:30.857607Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4422-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n\nThe following non security issues were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: don't log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Don't hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Don't treat ENTER and LEAVE as branches, because they aren't (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Don't fail destroy QP and cleanup debugfs earlier (git-fixes).\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes).\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: don't enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Don't fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: don't set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Don't use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: don't preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-17T10:52:47Z","modified":"2026-03-23T04:51:31.991873Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4505-1","title":"Security update for the Linux Kernel","description":"The 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-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes).\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes).\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes).\n- Revert 'drm/tegra: dsi: Clear enable register if powered by bootloader' (git-fixes).\n- Revert 'wifi: ath10k: avoid unnecessary wait for service ready message' (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- kabi/severities: drop xfer_to_guest_mode_handle_work.\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- powerpc: export MIN RMA size (bsc#1236743).\n- powerpc: increase MIN RMA size for CAS negotiation (bsc#1236743, bsc#1252269).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-22T16:35:13Z","modified":"2026-02-04T04:27:58.583618Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2025:4516-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40080: nbd: restrict sockets to TCP and UDP (bsc#1252774).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n- CVE-2025-40206: Add missing bugzilla reference to net fix (bsc#1250237 bsc#1253393).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tas2781: fix getting the wrong device number (git-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern() (git-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- Fix 'drm/xe: Do not allow evicting of BOs in same VM in array of VM binds' (bsc#1252923).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SEV: Enforce minimum GHCB version requirement for SEV-SNP guests (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- KVM: x86: Have all vendor neutral sub-configs depend on KVM_X86, not just KVM (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes)\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes)\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes)\n- Revert 'drm/tegra: dsi: Clear enable register if powered by bootloader' (git-fixes).\n- Revert 'wifi: ath10k: avoid unnecessary wait for service ready message' (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- acpi/hmat: Fix lockdep warning for hmem_register_resource() (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- ata: libata-scsi: Add missing scsi_device_put() in ata_scsi_dev_rescan() (git-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19 (bsc#1252368).\n- bpf: improve error message for unsupported helper (bsc#1252370).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- cgroup/cpuset: Remove remote_partition_check() \u0026 make update_cpumasks_hier() handle remote partition (bsc#1241166).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cpuset: Use new excpus for nocpu error check when enabling root partition (bsc#1241166).\n- cpuset: fix failure to enable isolated partition when containing isolcpus (bsc#1241166).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/amdgpu: Release xcp drm memory after unplug (stable-fixes).\n- drm/amd/display/dml2: Guard dml21_map_dc_state_into_dml_display_cfg with DC_FP_START (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Add fallback path for YCBCR422 (stable-fixes).\n- drm/amd/display: Allow VRR params change if unsynced with the stream (git-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Enable mst when it's detected but yet to be initialized (git-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Fix for test crash due to power gating (stable-fixes).\n- drm/amd/display: Fix incorrect return of vblank enable on unconfigured crtc (stable-fixes).\n- drm/amd/display: Fix pbn_div Calculation Error (stable-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: Increase minimum clock for TMDS 420 with pipe splitting (stable-fixes).\n- drm/amd/display: Init dispclk from bootup clock for DCN314 (stable-fixes).\n- drm/amd/display: Move setup_stream_attribute (stable-fixes).\n- drm/amd/display: Reject modes with too high pixel clock on DCE6-10 (git-fixes).\n- drm/amd/display: Reset apply_eamless_boot_optimization when dpms_off (stable-fixes).\n- drm/amd/display: Set up pixel encoding for YCBCR422 (stable-fixes).\n- drm/amd/display: Support HW cursor 180 rot for any number of pipe splits (stable-fixes).\n- drm/amd/display: Wait until OTG enable state is cleared (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: change dc stream color settings only in atomic commit (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: fix condition for setting timing_adjust_pending (stable-fixes).\n- drm/amd/display: fix dml ms order of operations (stable-fixes).\n- drm/amd/display: incorrect conditions for failing dto calculations (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Check that VPE has reached DPM0 in idle handler (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu/smu: Handle S0ix for vangogh (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Check vcn sram load return value (stable-fixes).\n- drm/amdgpu: Correct the counts of nr_banks and nr_errors (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Fix function header names in amdgpu_connectors.c (git-fixes).\n- drm/amdgpu: Fix unintended error log in VCN5_0_0 (git-fixes).\n- drm/amdgpu: Respect max pixel clock for HDMI and DVI-D (v2) (stable-fixes).\n- drm/amdgpu: Skip poison aca bank from UE channel (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add range check for RAS bad page address (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: disable peer-to-peer access for DCC-enabled GC12 VRAM surfaces (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: fix nullptr err of vm_handle_moved (stable-fixes).\n- drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdgpu: remove two invalid BUG_ON()s (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: relax checks for over allocation of save area (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/ast: Blank with VGACR17 sync enable, always clear VGACRB6 sync off (git-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/exynos: exynos7_drm_decon: remove ctx-\u003esuspended (git-fixes).\n- drm/i915/dp_mst: Work around Thunderbolt sink disconnect after SINK_COUNT_ESI read (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/mediatek: Add pm_runtime support for GCE power control (git-fixes).\n- drm/mediatek: Disable AFBC support on Mediatek DRM driver (git-fixes).\n- drm/msm/a6xx: Fix PDC sleep sequence (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm/registers: Generate _HI/LO builders for reg64 (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/panthor: Serialize GPU cache flush operations (stable-fixes).\n- drm/panthor: check bo offset alignment in vm bind (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/sched: Optimise drm_sched_entity_push_job (stable-fixes).\n- drm/sched: avoid killing parent entity on child SIGKILL (stable-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- drm/xe/guc: Add more GuC load error status codes (stable-fixes).\n- drm/xe/guc: Increase GuC crash dump buffer size (stable-fixes).\n- drm/xe/guc: Return an error code if the GuC load fails (stable-fixes).\n- drm/xe/guc: Set upper limit of H2G retries over CTB (stable-fixes).\n- drm/xe/guc: Synchronize Dead CT worker with unbind (git-fixes).\n- drm/xe: Do clean shutdown also when using flr (git-fixes).\n- drm/xe: Do not wake device during a GT reset (git-fixes).\n- drm/xe: Fix oops in xe_gem_fault when running core_hotunplug test (stable-fixes).\n- drm/xe: Move declarations under conditional branch (stable-fixes).\n- drm/xe: Remove duplicate DRM_EXEC selection from Kconfig (git-fixes).\n- drm: panel-backlight-quirks: Make EDID match optional (stable-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- hyperv: Remove the spurious null directive line (git-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- ixgbe: fix memory leak and use-after-free in ixgbe_recovery_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes) (git-fixes).\n- kabi/severities: drop xfer_to_guest_mode_handle_work.\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- media: videobuf2: forbid remove_bufs when legacy fileio is active (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- nvme-auth: add hkdf_expand_label() (bsc#1247683).\n- nvme-auth: use hkdf_expand_label() (bsc#1247683).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- powerpc: export MIN RMA size (bsc#1236743 ltc#211409).\n- powerpc: increase MIN RMA size for CAS negotiation (bsc#1236743 ltc#211409 bsc#1252269 ltc#215957).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Check for timeout in perf_link test (bsc#1253648).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Remove sockmap_ktls disconnect_after_delete test (bsc#1252365).\n- selftests/bpf: Remove tests for zeroed-array kptr (bsc#1252366).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- selftests/net/forwarding: add slowwait functions (bsc#1254235).\n- selftests/net/lib: no need to record ns name if it already exist (bsc#1254235).\n- selftests/net/lib: update busywait timeout value (bsc#1254235).\n- selftests/net: add lib.sh (bsc#1254235).\n- selftests/net: add variable NS_LIST for lib.sh (bsc#1254235).\n- selftests/net: use tc rule to filter the na packet (bsc#1254235).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- selftests: forwarding.config.sample: Move overrides to lib.sh (bsc#1254235).\n- selftests: forwarding: Add a test for testing lib.sh functionality (bsc#1254235).\n- selftests: forwarding: Avoid failures to source net/lib.sh (bsc#1254235).\n- selftests: forwarding: Change inappropriate log_test_skip() calls (bsc#1254235).\n- selftests: forwarding: Convert log_test() to recognize RET values (bsc#1254235).\n- selftests: forwarding: Have RET track kselftest framework constants (bsc#1254235).\n- selftests: forwarding: Parametrize mausezahn delay (bsc#1254235).\n- selftests: forwarding: Redefine relative_path variable (bsc#1254235).\n- selftests: forwarding: Remove duplicated lib.sh content (bsc#1254235).\n- selftests: forwarding: Support for performance sensitive tests (bsc#1254235).\n- selftests: lib: Define more kselftest exit codes (bsc#1254235).\n- selftests: lib: tc_rule_stats_get(): Move default to argument definition (bsc#1254235).\n- selftests: net: List helper scripts in TEST_FILES Makefile variable (bsc#1254235).\n- selftests: net: Unify code of busywait() and slowwait() (bsc#1254235).\n- selftests: net: add helper for checking if nettest is available (bsc#1254235).\n- selftests: net: lib: Do not overwrite error messages (bsc#1254235).\n- selftests: net: lib: Move logging from forwarding/lib.sh here (bsc#1254235).\n- selftests: net: lib: avoid error removing empty netns name (bsc#1254235).\n- selftests: net: lib: do not set ns var as readonly (bsc#1254235).\n- selftests: net: lib: fix shift count out of range (bsc#1254235).\n- selftests: net: lib: ignore possible errors (bsc#1254235).\n- selftests: net: lib: kill PIDs before del netns (bsc#1254235).\n- selftests: net: lib: remove 'ns' var in setup_ns (bsc#1254235).\n- selftests: net: lib: remove ns from list after clean-up (bsc#1254235).\n- selftests: net: lib: set 'i' as local (bsc#1254235).\n- selftests: net: lib: support errexit with busywait (bsc#1254235).\n- selftests: net: libs: Change variable fallback syntax (bsc#1254235).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/hv: fcopy: Fix incorrect file path conversion (git-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: iwlwifi: fw: Add ASUS to PPAG and TAS list (stable-fixes).\n- wifi: mac80211: Fix 6 GHz Band capabilities element advertisement in lower bands (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: Track NAN interface start/stop (stable-fixes).\n- wifi: mac80211: do not mark keys for inactive links as uploaded (stable-fixes).\n- wifi: mac80211: fix key tailroom accounting leak (git-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: rtw89: print just once for unknown C2H events (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xe/oa: Fix query mode of operation for OAR/OAC (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-23T16:27:39Z","modified":"2026-03-23T04:49:23.610108Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2025:4517-1","title":"Security update for the Linux Kernel","description":"The 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-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38360: drm/amd/display: Add more checks for DSC / HUBP ONO guarantees (bsc#1247078).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tas2781: fix getting the wrong device number (git-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern() (git-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SEV: Enforce minimum GHCB version requirement for SEV-SNP guests (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- KVM: x86: Have all vendor neutral sub-configs depend on KVM_X86, not just KVM (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes).\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes).\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes).\n- Revert 'drm/tegra: dsi: Clear enable register if powered by bootloader' (git-fixes).\n- Revert 'wifi: ath10k: avoid unnecessary wait for service ready message' (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- acpi/hmat: Fix lockdep warning for hmem_register_resource() (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- ata: libata-scsi: Add missing scsi_device_put() in ata_scsi_dev_rescan() (git-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19 (bsc#1252368).\n- bpf: improve error message for unsupported helper (bsc#1252370).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- cgroup/cpuset: Remove remote_partition_check() \u0026 make update_cpumasks_hier() handle remote partition (bsc#1241166).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cpuset: Use new excpus for nocpu error check when enabling root partition (bsc#1241166).\n- cpuset: fix failure to enable isolated partition when containing isolcpus (bsc#1241166).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/amdgpu: Release xcp drm memory after unplug (stable-fixes).\n- drm/amd/display/dml2: Guard dml21_map_dc_state_into_dml_display_cfg with DC_FP_START (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Add fallback path for YCBCR422 (stable-fixes).\n- drm/amd/display: Allow VRR params change if unsynced with the stream (git-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Enable mst when it's detected but yet to be initialized (git-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Fix for test crash due to power gating (stable-fixes).\n- drm/amd/display: Fix incorrect return of vblank enable on unconfigured crtc (stable-fixes).\n- drm/amd/display: Fix pbn_div Calculation Error (stable-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: Increase minimum clock for TMDS 420 with pipe splitting (stable-fixes).\n- drm/amd/display: Init dispclk from bootup clock for DCN314 (stable-fixes).\n- drm/amd/display: Move setup_stream_attribute (stable-fixes).\n- drm/amd/display: Reject modes with too high pixel clock on DCE6-10 (git-fixes).\n- drm/amd/display: Reset apply_eamless_boot_optimization when dpms_off (stable-fixes).\n- drm/amd/display: Set up pixel encoding for YCBCR422 (stable-fixes).\n- drm/amd/display: Support HW cursor 180 rot for any number of pipe splits (stable-fixes).\n- drm/amd/display: Wait until OTG enable state is cleared (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: change dc stream color settings only in atomic commit (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: fix condition for setting timing_adjust_pending (stable-fixes).\n- drm/amd/display: fix dml ms order of operations (stable-fixes).\n- drm/amd/display: incorrect conditions for failing dto calculations (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Check that VPE has reached DPM0 in idle handler (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu/smu: Handle S0ix for vangogh (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Check vcn sram load return value (stable-fixes).\n- drm/amdgpu: Correct the counts of nr_banks and nr_errors (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Fix function header names in amdgpu_connectors.c (git-fixes).\n- drm/amdgpu: Fix unintended error log in VCN5_0_0 (git-fixes).\n- drm/amdgpu: Respect max pixel clock for HDMI and DVI-D (v2) (stable-fixes).\n- drm/amdgpu: Skip poison aca bank from UE channel (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add range check for RAS bad page address (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: disable peer-to-peer access for DCC-enabled GC12 VRAM surfaces (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: fix nullptr err of vm_handle_moved (stable-fixes).\n- drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdgpu: remove two invalid BUG_ON()s (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: relax checks for over allocation of save area (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/ast: Blank with VGACR17 sync enable, always clear VGACRB6 sync off (git-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/exynos: exynos7_drm_decon: remove ctx-\u003esuspended (git-fixes).\n- drm/i915/dp_mst: Work around Thunderbolt sink disconnect after SINK_COUNT_ESI read (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/mediatek: Add pm_runtime support for GCE power control (git-fixes).\n- drm/mediatek: Disable AFBC support on Mediatek DRM driver (git-fixes).\n- drm/msm/a6xx: Fix PDC sleep sequence (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm/registers: Generate _HI/LO builders for reg64 (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/panthor: Serialize GPU cache flush operations (stable-fixes).\n- drm/panthor: check bo offset alignment in vm bind (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/sched: Optimise drm_sched_entity_push_job (stable-fixes).\n- drm/sched: avoid killing parent entity on child SIGKILL (stable-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- drm/xe/guc: Add more GuC load error status codes (stable-fixes).\n- drm/xe/guc: Increase GuC crash dump buffer size (stable-fixes).\n- drm/xe/guc: Return an error code if the GuC load fails (stable-fixes).\n- drm/xe/guc: Set upper limit of H2G retries over CTB (stable-fixes).\n- drm/xe/guc: Synchronize Dead CT worker with unbind (git-fixes).\n- drm/xe: Do clean shutdown also when using flr (git-fixes).\n- drm/xe: Do not wake device during a GT reset (git-fixes).\n- drm/xe: Fix oops in xe_gem_fault when running core_hotunplug test (stable-fixes).\n- drm/xe: Move declarations under conditional branch (stable-fixes).\n- drm/xe: Remove duplicate DRM_EXEC selection from Kconfig (git-fixes).\n- drm: panel-backlight-quirks: Make EDID match optional (stable-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- hyperv: Remove the spurious null directive line (git-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- ixgbe: fix memory leak and use-after-free in ixgbe_recovery_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- kabi/severities: drop xfer_to_guest_mode_handle_work.\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- media: videobuf2: forbid remove_bufs when legacy fileio is active (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- nvme-auth: add hkdf_expand_label() (bsc#1247683).\n- nvme-auth: use hkdf_expand_label() (bsc#1247683).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- powerpc: export MIN RMA size (bsc#1236743).\n- powerpc: increase MIN RMA size for CAS negotiation (bsc#1236743, bsc#1252269).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Check for timeout in perf_link test (bsc#1253648).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Remove sockmap_ktls disconnect_after_delete test (bsc#1252365).\n- selftests/bpf: Remove tests for zeroed-array kptr (bsc#1252366).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- selftests/net/forwarding: add slowwait functions (bsc#1254235).\n- selftests/net/lib: no need to record ns name if it already exist (bsc#1254235).\n- selftests/net/lib: update busywait timeout value (bsc#1254235).\n- selftests/net: add lib.sh (bsc#1254235).\n- selftests/net: add variable NS_LIST for lib.sh (bsc#1254235).\n- selftests/net: use tc rule to filter the na packet (bsc#1254235).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- selftests: forwarding.config.sample: Move overrides to lib.sh (bsc#1254235).\n- selftests: forwarding: Add a test for testing lib.sh functionality (bsc#1254235).\n- selftests: forwarding: Avoid failures to source net/lib.sh (bsc#1254235).\n- selftests: forwarding: Change inappropriate log_test_skip() calls (bsc#1254235).\n- selftests: forwarding: Convert log_test() to recognize RET values (bsc#1254235).\n- selftests: forwarding: Have RET track kselftest framework constants (bsc#1254235).\n- selftests: forwarding: Parametrize mausezahn delay (bsc#1254235).\n- selftests: forwarding: Redefine relative_path variable (bsc#1254235).\n- selftests: forwarding: Remove duplicated lib.sh content (bsc#1254235).\n- selftests: forwarding: Support for performance sensitive tests (bsc#1254235).\n- selftests: lib: Define more kselftest exit codes (bsc#1254235).\n- selftests: lib: tc_rule_stats_get(): Move default to argument definition (bsc#1254235).\n- selftests: net: List helper scripts in TEST_FILES Makefile variable (bsc#1254235).\n- selftests: net: Unify code of busywait() and slowwait() (bsc#1254235).\n- selftests: net: add helper for checking if nettest is available (bsc#1254235).\n- selftests: net: lib: Do not overwrite error messages (bsc#1254235).\n- selftests: net: lib: Move logging from forwarding/lib.sh here (bsc#1254235).\n- selftests: net: lib: avoid error removing empty netns name (bsc#1254235).\n- selftests: net: lib: do not set ns var as readonly (bsc#1254235).\n- selftests: net: lib: fix shift count out of range (bsc#1254235).\n- selftests: net: lib: ignore possible errors (bsc#1254235).\n- selftests: net: lib: kill PIDs before del netns (bsc#1254235).\n- selftests: net: lib: remove 'ns' var in setup_ns (bsc#1254235).\n- selftests: net: lib: remove ns from list after clean-up (bsc#1254235).\n- selftests: net: lib: set 'i' as local (bsc#1254235).\n- selftests: net: lib: support errexit with busywait (bsc#1254235).\n- selftests: net: libs: Change variable fallback syntax (bsc#1254235).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/hv: fcopy: Fix incorrect file path conversion (git-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: iwlwifi: fw: Add ASUS to PPAG and TAS list (stable-fixes).\n- wifi: mac80211: Fix 6 GHz Band capabilities element advertisement in lower bands (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: Track NAN interface start/stop (stable-fixes).\n- wifi: mac80211: do not mark keys for inactive links as uploaded (stable-fixes).\n- wifi: mac80211: fix key tailroom accounting leak (git-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: rtw89: print just once for unknown C2H events (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xe/oa: Fix query mode of operation for OAR/OAC (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-23T16:28:51Z","modified":"2026-03-23T04:51:51.09247Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2025:4521-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes).\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes).\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes).\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes).\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes).\n- RDMA/irdma: Fix SD index calculation (git-fixes).\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes).\n- Revert 'drm/tegra: dsi: Clear enable register if powered by bootloader' (git-fixes).\n- Revert 'wifi: ath10k: avoid unnecessary wait for service ready message' (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- kabi/severities: drop xfer_to_guest_mode_handle_work.\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2025-12-24T12:42:49Z","modified":"2026-03-23T04:49:23.294846Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2026:20012-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431 bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39831: fbnic: Move phylink resume out of service_task and into open/close (bsc#1249977).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39897: net: xilinx: axienet: Add error handling for RX metadata pointer retrieval (bsc#1250746).\n- CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt (bsc#1250723).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39961: iommu/amd/pgtbl: Fix possible race while increase page table level (bsc#1251817).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-39990: bpf: Check the helper function is valid in get_helper_proto (bsc#1252054).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work (bsc#1252301).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40031: tee: fix register_shm_helper() (bsc#1252779).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: tcp: convert to dev_net_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (bsc#1252901).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40133: mptcp: Call dst_release() in mptcp_active_enable() (bsc#1253328).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (bsc#1253423).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40175: idpf: cleanup remaining SKBs in PTP flows (bsc#1253426).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40203: listmount: don't call path_put() under namespace semaphore (bsc#1253457).\n\nThe following non security issues were fixed:\n\n- ACPI: scan: Update honor list for RPMI System MSI (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Fix \"drm/xe: Don't allow evicting of BOs in same VM in array of VM binds\" (bsc#1252923)\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault (git-fixes).\n- PCI/ERR: Update device error_state already after reset (stable-fixes).\n- PM: EM: Slightly reduce em_check_capacity_update() overhead (stable-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon MTU set\" (git-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon port speed set\" (git-fixes).\n- Update config files: enable zstd module decompression (jsc#PED-14115).\n- bpf/selftests: Fix test_tcpnotify_user (bsc#1253635).\n- btrfs: do not clear read-only when adding sprout device (bsc#1253238).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- hwmon: (lenovo-ec-sensors) Update P8 supprt (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- mount: handle NULL values in mnt_ns_release() (bsc#1254308)\n- net/smc: Remove validation of reserved bits in CLC Decline (bsc#1252357).\n- net: phy: move realtek PHY driver to its own subdirectory (jsc#PED-14353).\n- net: phy: realtek: add defines for shadowed c45 standard registers (jsc#PED-14353).\n- net: phy: realtek: add helper RTL822X_VND2_C22_REG (jsc#PED-14353).\n- net: phy: realtek: change order of calls in C22 read_status() (jsc#PED-14353).\n- net: phy: realtek: clear 1000Base-T link partner advertisement (jsc#PED-14353).\n- net: phy: realtek: improve mmd register access for internal PHY's (jsc#PED-14353).\n- net: phy: realtek: read duplex and gbit master from PHYSR register (jsc#PED-14353).\n- net: phy: realtek: switch from paged to MMD ops in rtl822x functions (jsc#PED-14353).\n- net: phy: realtek: use string choices helpers (jsc#PED-14353).\n- net: xilinx: axienet: Fix IRQ coalescing packet count overflow (bsc#1250746)\n- net: xilinx: axienet: Fix RX skb ring management in DMAengine mode (bsc#1250746)\n- net: xilinx: axienet: Fix Tx skb circular buffer occupancy check in dmaengine xmit (bsc#1250746)\n- nvmet-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- perf list: Add IBM z17 event descriptions (jsc#PED-13611).\n- platform/x86:intel/pmc: Update Arrow Lake telemetry GUID (git-fixes).\n- powercap: intel_rapl: Add support for Panther Lake platform (jsc#PED-13949).\n- pwm: pca9685: Use bulk write to atomicially update registers (stable-fixes).\n- r8169: add PHY c45 ops for MDIO_MMD_VENDOR2 registers (jsc#PED-14353).\n- r8169: add support for Intel Killer E5000 (jsc#PED-14353).\n- r8169: add support for RTL8125BP rev.b (jsc#PED-14353).\n- r8169: add support for RTL8125D rev.b (jsc#PED-14353).\n- r8169: adjust version numbering for RTL8126 (jsc#PED-14353).\n- r8169: align RTL8125 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8125/RTL8126 PHY config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8126 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align WAKE_PHY handling with r8125/r8126 vendor drivers (jsc#PED-14353).\n- r8169: avoid duplicated messages if loading firmware fails and switch to warn level (jsc#PED-14353).\n- r8169: don't take RTNL lock in rtl_task() (jsc#PED-14353).\n- r8169: enable EEE at 2.5G per default on RTL8125B (jsc#PED-14353).\n- r8169: enable RTL8168H/RTL8168EP/RTL8168FP ASPM support (jsc#PED-14353).\n- r8169: fix inconsistent indenting in rtl8169_get_eth_mac_stats (jsc#PED-14353).\n- r8169: implement additional ethtool stats ops (jsc#PED-14353).\n- r8169: improve __rtl8169_set_wol (jsc#PED-14353).\n- r8169: improve initialization of RSS registers on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: improve rtl_set_d3_pll_down (jsc#PED-14353).\n- r8169: increase max jumbo packet size on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: remove leftover locks after reverted change (jsc#PED-14353).\n- r8169: remove original workaround for RTL8125 broken rx issue (jsc#PED-14353).\n- r8169: remove rtl_dash_loop_wait_high/low (jsc#PED-14353).\n- r8169: remove support for chip version 11 (jsc#PED-14353).\n- r8169: remove unused flag RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE (jsc#PED-14353).\n- r8169: replace custom flag with disable_work() et al (jsc#PED-14353).\n- r8169: switch away from deprecated pcim_iomap_table (jsc#PED-14353).\n- r8169: use helper r8169_mod_reg8_cond to simplify rtl_jumbo_config (jsc#PED-14353).\n- ring-buffer: Update pages_touched to reflect persistent buffer content (git-fixes).\n- s390/mm: Fix __ptep_rdp() inline assembly (bsc#1253643).\n- sched/fair: Get rid of sched_domains_curr_level hack for tl-\u003ecpumask() (bsc#1246843).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1248792).\n- sched/fair: Proportional newidle balance (bsc#1248792).\n- sched/fair: Proportional newidle balance -KABI (bsc#1248792).\n- sched/fair: Revert max_newidle_lb_cost bump (bsc#1248792).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1248792).\n- sched/fair: Small cleanup to sched_balance_newidle() (bsc#1248792).\n- sched/fair: Small cleanup to update_newidle_cost() (bsc#1248792).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- smpboot: introduce SDTL_INIT() helper to tidy sched topology setup (bsc#1246843).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: mt76: do not add wcid entries to sta poll list during MCU reset (bsc#1254315).\n- wifi: mt76: introduce mt792x_config_mac_addr_list routine (bsc#1254315).\n- wifi: mt76: mt7925: Fix logical vs bitwise typo (bsc#1254315).\n- wifi: mt76: mt7925: Remove unnecessary if-check (bsc#1254315).\n- wifi: mt76: mt7925: Simplify HIF suspend handling to avoid suspend fail (bsc#1254315).\n- wifi: mt76: mt7925: add EHT control support based on the CLC data (bsc#1254315).\n- wifi: mt76: mt7925: add handler to hif suspend/resume event (bsc#1254315).\n- wifi: mt76: mt7925: add pci restore for hibernate (bsc#1254315).\n- wifi: mt76: mt7925: config the dwell time by firmware (bsc#1254315).\n- wifi: mt76: mt7925: extend MCU support for testmode (bsc#1254315).\n- wifi: mt76: mt7925: fix CLC command timeout when suspend/resume (bsc#1254315).\n- wifi: mt76: mt7925: fix missing hdr_trans_tlv command for broadcast wtbl (bsc#1254315).\n- wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend (bsc#1254315).\n- wifi: mt76: mt7925: refine the txpower initialization flow (bsc#1254315).\n- wifi: mt76: mt7925: replace zero-length array with flexible-array member (bsc#1254315).\n- wifi: mt76: mt7925: update the channel usage when the regd domain changed (bsc#1254315).\n- wifi: mt76: mt7925e: fix too long of wifi resume time (bsc#1254315).\n- x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled (bsc#1246843).\n- x86/smpboot: moves x86_topology to static initialize and truncate (bsc#1246843).\n- x86/smpboot: remove redundant CONFIG_SCHED_SMT (bsc#1246843).\n","status":"published","published":"2025-12-19T16:46:47Z","modified":"2026-03-23T04:52:29.286643Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20015-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431 bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39831: fbnic: Move phylink resume out of service_task and into open/close (bsc#1249977).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39897: net: xilinx: axienet: Add error handling for RX metadata pointer retrieval (bsc#1250746).\n- CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt (bsc#1250723).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39961: iommu/amd/pgtbl: Fix possible race while increase page table level (bsc#1251817).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-39990: bpf: Check the helper function is valid in get_helper_proto (bsc#1252054).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work (bsc#1252301).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40031: tee: fix register_shm_helper() (bsc#1252779).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: tcp: convert to dev_net_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (bsc#1252901).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40133: mptcp: Call dst_release() in mptcp_active_enable() (bsc#1253328).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (bsc#1253423).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40175: idpf: cleanup remaining SKBs in PTP flows (bsc#1253426).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40203: listmount: don't call path_put() under namespace semaphore (bsc#1253457).\n\nThe following non security issues were fixed:\n\n- ACPI: scan: Update honor list for RPMI System MSI (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Fix \"drm/xe: Don't allow evicting of BOs in same VM in array of VM binds\" (bsc#1252923)\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault (git-fixes).\n- PCI/ERR: Update device error_state already after reset (stable-fixes).\n- PM: EM: Slightly reduce em_check_capacity_update() overhead (stable-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon MTU set\" (git-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon port speed set\" (git-fixes).\n- Update config files: enable zstd module decompression (jsc#PED-14115).\n- bpf/selftests: Fix test_tcpnotify_user (bsc#1253635).\n- btrfs: do not clear read-only when adding sprout device (bsc#1253238).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- hwmon: (lenovo-ec-sensors) Update P8 supprt (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- mount: handle NULL values in mnt_ns_release() (bsc#1254308)\n- net/smc: Remove validation of reserved bits in CLC Decline (bsc#1252357).\n- net: phy: move realtek PHY driver to its own subdirectory (jsc#PED-14353).\n- net: phy: realtek: add defines for shadowed c45 standard registers (jsc#PED-14353).\n- net: phy: realtek: add helper RTL822X_VND2_C22_REG (jsc#PED-14353).\n- net: phy: realtek: change order of calls in C22 read_status() (jsc#PED-14353).\n- net: phy: realtek: clear 1000Base-T link partner advertisement (jsc#PED-14353).\n- net: phy: realtek: improve mmd register access for internal PHY's (jsc#PED-14353).\n- net: phy: realtek: read duplex and gbit master from PHYSR register (jsc#PED-14353).\n- net: phy: realtek: switch from paged to MMD ops in rtl822x functions (jsc#PED-14353).\n- net: phy: realtek: use string choices helpers (jsc#PED-14353).\n- net: xilinx: axienet: Fix IRQ coalescing packet count overflow (bsc#1250746)\n- net: xilinx: axienet: Fix RX skb ring management in DMAengine mode (bsc#1250746)\n- net: xilinx: axienet: Fix Tx skb circular buffer occupancy check in dmaengine xmit (bsc#1250746)\n- nvmet-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- perf list: Add IBM z17 event descriptions (jsc#PED-13611).\n- platform/x86:intel/pmc: Update Arrow Lake telemetry GUID (git-fixes).\n- powercap: intel_rapl: Add support for Panther Lake platform (jsc#PED-13949).\n- pwm: pca9685: Use bulk write to atomicially update registers (stable-fixes).\n- r8169: add PHY c45 ops for MDIO_MMD_VENDOR2 registers (jsc#PED-14353).\n- r8169: add support for Intel Killer E5000 (jsc#PED-14353).\n- r8169: add support for RTL8125BP rev.b (jsc#PED-14353).\n- r8169: add support for RTL8125D rev.b (jsc#PED-14353).\n- r8169: adjust version numbering for RTL8126 (jsc#PED-14353).\n- r8169: align RTL8125 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8125/RTL8126 PHY config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8126 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align WAKE_PHY handling with r8125/r8126 vendor drivers (jsc#PED-14353).\n- r8169: avoid duplicated messages if loading firmware fails and switch to warn level (jsc#PED-14353).\n- r8169: don't take RTNL lock in rtl_task() (jsc#PED-14353).\n- r8169: enable EEE at 2.5G per default on RTL8125B (jsc#PED-14353).\n- r8169: enable RTL8168H/RTL8168EP/RTL8168FP ASPM support (jsc#PED-14353).\n- r8169: fix inconsistent indenting in rtl8169_get_eth_mac_stats (jsc#PED-14353).\n- r8169: implement additional ethtool stats ops (jsc#PED-14353).\n- r8169: improve __rtl8169_set_wol (jsc#PED-14353).\n- r8169: improve initialization of RSS registers on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: improve rtl_set_d3_pll_down (jsc#PED-14353).\n- r8169: increase max jumbo packet size on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: remove leftover locks after reverted change (jsc#PED-14353).\n- r8169: remove original workaround for RTL8125 broken rx issue (jsc#PED-14353).\n- r8169: remove rtl_dash_loop_wait_high/low (jsc#PED-14353).\n- r8169: remove support for chip version 11 (jsc#PED-14353).\n- r8169: remove unused flag RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE (jsc#PED-14353).\n- r8169: replace custom flag with disable_work() et al (jsc#PED-14353).\n- r8169: switch away from deprecated pcim_iomap_table (jsc#PED-14353).\n- r8169: use helper r8169_mod_reg8_cond to simplify rtl_jumbo_config (jsc#PED-14353).\n- ring-buffer: Update pages_touched to reflect persistent buffer content (git-fixes).\n- s390/mm: Fix __ptep_rdp() inline assembly (bsc#1253643).\n- sched/fair: Get rid of sched_domains_curr_level hack for tl-\u003ecpumask() (bsc#1246843).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1248792).\n- sched/fair: Proportional newidle balance (bsc#1248792).\n- sched/fair: Proportional newidle balance -KABI (bsc#1248792).\n- sched/fair: Revert max_newidle_lb_cost bump (bsc#1248792).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1248792).\n- sched/fair: Small cleanup to sched_balance_newidle() (bsc#1248792).\n- sched/fair: Small cleanup to update_newidle_cost() (bsc#1248792).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- smpboot: introduce SDTL_INIT() helper to tidy sched topology setup (bsc#1246843).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: mt76: do not add wcid entries to sta poll list during MCU reset (bsc#1254315).\n- wifi: mt76: introduce mt792x_config_mac_addr_list routine (bsc#1254315).\n- wifi: mt76: mt7925: Fix logical vs bitwise typo (bsc#1254315).\n- wifi: mt76: mt7925: Remove unnecessary if-check (bsc#1254315).\n- wifi: mt76: mt7925: Simplify HIF suspend handling to avoid suspend fail (bsc#1254315).\n- wifi: mt76: mt7925: add EHT control support based on the CLC data (bsc#1254315).\n- wifi: mt76: mt7925: add handler to hif suspend/resume event (bsc#1254315).\n- wifi: mt76: mt7925: add pci restore for hibernate (bsc#1254315).\n- wifi: mt76: mt7925: config the dwell time by firmware (bsc#1254315).\n- wifi: mt76: mt7925: extend MCU support for testmode (bsc#1254315).\n- wifi: mt76: mt7925: fix CLC command timeout when suspend/resume (bsc#1254315).\n- wifi: mt76: mt7925: fix missing hdr_trans_tlv command for broadcast wtbl (bsc#1254315).\n- wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend (bsc#1254315).\n- wifi: mt76: mt7925: refine the txpower initialization flow (bsc#1254315).\n- wifi: mt76: mt7925: replace zero-length array with flexible-array member (bsc#1254315).\n- wifi: mt76: mt7925: update the channel usage when the regd domain changed (bsc#1254315).\n- wifi: mt76: mt7925e: fix too long of wifi resume time (bsc#1254315).\n- x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled (bsc#1246843).\n- x86/smpboot: moves x86_topology to static initialize and truncate (bsc#1246843).\n- x86/smpboot: remove redundant CONFIG_SCHED_SMT (bsc#1246843).\n","status":"published","published":"2025-12-19T16:46:47Z","modified":"2026-03-23T04:52:29.41877Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20021-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431 bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39831: fbnic: Move phylink resume out of service_task and into open/close (bsc#1249977).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39897: net: xilinx: axienet: Add error handling for RX metadata pointer retrieval (bsc#1250746).\n- CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt (bsc#1250723).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39961: iommu/amd/pgtbl: Fix possible race while increase page table level (bsc#1251817).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-39990: bpf: Check the helper function is valid in get_helper_proto (bsc#1252054).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work (bsc#1252301).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40031: tee: fix register_shm_helper() (bsc#1252779).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: tcp: convert to dev_net_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (bsc#1252901).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40133: mptcp: Call dst_release() in mptcp_active_enable() (bsc#1253328).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (bsc#1253423).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40175: idpf: cleanup remaining SKBs in PTP flows (bsc#1253426).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40203: listmount: don't call path_put() under namespace semaphore (bsc#1253457).\n\nThe following non security issues were fixed:\n\n- ACPI: scan: Update honor list for RPMI System MSI (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Fix \"drm/xe: Don't allow evicting of BOs in same VM in array of VM binds\" (bsc#1252923)\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault (git-fixes).\n- PCI/ERR: Update device error_state already after reset (stable-fixes).\n- PM: EM: Slightly reduce em_check_capacity_update() overhead (stable-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon MTU set\" (git-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon port speed set\" (git-fixes).\n- Update config files: enable zstd module decompression (jsc#PED-14115).\n- bpf/selftests: Fix test_tcpnotify_user (bsc#1253635).\n- btrfs: do not clear read-only when adding sprout device (bsc#1253238).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- hwmon: (lenovo-ec-sensors) Update P8 supprt (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- mount: handle NULL values in mnt_ns_release() (bsc#1254308)\n- net/smc: Remove validation of reserved bits in CLC Decline (bsc#1252357).\n- net: phy: move realtek PHY driver to its own subdirectory (jsc#PED-14353).\n- net: phy: realtek: add defines for shadowed c45 standard registers (jsc#PED-14353).\n- net: phy: realtek: add helper RTL822X_VND2_C22_REG (jsc#PED-14353).\n- net: phy: realtek: change order of calls in C22 read_status() (jsc#PED-14353).\n- net: phy: realtek: clear 1000Base-T link partner advertisement (jsc#PED-14353).\n- net: phy: realtek: improve mmd register access for internal PHY's (jsc#PED-14353).\n- net: phy: realtek: read duplex and gbit master from PHYSR register (jsc#PED-14353).\n- net: phy: realtek: switch from paged to MMD ops in rtl822x functions (jsc#PED-14353).\n- net: phy: realtek: use string choices helpers (jsc#PED-14353).\n- net: xilinx: axienet: Fix IRQ coalescing packet count overflow (bsc#1250746)\n- net: xilinx: axienet: Fix RX skb ring management in DMAengine mode (bsc#1250746)\n- net: xilinx: axienet: Fix Tx skb circular buffer occupancy check in dmaengine xmit (bsc#1250746)\n- nvmet-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- perf list: Add IBM z17 event descriptions (jsc#PED-13611).\n- platform/x86:intel/pmc: Update Arrow Lake telemetry GUID (git-fixes).\n- powercap: intel_rapl: Add support for Panther Lake platform (jsc#PED-13949).\n- pwm: pca9685: Use bulk write to atomicially update registers (stable-fixes).\n- r8169: add PHY c45 ops for MDIO_MMD_VENDOR2 registers (jsc#PED-14353).\n- r8169: add support for Intel Killer E5000 (jsc#PED-14353).\n- r8169: add support for RTL8125BP rev.b (jsc#PED-14353).\n- r8169: add support for RTL8125D rev.b (jsc#PED-14353).\n- r8169: adjust version numbering for RTL8126 (jsc#PED-14353).\n- r8169: align RTL8125 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8125/RTL8126 PHY config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8126 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align WAKE_PHY handling with r8125/r8126 vendor drivers (jsc#PED-14353).\n- r8169: avoid duplicated messages if loading firmware fails and switch to warn level (jsc#PED-14353).\n- r8169: don't take RTNL lock in rtl_task() (jsc#PED-14353).\n- r8169: enable EEE at 2.5G per default on RTL8125B (jsc#PED-14353).\n- r8169: enable RTL8168H/RTL8168EP/RTL8168FP ASPM support (jsc#PED-14353).\n- r8169: fix inconsistent indenting in rtl8169_get_eth_mac_stats (jsc#PED-14353).\n- r8169: implement additional ethtool stats ops (jsc#PED-14353).\n- r8169: improve __rtl8169_set_wol (jsc#PED-14353).\n- r8169: improve initialization of RSS registers on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: improve rtl_set_d3_pll_down (jsc#PED-14353).\n- r8169: increase max jumbo packet size on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: remove leftover locks after reverted change (jsc#PED-14353).\n- r8169: remove original workaround for RTL8125 broken rx issue (jsc#PED-14353).\n- r8169: remove rtl_dash_loop_wait_high/low (jsc#PED-14353).\n- r8169: remove support for chip version 11 (jsc#PED-14353).\n- r8169: remove unused flag RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE (jsc#PED-14353).\n- r8169: replace custom flag with disable_work() et al (jsc#PED-14353).\n- r8169: switch away from deprecated pcim_iomap_table (jsc#PED-14353).\n- r8169: use helper r8169_mod_reg8_cond to simplify rtl_jumbo_config (jsc#PED-14353).\n- ring-buffer: Update pages_touched to reflect persistent buffer content (git-fixes).\n- s390/mm: Fix __ptep_rdp() inline assembly (bsc#1253643).\n- sched/fair: Get rid of sched_domains_curr_level hack for tl-\u003ecpumask() (bsc#1246843).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1248792).\n- sched/fair: Proportional newidle balance (bsc#1248792).\n- sched/fair: Proportional newidle balance -KABI (bsc#1248792).\n- sched/fair: Revert max_newidle_lb_cost bump (bsc#1248792).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1248792).\n- sched/fair: Small cleanup to sched_balance_newidle() (bsc#1248792).\n- sched/fair: Small cleanup to update_newidle_cost() (bsc#1248792).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- smpboot: introduce SDTL_INIT() helper to tidy sched topology setup (bsc#1246843).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: mt76: do not add wcid entries to sta poll list during MCU reset (bsc#1254315).\n- wifi: mt76: introduce mt792x_config_mac_addr_list routine (bsc#1254315).\n- wifi: mt76: mt7925: Fix logical vs bitwise typo (bsc#1254315).\n- wifi: mt76: mt7925: Remove unnecessary if-check (bsc#1254315).\n- wifi: mt76: mt7925: Simplify HIF suspend handling to avoid suspend fail (bsc#1254315).\n- wifi: mt76: mt7925: add EHT control support based on the CLC data (bsc#1254315).\n- wifi: mt76: mt7925: add handler to hif suspend/resume event (bsc#1254315).\n- wifi: mt76: mt7925: add pci restore for hibernate (bsc#1254315).\n- wifi: mt76: mt7925: config the dwell time by firmware (bsc#1254315).\n- wifi: mt76: mt7925: extend MCU support for testmode (bsc#1254315).\n- wifi: mt76: mt7925: fix CLC command timeout when suspend/resume (bsc#1254315).\n- wifi: mt76: mt7925: fix missing hdr_trans_tlv command for broadcast wtbl (bsc#1254315).\n- wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend (bsc#1254315).\n- wifi: mt76: mt7925: refine the txpower initialization flow (bsc#1254315).\n- wifi: mt76: mt7925: replace zero-length array with flexible-array member (bsc#1254315).\n- wifi: mt76: mt7925: update the channel usage when the regd domain changed (bsc#1254315).\n- wifi: mt76: mt7925e: fix too long of wifi resume time (bsc#1254315).\n- x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled (bsc#1246843).\n- x86/smpboot: moves x86_topology to static initialize and truncate (bsc#1246843).\n- x86/smpboot: remove redundant CONFIG_SCHED_SMT (bsc#1246843).\n","status":"published","published":"2025-12-19T16:19:41Z","modified":"2026-03-23T04:52:29.761107Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20039-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\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: net: dst_cache: annotate data-races around dst_cache-\u003ereset_ts (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n- CVE-2025-40206: Add missing bugzilla reference to net fix (bsc#1250237 bsc#1253393).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes)\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes)\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes)\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes)\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes)\n- RDMA/irdma: Fix SD index calculation (git-fixes)\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes)\n- Revert \"drm/tegra: dsi: Clear enable register if powered by bootloader\" (git-fixes).\n- Revert \"wifi: ath10k: avoid unnecessary wait for service ready message\" (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes) (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2026-01-07T12:33:45Z","modified":"2026-03-23T04:52:31.109155Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20059-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\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: net: dst_cache: annotate data-races around dst_cache-\u003ereset_ts (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n- CVE-2025-40206: Add missing bugzilla reference to net fix (bsc#1250237 bsc#1253393).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes)\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes)\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes)\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes)\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes)\n- RDMA/irdma: Fix SD index calculation (git-fixes)\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes)\n- Revert \"drm/tegra: dsi: Clear enable register if powered by bootloader\" (git-fixes).\n- Revert \"wifi: ath10k: avoid unnecessary wait for service ready message\" (git-fixes).\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- kABI fix for KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes) (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2026-01-07T10:55:44Z","modified":"2026-03-23T04:52:33.099373Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20473-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\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Do not leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n- CVE-2025-40206: Add missing bugzilla reference to net fix (bsc#1253393).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes) (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes)\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes)\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes)\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes)\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes)\n- RDMA/irdma: Fix SD index calculation (git-fixes)\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes)\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2026-02-19T16:55:02Z","modified":"2026-03-23T04:51:38.764552Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20496-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\n\nThe following security bugs were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).\n- CVE-2025-21710: tcp: correct handling of extreme memory squeeze (bsc#1237888).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38359: s390/mm: Fix in_atomic() handling in do_secure_storage_access() (bsc#1247076).\n- CVE-2025-38361: drm/amd/display: Check dce_hwseq before dereferencing it (bsc#1247079).\n- CVE-2025-39788: scsi: ufs: exynos: Fix programming of HCI_UTRL_NEXUS_TYPE (bsc#1249547).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).\n- CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: ipv4: start using dst_dev_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40105: vfs: Do not leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).\n- CVE-2025-40206: Add missing bugzilla reference to net fix (bsc#1253393).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Check _CPC validity for only the online CPUs (git-fixes).\n- ACPI: CPPC: Limit perf ctrs in PCC check only to online CPUs (git-fixes).\n- ACPI: CPPC: Perform fast check switch only for online CPUs (git-fixes).\n- ACPI: PRM: Skip handlers with NULL handler_address or NULL VA (stable-fixes).\n- ACPI: SBS: Fix present test in acpi_battery_read() (git-fixes).\n- ACPI: property: Return present device nodes only on fwnode interface (stable-fixes).\n- ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- ACPICA: dispatcher: Use acpi_ds_clear_operands() in acpi_ds_call_control_method() (stable-fixes).\n- ALSA: hda: Fix missing pointer check in hda_component_manager_init function (git-fixes).\n- ALSA: serial-generic: remove shared static buffer (stable-fixes).\n- ALSA: usb-audio: Add validation of UAC2/UAC3 effect units (stable-fixes).\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd (git-fixes).\n- ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (stable-fixes).\n- ALSA: usb-audio: add mono main switch to Presonus S1824c (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP Quark2 (stable-fixes).\n- ALSA: usb-audio: do not log messages meant for 1810c when initializing 1824c (git-fixes).\n- ALSA: usb-audio: fix uac2 clock source at terminal parser (git-fixes).\n- ASoC: codecs: va-macro: fix resource leak in probe error path (git-fixes).\n- ASoC: cs4271: Fix regulator leak on probe failure (git-fixes).\n- ASoC: max98090/91: fixed max98091 ALSA widget powering up/down (stable-fixes).\n- ASoC: meson: aiu-encoder-i2s: fix bit clock polarity (stable-fixes).\n- ASoC: qcom: sc8280xp: explicitly set S16LE format in sc8280xp_be_hw_params_fixup() (stable-fixes).\n- ASoC: stm32: sai: manage context in set_sysclk callback (stable-fixes).\n- ASoC: tlv320aic3x: Fix class-D initialization for tlv320aic3007 (stable-fixes).\n- Bluetooth: 6lowpan: Do not hold spin lock over sleeping functions (git-fixes).\n- Bluetooth: 6lowpan: add missing l2cap_chan_lock() (git-fixes).\n- Bluetooth: 6lowpan: fix BDADDR_LE vs ADDR_LE_DEV address type confusion (git-fixes).\n- Bluetooth: 6lowpan: reset link-local header on ipv6 recv path (git-fixes).\n- Bluetooth: L2CAP: export l2cap_chan_hold for modules (stable-fixes).\n- Bluetooth: MGMT: cancel mesh send timer when hdev removed (git-fixes).\n- Bluetooth: SCO: Fix UAF on sco_conn_free (stable-fixes).\n- Bluetooth: bcsp: receive data only if registered (stable-fixes).\n- Bluetooth: btrtl: Fix memory leak in rtlbt_parse_firmware_v2() (git-fixes).\n- Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames (stable-fixes).\n- Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (git-fixes).\n- Bluetooth: hci_event: validate skb length for unknown CC opcode (git-fixes).\n- Documentation: ACPI: i2c-muxes: fix I2C device references (git-fixes).\n- Drivers: hv: vmbus: Add utility function for querying ring size (git-fixes).\n- HID: amd_sfh: Stop sensor before starting (git-fixes).\n- HID: hid-ntrig: Prevent memory leak in ntrig_report_version() (git-fixes).\n- HID: quirks: avoid Cooler Master MM712 dongle wakeup bug (stable-fixes).\n- HID: quirks: work around VID/PID conflict for 0x4c4a/0x4155 (git-fixes).\n- HID: uclogic: Fix potential memory leak in error path (git-fixes).\n- Input: atmel_mxt_ts - allow reset GPIO to sleep (stable-fixes).\n- Input: imx_sc_key - fix memory corruption on unload (git-fixes).\n- Input: pegasus-notetaker - fix potential out-of-bounds access (git-fixes).\n- KVM: Pass new routing entries and irqfd when updating IRTEs (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Emulate PERF_CNTR_GLOBAL_STATUS_SET for PerfMonV2 (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: SVM: Re-load current, not host, TSC_AUX on #VMEXIT from SEV-ES guest (git-fixes).\n- KVM: SVM: Track per-vCPU IRTEs using kvm_kernel_irqfd structure (git-fixes).\n- KVM: SVM: WARN if an invalid posted interrupt IRTE entry is added (git-fixes).\n- KVM: VMX: Allow guest to set DEBUGCTL.RTM_DEBUG if RTM is supported (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes) (git-fixes).\n- KVM: VMX: Apply MMIO Stale Data mitigation if KVM maps MMIO into the guest (git-fixes).\n- KVM: VMX: Fix check for valid GVA on an EPT violation (git-fixes).\n- KVM: VMX: Preserve host's DEBUGCTLMSR_FREEZE_IN_SMM while running the guest (git-fixes).\n- KVM: VMX: Wrap all accesses to IA32_DEBUGCTL with getter/setter APIs (git-fixes).\n- KVM: nVMX: Check vmcs12-\u003eguest_ia32_debugctl on nested VM-Enter (git-fixes).\n- KVM: x86/mmu: Locally cache whether a PFN is host MMIO when making a SPTE (git-fixes).\n- KVM: x86: Add helper to retrieve current value of user return MSR (git-fixes).\n- KVM: x86: Convert vcpu_run()'s immediate exit param into a generic bitmap (git-fixes).\n- KVM: x86: Do not treat ENTER and LEAVE as branches, because they are not (git-fixes).\n- KVM: x86: Drop kvm_x86_ops.set_dr6() in favor of a new KVM_RUN flag (git-fixes).\n- NFS4: Fix state renewals missing after boot (git-fixes).\n- NFS: check if suid/sgid was cleared after a write as needed (git-fixes).\n- NFSD: Never cache a COMPOUND when the SEQUENCE operation fails (git-fixes).\n- NFSD: Skip close replay processing if XDR encoding fails (git-fixes).\n- NFSD: free copynotify stateid in nfs4_free_ol_stateid() (git-fixes).\n- NFSv4.1: fix mount hang after CREATE_SESSION failure (git-fixes).\n- NFSv4: handle ERR_GRACE on delegation recalls (git-fixes).\n- PCI/P2PDMA: Fix incorrect pointer usage in devm_kfree() call (stable-fixes).\n- PCI/PM: Skip resuming to D0 if device is disconnected (stable-fixes).\n- PCI: Disable MSI on RDC PCI to PCIe bridges (stable-fixes).\n- PCI: cadence: Check for the existence of cdns_pcie::ops before using it (stable-fixes).\n- PCI: dwc: Verify the single eDMA IRQ in dw_pcie_edma_irq_verify() (stable-fixes).\n- PCI: j721e: Fix incorrect error message in probe() (git-fixes).\n- PCI: rcar-host: Convert struct rcar_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra194: Reset BARs when running in PCIe endpoint mode (git-fixes).\n- RDMA/bnxt_re: Do not fail destroy QP and cleanup debugfs earlier (git-fixes)\n- RDMA/bnxt_re: Fix a potential memory leak in destroy_gsi_sqp (git-fixes)\n- RDMA/hns: Fix recv CQ and QP cache affinity (git-fixes)\n- RDMA/hns: Fix the modification of max_send_sge (git-fixes)\n- RDMA/hns: Fix wrong WQE data when QP wraps around (git-fixes)\n- RDMA/irdma: Fix SD index calculation (git-fixes)\n- RDMA/irdma: Set irdma_cq cq_num field during CQ create (git-fixes)\n- accel/habanalabs/gaudi2: fix BMON disable configuration (stable-fixes).\n- accel/habanalabs/gaudi2: read preboot status after recovering from dirty state (stable-fixes).\n- accel/habanalabs: return ENOMEM if less than requested pages were pinned (stable-fixes).\n- accel/habanalabs: support mapping cb with vmalloc-backed coherent memory (stable-fixes).\n- acpi,srat: Fix incorrect device handle check for Generic Initiator (git-fixes).\n- amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw (stable-fixes).\n- block: avoid possible overflow for chunk_sectors check in blk_stack_limits() (git-fixes).\n- block: fix kobject double initialization in add_disk (git-fixes).\n- btrfs: abort transaction on failure to add link to inode (git-fixes).\n- btrfs: avoid page_lockend underflow in btrfs_punch_hole_lock_range() (git-fix).\n- btrfs: avoid using fixed char array size for tree names (git-fix).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- btrfs: fix COW handling in run_delalloc_nocow() (git-fix).\n- btrfs: fix inode leak on failure to add link to inode (git-fixes).\n- btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve (git-fix).\n- btrfs: mark dirty extent range for out of bound prealloc extents (git-fixes).\n- btrfs: qgroup: correctly model root qgroup rsv in convert (git-fix).\n- btrfs: rename err to ret in btrfs_link() (git-fixes).\n- btrfs: run btrfs_error_commit_super() early (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fix).\n- btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: send: fix duplicated rmdir operations when using extrefs (git-fixes).\n- btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name (git-fixes).\n- btrfs: simplify error handling logic for btrfs_link() (git-fixes).\n- btrfs: tree-checker: add dev extent item checks (git-fix).\n- btrfs: tree-checker: add type and sequence check for inline backrefs (git-fix).\n- btrfs: tree-checker: fix the wrong output of data backref objectid (git-fix).\n- btrfs: tree-checker: reject BTRFS_FT_UNKNOWN dir type (git-fix).\n- btrfs: tree-checker: validate dref root and objectid (git-fix).\n- btrfs: use smp_mb__after_atomic() when forcing COW in create_pending_snapshot() (git-fixes).\n- char: misc: Does not request module for miscdevice with dynamic minor (stable-fixes).\n- char: misc: Make misc_register() reentry for miscdevice who wants dynamic minor (stable-fixes).\n- char: misc: restrict the dynamic range to exclude reserved minors (stable-fixes).\n- cramfs: Verify inode mode when loading from disk (git-fixes).\n- crypto: aspeed - fix double free caused by devm (git-fixes).\n- crypto: aspeed-acry - Convert to platform remove callback returning void (stable-fixes).\n- crypto: hisilicon/qm - Fix device reference leak in qm_get_qos_value (git-fixes).\n- crypto: iaa - Do not clobber req-\u003ebase.data (git-fixes).\n- crypto: qat - use kcalloc() in qat_uclo_map_objs_from_mof() (stable-fixes).\n- dmaengine: dw-edma: Set status for callback_result (stable-fixes).\n- dmaengine: mv_xor: match alloc_wc and free_wc (stable-fixes).\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: Disable VRR on DCE 6 (stable-fixes).\n- drm/amd/display: Fix DVI-D/HDMI adapters (stable-fixes).\n- drm/amd/display: Fix NULL deref in debugfs odm_combine_segments (git-fixes).\n- drm/amd/display: Fix black screen with HDMI outputs (git-fixes).\n- drm/amd/display: Increase AUX Intra-Hop Done Max Wait Duration (stable-fixes).\n- drm/amd/display: add more cyan skillfish devices (stable-fixes).\n- drm/amd/display: ensure committing streams is seamless (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/amd/pm: Disable MCLK switching on SI at high pixel clocks (stable-fixes).\n- drm/amd/pm: Use cached metrics data on aldebaran (stable-fixes).\n- drm/amd/pm: Use cached metrics data on arcturus (stable-fixes).\n- drm/amd: Avoid evicting resources at S5 (stable-fixes).\n- drm/amd: Fix suspend failure with secure display TA (git-fixes).\n- drm/amd: add more cyan skillfish PCI ids (stable-fixes).\n- drm/amdgpu/jpeg: Hold pg_lock before jpeg poweroff (stable-fixes).\n- drm/amdgpu: Allow kfd CRIU with no buffer objects (stable-fixes).\n- drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices (stable-fixes).\n- drm/amdgpu: Use memdup_array_user in amdgpu_cs_wait_fences_ioctl (stable-fixes).\n- drm/amdgpu: add support for cyan skillfish gpu_info (stable-fixes).\n- drm/amdgpu: do not enable SMU on cyan skillfish (stable-fixes).\n- drm/amdgpu: reject gang submissions under SRIOV (stable-fixes).\n- drm/amdkfd: Handle lack of READ permissions in SVM mapping (stable-fixes).\n- drm/amdkfd: Tie UNMAP_LATENCY to queue_preemption (stable-fixes).\n- drm/amdkfd: fix vram allocation failure for a special case (stable-fixes).\n- drm/amdkfd: return -ENOTTY for unsupported IOCTLs (stable-fixes).\n- drm/bridge: cdns-dsi: Do not fail on MIPI_DSI_MODE_VIDEO_BURST (stable-fixes).\n- drm/bridge: cdns-dsi: Fix REG_WAKEUP_TIME value (stable-fixes).\n- drm/bridge: display-connector: do not set OP_DETECT for DisplayPorts (stable-fixes).\n- drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD (git-fixes).\n- drm/i915: Fix conversion between clock ticks and nanoseconds (git-fixes).\n- drm/msm/dsi/phy: Toggle back buffer resync after preparing PLL (stable-fixes).\n- drm/msm/dsi/phy_7nm: Fix missing initial VCO rate (stable-fixes).\n- drm/msm: make sure to not queue up recovery more than once (stable-fixes).\n- drm/nouveau: replace snprintf() with scnprintf() in nvkm_snprintbf() (stable-fixes).\n- drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb (git-fixes).\n- drm/tegra: Add call to put_pid() (git-fixes).\n- drm/tegra: dc: Fix reference leak in tegra_dc_couple() (git-fixes).\n- drm/tidss: Set crtc modesetting parameters with adjusted mode (stable-fixes).\n- drm/tidss: Use the crtc_* timings when programming the HW (stable-fixes).\n- drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (git-fixes).\n- exfat: limit log print for IO error (git-fixes).\n- extcon: adc-jack: Cleanup wakeup source only if it was enabled (git-fixes).\n- extcon: adc-jack: Fix wakeup source leaks on device unbind (stable-fixes).\n- fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (stable-fixes).\n- fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (stable-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_putcs* (stable-fixes).\n- fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS (stable-fixes).\n- hwmon: (asus-ec-sensors) increase timeout for locking ACPI mutex (stable-fixes).\n- hwmon: (dell-smm) Add support for Dell OptiPlex 7040 (stable-fixes).\n- hwmon: (k10temp) Add device ID for Strix Halo (stable-fixes).\n- hwmon: (k10temp) Add thermal support for AMD Family 1Ah-based models (stable-fixes).\n- hwmon: (sbtsi_temp) AMD CPU extended temperature range support (stable-fixes).\n- hwmon: sy7636a: add alias (stable-fixes).\n- iio: adc: imx93_adc: load calibrated values even calibration failed (stable-fixes).\n- iio: adc: spear_adc: mask SPEAR_ADC_STATUS channel and avg sample before setting register (stable-fixes).\n- ima: do not clear IMA_DIGSIG flag when setting or removing non-IMA xattr (stable-fixes).\n- iommu/amd: Return an error if vCPU affinity is set for non-vCPU IRTE (git-fixes).\n- isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() (git-fixes).\n- jfs: Verify inode mode when loading from disk (git-fixes).\n- jfs: fix uninitialized waitqueue in transaction manager (git-fixes).\n- lib/crypto: curve25519-hacl64: Fix older clang KASAN workaround for GCC (git-fixes).\n- md/raid1: fix data lost for writemostly rdev (git-fixes).\n- md: fix mssing blktrace bio split events (git-fixes).\n- media: adv7180: Add missing lock in suspend callback (stable-fixes).\n- media: adv7180: Do not write format to device in set_fmt (stable-fixes).\n- media: adv7180: Only validate format in querystd (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- media: fix uninitialized symbol warnings (stable-fixes).\n- media: i2c: Kconfig: Ensure a dependency on HAVE_CLK for VIDEO_CAMERA_SENSOR (stable-fixes).\n- media: i2c: og01a1b: Specify monochrome media bus format instead of Bayer (stable-fixes).\n- media: imon: make send_packet() more robust (stable-fixes).\n- media: ov08x40: Fix the horizontal flip control (stable-fixes).\n- media: redrat3: use int type to store negative error codes (stable-fixes).\n- media: uvcvideo: Use heuristic to find stream entity (git-fixes).\n- memstick: Add timeout to prevent indefinite waiting (stable-fixes).\n- mfd: da9063: Split chip variant reading in two bus transactions (stable-fixes).\n- mfd: madera: Work around false-positive -Wininitialized warning (stable-fixes).\n- mfd: stmpe-i2c: Add missing MODULE_LICENSE (stable-fixes).\n- mfd: stmpe: Remove IRQ domain upon removal (stable-fixes).\n- minixfs: Verify inode mode when loading from disk (git-fixes).\n- mm/mm_init: fix hash table order logging in alloc_large_system_hash() (git-fixes).\n- mm/secretmem: fix use-after-free race in fault handler (git-fixes).\n- mmc: host: renesas_sdhi: Fix the actual clock (stable-fixes).\n- mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Change DLL_STRBIN_TAPNUM_DEFAULT to 0x4 (git-fixes).\n- mtd: onenand: Pass correct pointer to IRQ handler (git-fixes).\n- mtd: rawnand: cadence: fix DMA device NULL pointer dereference (git-fixes).\n- mtdchar: fix integer overflow in read/write ioctls (git-fixes).\n- net/mana: fix warning in the writer of client oob (git-fixes).\n- net/smc: Remove validation of reserved bits in CLC Decline message (bsc#1253779).\n- net: nfc: nci: Increase NCI_DATA_TIMEOUT to 3000 ms (stable-fixes).\n- net: phy: clear link parameters on admin link down (stable-fixes).\n- net: phy: fixed_phy: let fixed_phy_unregister free the phy_device (stable-fixes).\n- net: phy: marvell: Fix 88e1510 downshift counter errata (stable-fixes).\n- net: tcp: send zero-window ACK when no memory (bsc#1253779).\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (git-fixes).\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing (git-fixes).\n- nfsd: do not defer requests during idmap lookup in v4 compound decode (bsc#1232223).\n- nfsd: fix return error codes for nfsd_map_name_to_id (bsc#1232223).\n- nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot (git-fixes).\n- perf script: add --addr2line option (bsc#1247509).\n- phy: cadence: cdns-dphy: Enable lower resolutions in dphy (stable-fixes).\n- phy: renesas: r8a779f0-ether-serdes: add new step added to latest datasheet (stable-fixes).\n- phy: rockchip: phy-rockchip-inno-csidphy: allow writes to grf register 0 (stable-fixes).\n- pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc (git-fixes).\n- pinctrl: s32cc: initialize gpio_pin_config::list after kmalloc() (git-fixes).\n- pinctrl: single: fix bias pull up/down handling in pin_config_set (stable-fixes).\n- platform/x86/intel/speed_select_if: Convert PCIBIOS_* return codes to errnos (git-fixes).\n- power: supply: qcom_battmgr: add OOI chemistry (stable-fixes).\n- power: supply: qcom_battmgr: handle charging state change notifications (stable-fixes).\n- power: supply: sbs-charger: Support multiple devices (stable-fixes).\n- regulator: fixed: fix GPIO descriptor leak on register failure (git-fixes).\n- rtc: rx8025: fix incorrect register reference (git-fixes).\n- s390/mm,fault: simplify kfence fault handling (bsc#1247076).\n- scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans (git-fixes).\n- scsi: aacraid: Stop using PCI_IRQ_AFFINITY (git-fixes).\n- scsi: core: sysfs: Correct sysfs attributes access rights (git-fixes).\n- scsi: hpsa: Fix potential memory leak in hpsa_big_passthru_ioctl() (git-fixes).\n- scsi: libfc: Prevent integer overflow in fc_fcp_recv_data() (git-fixes).\n- scsi: mpi3mr: Correctly handle ATA device errors (git-fixes).\n- scsi: mpi3mr: Drop unnecessary volatile from __iomem pointers (git-fixes).\n- scsi: mpt3sas: Correctly handle ATA device errors (git-fixes).\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (git-fixes).\n- scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod (git-fixes).\n- scsi: storvsc: Prefer returning channel with the same CPU as on the I/O issuing CPU (bsc#1252267).\n- selftests/bpf: Close fd in error path in drop_on_reuseport (git-fixes).\n- selftests/bpf: Close obj in error path in xdp_adjust_tail (git-fixes).\n- selftests/bpf: Fix missing ARRAY_SIZE() definition in bench.c (git-fixes).\n- selftests/bpf: Fix missing BUILD_BUG_ON() declaration (git-fixes).\n- selftests/bpf: Fix missing UINT_MAX definitions in benchmarks (git-fixes).\n- selftests/bpf: Fix string read in strncmp benchmark (git-fixes).\n- selftests/bpf: Mitigate sockmap_ktls disconnect_after_delete failure (git-fixes).\n- selftests/bpf: Use pid_t consistently in test_progs.c (git-fixes).\n- selftests/bpf: fix signedness bug in redir_partial() (git-fixes).\n- serial: 8250_exar: add support for Advantech 2 port card with Device ID 0x0018 (git-fixes).\n- serial: 8250_mtk: Enable baud clock and manage in runtime PM (git-fixes).\n- soc/tegra: fuse: Add Tegra114 nvmem cells and fuse lookups (stable-fixes).\n- soc: aspeed: socinfo: Add AST27xx silicon IDs (stable-fixes).\n- soc: qcom: smem: Fix endian-unaware access of num_entries (stable-fixes).\n- spi: Try to get ACPI GPIO IRQ earlier (git-fixes).\n- spi: loopback-test: Do not use %pK through printk (stable-fixes).\n- spi: rpc-if: Add resume support for RZ/G3E (stable-fixes).\n- strparser: Fix signed/unsigned mismatch bug (git-fixes).\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- thunderbolt: Use is_pciehp instead of is_hotplug_bridge (stable-fixes).\n- tools/cpupower: Fix incorrect size in cpuidle_state_disable() (stable-fixes).\n- tools/cpupower: fix error return value in cpupower_write_sysfs() (stable-fixes).\n- tools/power x86_energy_perf_policy: Enhance HWP enable (stable-fixes).\n- tools/power x86_energy_perf_policy: Fix incorrect fopen mode usage (stable-fixes).\n- tools/power x86_energy_perf_policy: Prefer driver HWP limits (stable-fixes).\n- tools: lib: thermal: do not preserve owner in install (stable-fixes).\n- tools: lib: thermal: use pkg-config to locate libnl3 (stable-fixes).\n- uio_hv_generic: Query the ringbuffer size for device (git-fixes).\n- usb/core/quirks: Add Huawei ME906S to wakeup quirk (git-fixes).\n- usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget (stable-fixes).\n- usb: gadget: f_fs: Fix epfile null pointer access after ep enable (stable-fixes).\n- usb: gadget: f_hid: Fix zero length packet transfer (stable-fixes).\n- usb: gadget: f_ncm: Fix MAC assignment NCM ethernet (stable-fixes).\n- usb: mon: Increase BUFF_MAX to 64 MiB to support multi-MB URBs (stable-fixes).\n- usb: xhci: plat: Facilitate using autosuspend for xhci plat devices (stable-fixes).\n- video: backlight: lp855x_bl: Set correct EPROM start for LP8556 (stable-fixes).\n- watchdog: s3c2410_wdt: Fix max_timeout being calculated larger (stable-fixes).\n- wifi: ath10k: Fix connection after GTK rekeying (stable-fixes).\n- wifi: ath11k: zero init info-\u003estatus in wmi_process_mgmt_tx_comp() (git-fixes).\n- wifi: ath12k: Increase DP_REO_CMD_RING_SIZE to 256 (stable-fixes).\n- wifi: mac80211: Fix HE capabilities element check (stable-fixes).\n- wifi: mac80211: reject address change while connecting (git-fixes).\n- wifi: mac80211: skip rate verification for not captured PSDUs (git-fixes).\n- wifi: mac80211_hwsim: Limit destroy_on_close radio removal to netgroup (git-fixes).\n- wifi: mt76: mt7921: Add 160MHz beamformee capability for mt7922 device (stable-fixes).\n- wifi: mt76: mt7996: Temporarily disable EPCS (stable-fixes).\n- wifi: mwl8k: inject DSSS Parameter Set element into beacons if missing (git-fixes).\n- wifi: rtw88: sdio: use indirect IO for device registers before power-on (stable-fixes).\n- wifi: zd1211rw: fix potential memory leak in __zd_usb_enable_rx() (git-fixes).\n- x86/CPU/AMD: Add RDSEED fix for Zen5 (git-fixes).\n- x86/CPU/AMD: Add additional fixed RDSEED microcode revisions (git-fixes).\n- x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode (git-fixes).\n- x86/CPU/AMD: Do the common init on future Zens too (git-fixes).\n- x86/amd_nb: Add new PCI IDs for AMD family 0x1a (stable-fixes).\n- x86/bugs: Fix reporting of LFENCE retpoline (git-fixes).\n- x86/bugs: Report correct retbleed mitigation status (git-fixes).\n- x86/vmscape: Add old Intel CPUs to affected list (git-fixes).\n- xhci: dbc: Allow users to modify DbC poll interval via sysfs (stable-fixes).\n- xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive (git-fixes).\n- xhci: dbc: Improve performance by removing delay in transfer event polling (stable-fixes).\n- xhci: dbc: fix bogus 1024 byte prefix if ttyDBC read races with stall event (git-fixes).\n- xhci: dbc: poll at different rate depending on data transfer activity (stable-fixes).\n","status":"published","published":"2026-02-19T15:57:41Z","modified":"2026-03-23T04:52:59.914226Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20562-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50253: bpf: make sure skb-\u003elen != 0 when redirecting to a tunneling device (bsc#1249912).\n- CVE-2025-37916: pds_core: remove write-after-free of client_id (bsc#1243474).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245431 bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39805: net: macb: fix unregister_netdev call order in macb_remove() (bsc#1249982).\n- CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).\n- CVE-2025-39822: io_uring/kbuf: fix signedness in this_len calculation (bsc#1250034).\n- CVE-2025-39831: fbnic: Move phylink resume out of service_task and into open/close (bsc#1249977).\n- CVE-2025-39859: ptp: ocp: fix use-after-free bugs causing by ptp_ocp_watchdog (bsc#1250252).\n- CVE-2025-39897: net: xilinx: axienet: Add error handling for RX metadata pointer retrieval (bsc#1250746).\n- CVE-2025-39917: bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt (bsc#1250723).\n- CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() (bsc#1251120).\n- CVE-2025-39961: iommu/amd/pgtbl: Fix possible race while increase page table level (bsc#1251817).\n- CVE-2025-39980: nexthop: Forbid FDB status change while nexthop is in a group (bsc#1252063).\n- CVE-2025-39990: bpf: Check the helper function is valid in get_helper_proto (bsc#1252054).\n- CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).\n- CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work (bsc#1252301).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40021: tracing: dynevent: Add a missing lockdown check on dynevent (bsc#1252681).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).\n- CVE-2025-40031: tee: fix register_shm_helper() (bsc#1252779).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40038: KVM: SVM: Skip fastpath emulation on VM-Exit if next RIP isn't valid (bsc#1252817).\n- CVE-2025-40047: io_uring/waitid: always prune wait queue entry in io_waitid_wait() (bsc#1252790).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).\n- CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc (bsc#1252809).\n- CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).\n- CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).\n- CVE-2025-40074: tcp: convert to dev_net_rcu() (bsc#1252794).\n- CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).\n- CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds (bsc#1252923).\n- CVE-2025-40098: ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_get_acpi_mute_state() (bsc#1252917).\n- CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (bsc#1252901).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40105: vfs: Don't leak disconnected dentries on umount (bsc#1252928).\n- CVE-2025-40133: mptcp: Call dst_release() in mptcp_active_enable() (bsc#1253328).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).\n- CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40157: EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (bsc#1253423).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40159: xsk: Harden userspace-supplied xdp_desc validation (bsc#1253403).\n- CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).\n- CVE-2025-40169: bpf: Reject negative offsets for ALU ops (bsc#1253416).\n- CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).\n- CVE-2025-40175: idpf: cleanup remaining SKBs in PTP flows (bsc#1253426).\n- CVE-2025-40176: tls: wait for pending async decryptions if tls_strp_msg_hold fails (bsc#1253425).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40185: ice: ice_adapter: release xa entry on adapter allocation failure (bsc#1253394).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40203: listmount: don't call path_put() under namespace semaphore (bsc#1253457).\n\nThe following non security issues were fixed:\n\n- ACPI: scan: Update honor list for RPMI System MSI (stable-fixes).\n- ACPICA: Update dsmethod.c to get rid of unused variable warning (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Fix \"drm/xe: Don't allow evicting of BOs in same VM in array of VM binds\" (bsc#1252923)\n- KVM: SVM: Delete IRTE link from previous vCPU before setting new IRTE (git-fixes).\n- KVM: SVM: Delete IRTE link from previous vCPU irrespective of new routing (git-fixes).\n- KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated (git-fixes).\n- KVM: s390: improve interrupt cpu for wakeup (bsc#1235463).\n- KVM: s390: kABI backport for 'last_sleep_cpu' (bsc#1252352).\n- KVM: x86/mmu: Return -EAGAIN if userspace deletes/moves memslot during prefault (git-fixes).\n- PCI/ERR: Update device error_state already after reset (stable-fixes).\n- PM: EM: Slightly reduce em_check_capacity_update() overhead (stable-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon MTU set\" (git-fixes).\n- Revert \"net/mlx5e: Update and set Xon/Xoff upon port speed set\" (git-fixes).\n- Update config files: enable zstd module decompression (jsc#PED-14115).\n- bpf/selftests: Fix test_tcpnotify_user (bsc#1253635).\n- btrfs: do not clear read-only when adding sprout device (bsc#1253238).\n- btrfs: do not update last_log_commit when logging inode due to a new name (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amd/display: Add AVI infoframe copy in copy_stream_update_to_stream (stable-fixes).\n- drm/amd/display: update color on atomic commit time (stable-fixes).\n- drm/amd/display: update dpp/disp clock from smu clock table (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- hwmon: (lenovo-ec-sensors) Update P8 supprt (stable-fixes).\n- media: amphion: Delete v4l2_fh synchronously in .release() (stable-fixes).\n- mount: handle NULL values in mnt_ns_release() (bsc#1254308)\n- net/smc: Remove validation of reserved bits in CLC Decline (bsc#1252357).\n- net: phy: move realtek PHY driver to its own subdirectory (jsc#PED-14353).\n- net: phy: realtek: add defines for shadowed c45 standard registers (jsc#PED-14353).\n- net: phy: realtek: add helper RTL822X_VND2_C22_REG (jsc#PED-14353).\n- net: phy: realtek: change order of calls in C22 read_status() (jsc#PED-14353).\n- net: phy: realtek: clear 1000Base-T link partner advertisement (jsc#PED-14353).\n- net: phy: realtek: improve mmd register access for internal PHY's (jsc#PED-14353).\n- net: phy: realtek: read duplex and gbit master from PHYSR register (jsc#PED-14353).\n- net: phy: realtek: switch from paged to MMD ops in rtl822x functions (jsc#PED-14353).\n- net: phy: realtek: use string choices helpers (jsc#PED-14353).\n- net: xilinx: axienet: Fix IRQ coalescing packet count overflow (bsc#1250746)\n- net: xilinx: axienet: Fix RX skb ring management in DMAengine mode (bsc#1250746)\n- net: xilinx: axienet: Fix Tx skb circular buffer occupancy check in dmaengine xmit (bsc#1250746)\n- nvmet-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- perf list: Add IBM z17 event descriptions (jsc#PED-13611).\n- platform/x86:intel/pmc: Update Arrow Lake telemetry GUID (git-fixes).\n- powercap: intel_rapl: Add support for Panther Lake platform (jsc#PED-13949).\n- pwm: pca9685: Use bulk write to atomicially update registers (stable-fixes).\n- r8169: add PHY c45 ops for MDIO_MMD_VENDOR2 registers (jsc#PED-14353).\n- r8169: add support for Intel Killer E5000 (jsc#PED-14353).\n- r8169: add support for RTL8125BP rev.b (jsc#PED-14353).\n- r8169: add support for RTL8125D rev.b (jsc#PED-14353).\n- r8169: adjust version numbering for RTL8126 (jsc#PED-14353).\n- r8169: align RTL8125 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8125/RTL8126 PHY config with vendor driver (jsc#PED-14353).\n- r8169: align RTL8126 EEE config with vendor driver (jsc#PED-14353).\n- r8169: align WAKE_PHY handling with r8125/r8126 vendor drivers (jsc#PED-14353).\n- r8169: avoid duplicated messages if loading firmware fails and switch to warn level (jsc#PED-14353).\n- r8169: don't take RTNL lock in rtl_task() (jsc#PED-14353).\n- r8169: enable EEE at 2.5G per default on RTL8125B (jsc#PED-14353).\n- r8169: enable RTL8168H/RTL8168EP/RTL8168FP ASPM support (jsc#PED-14353).\n- r8169: fix inconsistent indenting in rtl8169_get_eth_mac_stats (jsc#PED-14353).\n- r8169: implement additional ethtool stats ops (jsc#PED-14353).\n- r8169: improve __rtl8169_set_wol (jsc#PED-14353).\n- r8169: improve initialization of RSS registers on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: improve rtl_set_d3_pll_down (jsc#PED-14353).\n- r8169: increase max jumbo packet size on RTL8125/RTL8126 (jsc#PED-14353).\n- r8169: remove leftover locks after reverted change (jsc#PED-14353).\n- r8169: remove original workaround for RTL8125 broken rx issue (jsc#PED-14353).\n- r8169: remove rtl_dash_loop_wait_high/low (jsc#PED-14353).\n- r8169: remove support for chip version 11 (jsc#PED-14353).\n- r8169: remove unused flag RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE (jsc#PED-14353).\n- r8169: replace custom flag with disable_work() et al (jsc#PED-14353).\n- r8169: switch away from deprecated pcim_iomap_table (jsc#PED-14353).\n- r8169: use helper r8169_mod_reg8_cond to simplify rtl_jumbo_config (jsc#PED-14353).\n- ring-buffer: Update pages_touched to reflect persistent buffer content (git-fixes).\n- s390/mm: Fix __ptep_rdp() inline assembly (bsc#1253643).\n- sched/fair: Get rid of sched_domains_curr_level hack for tl-\u003ecpumask() (bsc#1246843).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1248792).\n- sched/fair: Proportional newidle balance (bsc#1248792).\n- sched/fair: Proportional newidle balance -KABI (bsc#1248792).\n- sched/fair: Revert max_newidle_lb_cost bump (bsc#1248792).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1248792).\n- sched/fair: Small cleanup to sched_balance_newidle() (bsc#1248792).\n- sched/fair: Small cleanup to update_newidle_cost() (bsc#1248792).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- selftests/run_kselftest.sh: Add `--skip` argument option (bsc#1254221).\n- smpboot: introduce SDTL_INIT() helper to tidy sched topology setup (bsc#1246843).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock-\u003ecork (bsc#1250705).\n- wifi: ath11k: Add quirk entries for Thinkpad T14s Gen3 AMD (bsc#1254181).\n- wifi: mt76: do not add wcid entries to sta poll list during MCU reset (bsc#1254315).\n- wifi: mt76: introduce mt792x_config_mac_addr_list routine (bsc#1254315).\n- wifi: mt76: mt7925: Fix logical vs bitwise typo (bsc#1254315).\n- wifi: mt76: mt7925: Remove unnecessary if-check (bsc#1254315).\n- wifi: mt76: mt7925: Simplify HIF suspend handling to avoid suspend fail (bsc#1254315).\n- wifi: mt76: mt7925: add EHT control support based on the CLC data (bsc#1254315).\n- wifi: mt76: mt7925: add handler to hif suspend/resume event (bsc#1254315).\n- wifi: mt76: mt7925: add pci restore for hibernate (bsc#1254315).\n- wifi: mt76: mt7925: config the dwell time by firmware (bsc#1254315).\n- wifi: mt76: mt7925: extend MCU support for testmode (bsc#1254315).\n- wifi: mt76: mt7925: fix CLC command timeout when suspend/resume (bsc#1254315).\n- wifi: mt76: mt7925: fix missing hdr_trans_tlv command for broadcast wtbl (bsc#1254315).\n- wifi: mt76: mt7925: fix the unfinished command of regd_notifier before suspend (bsc#1254315).\n- wifi: mt76: mt7925: refine the txpower initialization flow (bsc#1254315).\n- wifi: mt76: mt7925: replace zero-length array with flexible-array member (bsc#1254315).\n- wifi: mt76: mt7925: update the channel usage when the regd domain changed (bsc#1254315).\n- wifi: mt76: mt7925e: fix too long of wifi resume time (bsc#1254315).\n- x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled (bsc#1246843).\n- x86/smpboot: moves x86_topology to static initialize and truncate (bsc#1246843).\n- x86/smpboot: remove redundant CONFIG_SCHED_SMT (bsc#1246843).\n","status":"published","published":"2025-12-19T15:33:12Z","modified":"2026-07-09T18:24:04.276994383Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"USN-8029-1","title":"linux, linux-raspi, linux-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Drivers core;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - CXL (Compute Express Link) drivers;\n - Device frequency scaling framework;\n - ARM SCMI message protocol;\n - GPIO subsystem;\n - GPU drivers;\n - Hardware monitoring drivers;\n - HW tracing;\n - InfiniBand drivers;\n - Input Device (Miscellaneous) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - PCI Endpoint Test driver;\n - VMware Balloon Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - NVME drivers;\n - PCI subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Mellanox platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - SCSI subsystem;\n - SPI subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - vDPA drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EROFS file system;\n - Ext4 file system;\n - F2FS file system;\n - GFS2 file system;\n - JFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - BPF subsystem;\n - Mellanox drivers;\n - Memory management;\n - Virtio network driver;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - io_uring subsystem;\n - Kernel crash support code;\n - Perf events;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Ethernet bridge;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Network traffic control;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - HD-audio driver;\n - AMD SoC Alsa drivers;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-12T09:15:01Z","modified":"2026-11-03T14:34:42.37518646Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8029-2","title":"linux-aws, linux-oracle vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Drivers core;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - CXL (Compute Express Link) drivers;\n - Device frequency scaling framework;\n - ARM SCMI message protocol;\n - GPIO subsystem;\n - GPU drivers;\n - Hardware monitoring drivers;\n - HW tracing;\n - InfiniBand drivers;\n - Input Device (Miscellaneous) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - PCI Endpoint Test driver;\n - VMware Balloon Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - NVME drivers;\n - PCI subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Mellanox platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - SCSI subsystem;\n - SPI subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - vDPA drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EROFS file system;\n - Ext4 file system;\n - F2FS file system;\n - GFS2 file system;\n - JFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - BPF subsystem;\n - Mellanox drivers;\n - Memory management;\n - Virtio network driver;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - io_uring subsystem;\n - Kernel crash support code;\n - Perf events;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Ethernet bridge;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Network traffic control;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - HD-audio driver;\n - AMD SoC Alsa drivers;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-17T12:49:18Z","modified":"2026-11-03T14:35:03.428875576Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8029-3","title":"linux-azure vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Drivers core;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - CXL (Compute Express Link) drivers;\n - Device frequency scaling framework;\n - ARM SCMI message protocol;\n - GPIO subsystem;\n - GPU drivers;\n - Hardware monitoring drivers;\n - HW tracing;\n - InfiniBand drivers;\n - Input Device (Miscellaneous) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - PCI Endpoint Test driver;\n - VMware Balloon Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - NVME drivers;\n - PCI subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Mellanox platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - SCSI subsystem;\n - SPI subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - vDPA drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EROFS file system;\n - Ext4 file system;\n - F2FS file system;\n - GFS2 file system;\n - JFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - BPF subsystem;\n - Mellanox drivers;\n - Memory management;\n - Virtio network driver;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - io_uring subsystem;\n - Kernel crash support code;\n - Perf events;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Ethernet bridge;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Network traffic control;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - HD-audio driver;\n - AMD SoC Alsa drivers;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-24T11:20:31Z","modified":"2026-11-03T14:35:00.15213949Z","updated_at":"2026-11-03T15:16:40.267874Z"},{"id":"USN-8030-1","title":"linux-gcp vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Drivers core;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - CXL (Compute Express Link) drivers;\n - Device frequency scaling framework;\n - ARM SCMI message protocol;\n - GPIO subsystem;\n - GPU drivers;\n - Hardware monitoring drivers;\n - HW tracing;\n - InfiniBand drivers;\n - Input Device (Miscellaneous) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - PCI Endpoint Test driver;\n - VMware Balloon Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - NVME drivers;\n - PCI subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Mellanox platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - SCSI subsystem;\n - SPI subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - vDPA drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EROFS file system;\n - Ext4 file system;\n - F2FS file system;\n - GFS2 file system;\n - JFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - BPF subsystem;\n - Mellanox drivers;\n - Memory management;\n - Virtio network driver;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - io_uring subsystem;\n - Kernel crash support code;\n - Perf events;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Ethernet bridge;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Network traffic control;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - HD-audio driver;\n - AMD SoC Alsa drivers;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,\nCVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40189, CVE-2025-40191, CVE-2025-40192, CVE-2025-40193,\nCVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,\nCVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40222,\nCVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,\nCVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40234, CVE-2025-40235,\nCVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,\nCVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40256, CVE-2025-40267,\nCVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275,\nCVE-2025-40276, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,\nCVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,\nCVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,\nCVE-2025-40288, CVE-2025-40289, CVE-2025-40291, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,\nCVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301,\nCVE-2025-40302, CVE-2025-40303, CVE-2025-40304, CVE-2025-40305,\nCVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,\nCVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313,\nCVE-2025-40314, CVE-2025-40315, CVE-2025-40316, CVE-2025-40317,\nCVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326,\nCVE-2025-40327, CVE-2025-40328, CVE-2025-40329, CVE-2025-40330,\nCVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,\nCVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338,\nCVE-2025-40339, CVE-2025-40340, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352,\nCVE-2025-40353, CVE-2025-40354, CVE-2025-40355, CVE-2025-40356,\nCVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,\nCVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168,\nCVE-2025-68169, CVE-2025-68170, CVE-2025-68171, CVE-2025-68172,\nCVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68181, CVE-2025-68182, CVE-2025-68183, CVE-2025-68184,\nCVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,\nCVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192,\nCVE-2025-68193, CVE-2025-68194, CVE-2025-68196, CVE-2025-68197,\nCVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,\nCVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206,\nCVE-2025-68207, CVE-2025-68208, CVE-2025-68209, CVE-2025-68210,\nCVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,\nCVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68246, CVE-2025-68247, CVE-2025-68248, CVE-2025-68249,\nCVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,\nCVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313,\nCVE-2025-68314, CVE-2025-68315, CVE-2025-68316, CVE-2025-68317,\nCVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-12T09:39:54Z","modified":"2026-11-03T14:34:59.664448895Z","updated_at":"2026-11-03T15:16:40.267874Z"},{"id":"USN-8048-1","title":"linux-oem-6.17 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Drivers core;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - CXL (Compute Express Link) drivers;\n - Device frequency scaling framework;\n - ARM SCMI message protocol;\n - GPIO subsystem;\n - GPU drivers;\n - Hardware monitoring drivers;\n - HW tracing;\n - InfiniBand drivers;\n - Input Device (Miscellaneous) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - PCI Endpoint Test driver;\n - VMware Balloon Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - NVME drivers;\n - PCI subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Mellanox platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - SCSI subsystem;\n - SPI subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - vDPA drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EROFS file system;\n - Ext4 file system;\n - F2FS file system;\n - GFS2 file system;\n - JFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - BPF subsystem;\n - Mellanox drivers;\n - Memory management;\n - Virtio network driver;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - io_uring subsystem;\n - Kernel crash support code;\n - Perf events;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Ethernet bridge;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Network traffic control;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - HD-audio driver;\n - AMD SoC Alsa drivers;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40041, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40045, CVE-2025-40046, CVE-2025-40047, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40054, CVE-2025-40055, CVE-2025-40056,\nCVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,\nCVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064,\nCVE-2025-40065, CVE-2025-40066, CVE-2025-40067, CVE-2025-40068,\nCVE-2025-40069, CVE-2025-40070, CVE-2025-40071, CVE-2025-40072,\nCVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076,\nCVE-2025-40077, CVE-2025-40078, CVE-2025-40079, CVE-2025-40080,\nCVE-2025-40081, CVE-2025-40082, CVE-2025-40084, CVE-2025-40085,\nCVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089,\nCVE-2025-40091, CVE-2025-40092, CVE-2025-40093, CVE-2025-40094,\nCVE-2025-40095, CVE-2025-40096, CVE-2025-40097, CVE-2025-40098,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102,\nCVE-2025-40103, CVE-2025-40104, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40113,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118,\nCVE-2025-40119, CVE-2025-40120, CVE-2025-40121, CVE-2025-40122,\nCVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131,\nCVE-2025-40132, CVE-2025-40133, CVE-2025-40134, CVE-2025-40135,\nCVE-2025-40136, CVE-2025-40137, CVE-2025-40138, CVE-2025-40139,\nCVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143,\nCVE-2025-40145, CVE-2025-40146, CVE-2025-40147, CVE-2025-40148,\nCVE-2025-40149, CVE-2025-40150, CVE-2025-40151, CVE-2025-40152,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156,\nCVE-2025-40158, CVE-2025-40159, CVE-2025-40160, CVE-2025-40161,\nCVE-2025-40162, CVE-2025-40163, CVE-2025-40164, CVE-2025-40165,\nCVE-2025-40166, CVE-2025-40167, CVE-2025-40168, CVE-2025-40169,\nCVE-2025-40170, CVE-2025-40171, CVE-2025-40173, CVE-2025-40174,\nCVE-2025-40175, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68317,\nCVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-17T15:24:04Z","modified":"2026-11-03T14:35:01.29943175Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8095-1","title":"linux, linux-aws, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-hwe-6.8, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-16T14:03:41Z","modified":"2026-11-03T14:38:36.494075469Z","updated_at":"2026-11-03T15:14:17.286738Z"},{"id":"USN-8095-2","title":"linux-fips, linux-aws-fips, linux-gcp-fips vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-16T23:02:27Z","modified":"2026-11-03T14:35:38.945380735Z","updated_at":"2026-11-03T15:16:05.953168Z"},{"id":"USN-8095-3","title":"linux-realtime, linux-realtime-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-17T18:06:26Z","modified":"2026-11-03T14:34:41.040000385Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8095-4","title":"linux-aws-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-23T14:01:42Z","modified":"2026-11-03T14:35:07.834088684Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8095-5","title":"linux-raspi, linux-raspi-realtime vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-04-01T18:04:35Z","modified":"2026-11-03T14:35:15.998762447Z","updated_at":"2026-11-03T15:16:22.507285Z"},{"id":"USN-8100-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - SPI subsystem;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734, CVE-2026-23202,\nCVE-2026-23207)\n","status":"published","published":"2026-03-16T20:48:11Z","modified":"2026-11-04T20:01:36.961728599Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8125-1","title":"linux-azure vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22037, CVE-2025-22103, CVE-2025-22105,\nCVE-2025-22106, CVE-2025-22107, CVE-2025-22113, CVE-2025-22121,\nCVE-2025-22124, CVE-2025-22125, CVE-2025-23129, CVE-2025-23130,\nCVE-2025-23133, CVE-2025-23143, CVE-2025-37860, CVE-2025-37899,\nCVE-2025-38105, CVE-2025-38502, CVE-2025-38556, CVE-2025-38627,\nCVE-2025-38643, CVE-2025-38709, CVE-2025-39678, CVE-2025-39697,\nCVE-2025-39805, CVE-2025-39806, CVE-2025-39807, CVE-2025-39808,\nCVE-2025-39810, CVE-2025-39811, CVE-2025-39812, CVE-2025-39813,\nCVE-2025-39815, CVE-2025-39817, CVE-2025-39819, CVE-2025-39823,\nCVE-2025-39824, CVE-2025-39825, CVE-2025-39826, CVE-2025-39827,\nCVE-2025-39828, CVE-2025-39829, CVE-2025-39832, CVE-2025-39835,\nCVE-2025-39836, CVE-2025-39838, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39842, CVE-2025-39843, CVE-2025-39844, CVE-2025-39845,\nCVE-2025-39846, CVE-2025-39847, CVE-2025-39848, CVE-2025-39849,\nCVE-2025-39850, CVE-2025-39851, CVE-2025-39852, CVE-2025-39853,\nCVE-2025-39854, CVE-2025-39857, CVE-2025-39860, CVE-2025-39861,\nCVE-2025-39863, CVE-2025-39864, CVE-2025-39865, CVE-2025-39866,\nCVE-2025-39869, CVE-2025-39870, CVE-2025-39871, CVE-2025-39873,\nCVE-2025-39876, CVE-2025-39877, CVE-2025-39880, CVE-2025-39881,\nCVE-2025-39883, CVE-2025-39885, CVE-2025-39886, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39895, CVE-2025-39897, CVE-2025-39899,\nCVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39914, CVE-2025-39916,\nCVE-2025-39920, CVE-2025-39923, CVE-2025-39927, CVE-2025-39929,\nCVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937,\nCVE-2025-39938, CVE-2025-39940, CVE-2025-39942, CVE-2025-39943,\nCVE-2025-39944, CVE-2025-39945, CVE-2025-39947, CVE-2025-39948,\nCVE-2025-39949, CVE-2025-39950, CVE-2025-39951, CVE-2025-39952,\nCVE-2025-39953, CVE-2025-39955, CVE-2025-39957, CVE-2025-39961,\nCVE-2025-39965, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-39981,\nCVE-2025-39982, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39991, CVE-2025-39992, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40000,\nCVE-2025-40001, CVE-2025-40006, CVE-2025-40008, CVE-2025-40009,\nCVE-2025-40010, CVE-2025-40011, CVE-2025-40013, CVE-2025-40016,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40024, CVE-2025-40026,\nCVE-2025-40027, CVE-2025-40029, CVE-2025-40030, CVE-2025-40031,\nCVE-2025-40032, CVE-2025-40033, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40042, CVE-2025-40043,\nCVE-2025-40044, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059,\nCVE-2025-40060, CVE-2025-40061, CVE-2025-40062, CVE-2025-40067,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40071, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40084, CVE-2025-40085, CVE-2025-40087,\nCVE-2025-40088, CVE-2025-40092, CVE-2025-40093, CVE-2025-40094,\nCVE-2025-40095, CVE-2025-40096, CVE-2025-40099, CVE-2025-40100,\nCVE-2025-40101, CVE-2025-40103, CVE-2025-40104, CVE-2025-40105,\nCVE-2025-40106, CVE-2025-40107, CVE-2025-40109, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40115, CVE-2025-40116,\nCVE-2025-40118, CVE-2025-40120, CVE-2025-40121, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40134, CVE-2025-40137, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40153, CVE-2025-40154, CVE-2025-40155,\nCVE-2025-40156, CVE-2025-40159, CVE-2025-40160, CVE-2025-40165,\nCVE-2025-40166, CVE-2025-40167, CVE-2025-40169, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40176, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40180, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40192, CVE-2025-40193, CVE-2025-40194,\nCVE-2025-40196, CVE-2025-40198, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40202, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40211, CVE-2025-40218, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40221, CVE-2025-40223, CVE-2025-40226,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237,\nCVE-2025-40238, CVE-2025-40240, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40250,\nCVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40266,\nCVE-2025-40268, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40301, CVE-2025-40303,\nCVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307,\nCVE-2025-40308, CVE-2025-40309, CVE-2025-40310, CVE-2025-40311,\nCVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40328, CVE-2025-40329, CVE-2025-40331, CVE-2025-40333,\nCVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40353,\nCVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68198,\nCVE-2025-68200, CVE-2025-68201, CVE-2025-68204, CVE-2025-68208,\nCVE-2025-68213, CVE-2025-68214, CVE-2025-68217, CVE-2025-68218,\nCVE-2025-68219, CVE-2025-68220, CVE-2025-68222, CVE-2025-68223,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68231, CVE-2025-68233,\nCVE-2025-68235, CVE-2025-68237, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68249,\nCVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68297, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68305, CVE-2025-68307,\nCVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68315, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68327, CVE-2025-68328, CVE-2025-68330,\nCVE-2025-68331, CVE-2025-68339, CVE-2025-68340, CVE-2025-68342,\nCVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-25T19:11:40Z","modified":"2026-11-03T14:35:10.177253555Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8126-1","title":"linux-azure-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nIt was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM32 architecture;\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - PowerPC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - Serial ATA and Parallel ATA drivers;\n - ATM drivers;\n - Drivers core;\n - ATA over ethernet (AOE) driver;\n - DRBD Distributed Replicated Block Device drivers;\n - Block device driver;\n - Network block device driver;\n - Ublk userspace block driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - TPM device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - Buffer Sharing and Synchronization framework;\n - DMA engine subsystem;\n - EDAC drivers;\n - Arm Firmware Framework for ARMv8-A(FFA);\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - FPGA Framework;\n - GPU drivers;\n - HID subsystem;\n - Hardware monitoring drivers;\n - CoreSight HW tracing drivers;\n - I2C subsystem;\n - I3C subsystem;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - IRQ chip drivers;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - MCB driver;\n - Multiple devices driver;\n - Media drivers;\n - Multifunction device drivers;\n - Fastrpc Driver;\n - Microchip PCI driver;\n - Intel Management Engine Interface driver;\n - PCI Endpoint Test driver;\n - TI TPS6594 PFSM driver;\n - VMware VMCI Driver;\n - MMC subsystem;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - MediaTek network drivers;\n - NVDIMM (Non-Volatile Memory Device) drivers;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Amlogic Meson DDR PMU;\n - Performance monitor drivers;\n - PHY drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - Power supply drivers;\n - Powercap sysfs driver;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - RapidIO drivers;\n - Voltage and Current Regulator drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - ASPEED SoC drivers;\n - QCOM SoC drivers;\n - Samsung SoC drivers;\n - Texas Instruments SoC drivers;\n - SPI subsystem;\n - small TFT LCD display modules;\n - Media staging drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - Thunderbolt and USB4 drivers;\n - TTY drivers;\n - UFS subsystem;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - ChipIdea USB driver;\n - USB Device Class drivers;\n - USB core drivers;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - USB Type-C support driver;\n - USB Type-C Connector System Software Interface driver;\n - VFIO drivers;\n - Virtio Host (VHOST) subsystem;\n - Backlight driver;\n - Framebuffer layer;\n - TSM Common Guest driver;\n - Virtio drivers;\n - Xen hypervisor drivers;\n - AFS file system;\n - File systems infrastructure;\n - BTRFS file system;\n - Ceph distributed file system;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - Journaling layer for block devices (JBD2);\n - JFFS2 file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NILFS2 file system;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Overlay file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - DRM display driver;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Memory Management;\n - Internal shared memory driver;\n - LZO compression library;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - padata parallel execution mechanism;\n - Memory management;\n - Networking subsytem;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Netfilter;\n - Network traffic control;\n - Rose network layer;\n - SCTP protocol;\n - Network sockets;\n - UDP network protocol;\n - eXpress Data Path;\n - XFRM subsystem;\n - Digital Audio (PCM) driver;\n - Universal MIDI packet (UMP) support module;\n - Tracing infrastructure;\n - User-space API (UAPI);\n - io_uring subsystem;\n - IPC subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Perf events;\n - Kernel exit() syscall;\n - Kernel futex primitives;\n - IRQ subsystem;\n - Padata parallel execution mechanism;\n - Kernel command line parsing driver;\n - PID allocator;\n - Hibernation control;\n - RCU subsystem;\n - Restartable seuqences system call mechanism;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Maple Tree data structure library;\n - KASAN memory debugging framework;\n - 802.1Q VLAN protocol;\n - 9P file system network protocol;\n - Appletalk network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - CAN network layer;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - Distributed Switch Architecture;\n - HSR network protocol;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Management Component Transport Protocol (MCTP);\n - MultiProtocol Label Switching driver;\n - Multipath TCP;\n - NetLabel subsystem;\n - Netlink;\n - NFC subsystem;\n - Open vSwitch;\n - RDS protocol;\n - RF switch subsystem;\n - RxRPC session sockets;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - Unix domain sockets;\n - VMware vSockets driver;\n - Wireless networking;\n - Integrity Measurement Architecture(IMA) framework;\n - ALSA framework;\n - WCD audio codecs;\n - Intel ASoC drivers;\n - MediaTek ASoC drivers;\n - QCOM ASoC drivers;\n - SoC audio core drivers;\n - USB sound devices;\n - Virtio sound driver;\n - CPU Power monitoring subsystem;\n - KVM subsystem;\n(CVE-2025-21833, CVE-2025-21884, CVE-2025-21931, CVE-2025-22026,\nCVE-2025-22037, CVE-2025-22101, CVE-2025-22102, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22113,\nCVE-2025-22115, CVE-2025-22120, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-22126, CVE-2025-22128, CVE-2025-23129,\nCVE-2025-23130, CVE-2025-23133, CVE-2025-23140, CVE-2025-23141,\nCVE-2025-23142, CVE-2025-23143, CVE-2025-23144, CVE-2025-23145,\nCVE-2025-23146, CVE-2025-23147, CVE-2025-23148, CVE-2025-23149,\nCVE-2025-23150, CVE-2025-23151, CVE-2025-23155, CVE-2025-23156,\nCVE-2025-23157, CVE-2025-23158, CVE-2025-23159, CVE-2025-23160,\nCVE-2025-23161, CVE-2025-23163, CVE-2025-37738, CVE-2025-37739,\nCVE-2025-37740, CVE-2025-37741, CVE-2025-37742, CVE-2025-37744,\nCVE-2025-37745, CVE-2025-37748, CVE-2025-37749, CVE-2025-37754,\nCVE-2025-37755, CVE-2025-37757, CVE-2025-37758, CVE-2025-37759,\nCVE-2025-37761, CVE-2025-37763, CVE-2025-37764, CVE-2025-37765,\nCVE-2025-37766, CVE-2025-37767, CVE-2025-37768, CVE-2025-37769,\nCVE-2025-37770, CVE-2025-37771, CVE-2025-37772, CVE-2025-37773,\nCVE-2025-37775, CVE-2025-37777, CVE-2025-37778, CVE-2025-37780,\nCVE-2025-37781, CVE-2025-37784, CVE-2025-37786, CVE-2025-37787,\nCVE-2025-37788, CVE-2025-37789, CVE-2025-37790, CVE-2025-37792,\nCVE-2025-37793, CVE-2025-37794, CVE-2025-37796, CVE-2025-37799,\nCVE-2025-37800, CVE-2025-37801, CVE-2025-37803, CVE-2025-37805,\nCVE-2025-37808, CVE-2025-37809, CVE-2025-37810, CVE-2025-37811,\nCVE-2025-37812, CVE-2025-37813, CVE-2025-37815, CVE-2025-37816,\nCVE-2025-37817, CVE-2025-37819, CVE-2025-37820, CVE-2025-37822,\nCVE-2025-37823, CVE-2025-37824, CVE-2025-37826, CVE-2025-37827,\nCVE-2025-37828, CVE-2025-37829, CVE-2025-37830, CVE-2025-37831,\nCVE-2025-37836, CVE-2025-37839, CVE-2025-37840, CVE-2025-37841,\nCVE-2025-37842, CVE-2025-37844, CVE-2025-37846, CVE-2025-37849,\nCVE-2025-37850, CVE-2025-37851, CVE-2025-37852, CVE-2025-37853,\nCVE-2025-37854, CVE-2025-37856, CVE-2025-37857, CVE-2025-37858,\nCVE-2025-37859, CVE-2025-37860, CVE-2025-37861, CVE-2025-37862,\nCVE-2025-37863, CVE-2025-37864, CVE-2025-37865, CVE-2025-37867,\nCVE-2025-37869, CVE-2025-37871, CVE-2025-37872, CVE-2025-37873,\nCVE-2025-37874, CVE-2025-37875, CVE-2025-37878, CVE-2025-37879,\nCVE-2025-37881, CVE-2025-37883, CVE-2025-37884, CVE-2025-37885,\nCVE-2025-37886, CVE-2025-37887, CVE-2025-37891, CVE-2025-37892,\nCVE-2025-37897, CVE-2025-37899, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37956, CVE-2025-37957,\nCVE-2025-37959, CVE-2025-37960, CVE-2025-37961, CVE-2025-37962,\nCVE-2025-37963, CVE-2025-37967, CVE-2025-37968, CVE-2025-37969,\nCVE-2025-37970, CVE-2025-37972, CVE-2025-37973, CVE-2025-37975,\nCVE-2025-37977, CVE-2025-37978, CVE-2025-37979, CVE-2025-37980,\nCVE-2025-37982, CVE-2025-37983, CVE-2025-37984, CVE-2025-37985,\nCVE-2025-37986, CVE-2025-37987, CVE-2025-37988, CVE-2025-37989,\nCVE-2025-37990, CVE-2025-37991, CVE-2025-37992, CVE-2025-37994,\nCVE-2025-37995, CVE-2025-37998, CVE-2025-38003, CVE-2025-38004,\nCVE-2025-38005, CVE-2025-38006, CVE-2025-38007, CVE-2025-38008,\nCVE-2025-38009, CVE-2025-38010, CVE-2025-38011, CVE-2025-38013,\nCVE-2025-38014, CVE-2025-38015, CVE-2025-38018, CVE-2025-38019,\nCVE-2025-38020, CVE-2025-38023, CVE-2025-38024, CVE-2025-38027,\nCVE-2025-38031, CVE-2025-38034, CVE-2025-38035, CVE-2025-38037,\nCVE-2025-38039, CVE-2025-38040, CVE-2025-38043, CVE-2025-38044,\nCVE-2025-38045, CVE-2025-38048, CVE-2025-38051, CVE-2025-38052,\nCVE-2025-38053, CVE-2025-38055, CVE-2025-38057, CVE-2025-38058,\nCVE-2025-38059, CVE-2025-38060, CVE-2025-38061, CVE-2025-38062,\nCVE-2025-38063, CVE-2025-38065, CVE-2025-38066, CVE-2025-38067,\nCVE-2025-38068, CVE-2025-38071, CVE-2025-38072, CVE-2025-38074,\nCVE-2025-38075, CVE-2025-38077, CVE-2025-38078, CVE-2025-38079,\nCVE-2025-38080, CVE-2025-38081, CVE-2025-38084, CVE-2025-38085,\nCVE-2025-38086, CVE-2025-38087, CVE-2025-38088, CVE-2025-38089,\nCVE-2025-38090, CVE-2025-38094, CVE-2025-38095, CVE-2025-38097,\nCVE-2025-38098, CVE-2025-38099, CVE-2025-38100, CVE-2025-38101,\nCVE-2025-38102, CVE-2025-38103, CVE-2025-38104, CVE-2025-38105,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38245, CVE-2025-38246,\nCVE-2025-38248, CVE-2025-38249, CVE-2025-38250, CVE-2025-38251,\nCVE-2025-38253, CVE-2025-38255, CVE-2025-38257, CVE-2025-38258,\nCVE-2025-38259, CVE-2025-38260, CVE-2025-38262, CVE-2025-38263,\nCVE-2025-38264, CVE-2025-38265, CVE-2025-38269, CVE-2025-38274,\nCVE-2025-38275, CVE-2025-38277, CVE-2025-38278, CVE-2025-38279,\nCVE-2025-38280, CVE-2025-38282, CVE-2025-38283, CVE-2025-38285,\nCVE-2025-38286, CVE-2025-38289, CVE-2025-38290, CVE-2025-38292,\nCVE-2025-38293, CVE-2025-38295, CVE-2025-38298, CVE-2025-38299,\nCVE-2025-38300, CVE-2025-38303, CVE-2025-38304, CVE-2025-38305,\nCVE-2025-38307, CVE-2025-38310, CVE-2025-38312, CVE-2025-38313,\nCVE-2025-38319, CVE-2025-38320, CVE-2025-38321, CVE-2025-38322,\nCVE-2025-38323, CVE-2025-38324, CVE-2025-38326, CVE-2025-38328,\nCVE-2025-38331, CVE-2025-38332, CVE-2025-38333, CVE-2025-38334,\nCVE-2025-38335, CVE-2025-38336, CVE-2025-38337, CVE-2025-38338,\nCVE-2025-38342, CVE-2025-38343, CVE-2025-38344, CVE-2025-38345,\nCVE-2025-38346, CVE-2025-38347, CVE-2025-38348, CVE-2025-38349,\nCVE-2025-38351, CVE-2025-38354, CVE-2025-38361, CVE-2025-38362,\nCVE-2025-38363, CVE-2025-38364, CVE-2025-38365, CVE-2025-38368,\nCVE-2025-38369, CVE-2025-38371, CVE-2025-38373, CVE-2025-38374,\nCVE-2025-38375, CVE-2025-38376, CVE-2025-38377, CVE-2025-38382,\nCVE-2025-38384, CVE-2025-38385, CVE-2025-38386, CVE-2025-38387,\nCVE-2025-38388, CVE-2025-38389, CVE-2025-38390, CVE-2025-38391,\nCVE-2025-38392, CVE-2025-38393, CVE-2025-38395, CVE-2025-38396,\nCVE-2025-38399, CVE-2025-38400, CVE-2025-38401, CVE-2025-38402,\nCVE-2025-38403, CVE-2025-38405, CVE-2025-38406, CVE-2025-38407,\nCVE-2025-38408, CVE-2025-38409, CVE-2025-38410, CVE-2025-38412,\nCVE-2025-38414, CVE-2025-38415, CVE-2025-38416, CVE-2025-38418,\nCVE-2025-38419, CVE-2025-38420, CVE-2025-38422, CVE-2025-38424,\nCVE-2025-38425, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38502, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38556,\nCVE-2025-38560, CVE-2025-38561, CVE-2025-38562, CVE-2025-38566,\nCVE-2025-38568, CVE-2025-38569, CVE-2025-38571, CVE-2025-38572,\nCVE-2025-38574, CVE-2025-38576, CVE-2025-38577, CVE-2025-38578,\nCVE-2025-38579, CVE-2025-38581, CVE-2025-38582, CVE-2025-38583,\nCVE-2025-38584, CVE-2025-38585, CVE-2025-38587, CVE-2025-38588,\nCVE-2025-38590, CVE-2025-38593, CVE-2025-38595, CVE-2025-38601,\nCVE-2025-38602, CVE-2025-38604, CVE-2025-38608, CVE-2025-38609,\nCVE-2025-38610, CVE-2025-38612, CVE-2025-38614, CVE-2025-38615,\nCVE-2025-38619, CVE-2025-38622, CVE-2025-38623, CVE-2025-38624,\nCVE-2025-38625, CVE-2025-38626, CVE-2025-38627, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38643, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38709, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39678, CVE-2025-39679, CVE-2025-39681, CVE-2025-39683,\nCVE-2025-39684, CVE-2025-39685, CVE-2025-39686, CVE-2025-39687,\nCVE-2025-39689, CVE-2025-39691, CVE-2025-39692, CVE-2025-39693,\nCVE-2025-39694, CVE-2025-39697, CVE-2025-39698, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39889, CVE-2025-39890, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39895, CVE-2025-39897, CVE-2025-39899,\nCVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39914, CVE-2025-39916,\nCVE-2025-39920, CVE-2025-39923, CVE-2025-39927, CVE-2025-39929,\nCVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937,\nCVE-2025-39938, CVE-2025-39940, CVE-2025-39942, CVE-2025-39943,\nCVE-2025-39944, CVE-2025-39945, CVE-2025-39946, CVE-2025-39947,\nCVE-2025-39948, CVE-2025-39949, CVE-2025-39950, CVE-2025-39951,\nCVE-2025-39952, CVE-2025-39953, CVE-2025-39955, CVE-2025-39957,\nCVE-2025-39961, CVE-2025-39965, CVE-2025-39967, CVE-2025-39968,\nCVE-2025-39969, CVE-2025-39970, CVE-2025-39971, CVE-2025-39972,\nCVE-2025-39973, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980,\nCVE-2025-39981, CVE-2025-39982, CVE-2025-39985, CVE-2025-39986,\nCVE-2025-39987, CVE-2025-39988, CVE-2025-39989, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40019, CVE-2025-40020,\nCVE-2025-40021, CVE-2025-40024, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40035, CVE-2025-40036, CVE-2025-40037,\nCVE-2025-40038, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40047, CVE-2025-40048, CVE-2025-40049, CVE-2025-40051,\nCVE-2025-40052, CVE-2025-40053, CVE-2025-40055, CVE-2025-40056,\nCVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,\nCVE-2025-40061, CVE-2025-40062, CVE-2025-40067, CVE-2025-40068,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40077, CVE-2025-40078,\nCVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40083,\nCVE-2025-40084, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101,\nCVE-2025-40103, CVE-2025-40104, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40107, CVE-2025-40109, CVE-2025-40110, CVE-2025-40111,\nCVE-2025-40112, CVE-2025-40115, CVE-2025-40116, CVE-2025-40118,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40123, CVE-2025-40124,\nCVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40129,\nCVE-2025-40134, CVE-2025-40137, CVE-2025-40140, CVE-2025-40141,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156,\nCVE-2025-40159, CVE-2025-40160, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40215, CVE-2025-40218, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40221, CVE-2025-40223, CVE-2025-40226,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237,\nCVE-2025-40238, CVE-2025-40240, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40250,\nCVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40266,\nCVE-2025-40268, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40297, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734, CVE-2025-68750)\n","status":"published","published":"2026-03-25T19:13:52Z","modified":"2026-11-03T14:35:29.863770912Z","updated_at":"2026-11-03T15:16:14.724953Z"},{"id":"USN-8165-1","title":"linux-azure-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Hardware random number generator core;\n - Character device driver;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - ISDN/mISDN subsystem;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - Virtio Host (VHOST) subsystem;\n - Framebuffer layer;\n - Xen hypervisor drivers;\n - AFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - Ethernet bridge;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40202, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40206, CVE-2025-40207, CVE-2025-40211,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40223, CVE-2025-40226, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40235, CVE-2025-40237, CVE-2025-40238, CVE-2025-40240,\nCVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40250, CVE-2025-40251, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40266, CVE-2025-40268, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40284,\nCVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288,\nCVE-2025-40289, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294,\nCVE-2025-40301, CVE-2025-40303, CVE-2025-40304, CVE-2025-40305,\nCVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,\nCVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313,\nCVE-2025-40314, CVE-2025-40315, CVE-2025-40317, CVE-2025-40318,\nCVE-2025-40319, CVE-2025-40320, CVE-2025-40321, CVE-2025-40322,\nCVE-2025-40323, CVE-2025-40324, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40331, CVE-2025-40333, CVE-2025-40337, CVE-2025-40339,\nCVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40347, CVE-2025-40349, CVE-2025-40350,\nCVE-2025-40351, CVE-2025-40353, CVE-2025-40358, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68171, CVE-2025-68172,\nCVE-2025-68173, CVE-2025-68176, CVE-2025-68177, CVE-2025-68178,\nCVE-2025-68179, CVE-2025-68180, CVE-2025-68183, CVE-2025-68184,\nCVE-2025-68185, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192,\nCVE-2025-68194, CVE-2025-68198, CVE-2025-68200, CVE-2025-68201,\nCVE-2025-68204, CVE-2025-68208, CVE-2025-68213, CVE-2025-68214,\nCVE-2025-68217, CVE-2025-68218, CVE-2025-68219, CVE-2025-68220,\nCVE-2025-68222, CVE-2025-68223, CVE-2025-68227, CVE-2025-68229,\nCVE-2025-68231, CVE-2025-68233, CVE-2025-68235, CVE-2025-68237,\nCVE-2025-68238, CVE-2025-68241, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68246, CVE-2025-68249, CVE-2025-68282, CVE-2025-68283,\nCVE-2025-68284, CVE-2025-68285, CVE-2025-68286, CVE-2025-68287,\nCVE-2025-68288, CVE-2025-68289, CVE-2025-68290, CVE-2025-68295,\nCVE-2025-68297, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68305, CVE-2025-68307, CVE-2025-68308, CVE-2025-68310,\nCVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68315,\nCVE-2025-68320, CVE-2025-68321, CVE-2025-68322, CVE-2025-68327,\nCVE-2025-68328, CVE-2025-68330, CVE-2025-68331, CVE-2025-68339,\nCVE-2025-68340, CVE-2025-68342, CVE-2025-68343, CVE-2025-68734,\nCVE-2026-23060, CVE-2026-23074, CVE-2026-23111)\n","status":"published","published":"2026-04-09T23:38:24Z","modified":"2026-11-04T20:01:11.526209673Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8261-1","title":"linux-xilinx vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - MIPS architecture;\n - Nios II architecture;\n - PA-RISC architecture;\n - PowerPC architecture;\n - RISC-V architecture;\n - S390 architecture;\n - Sun Sparc architecture;\n - User-Mode Linux (UML);\n - x86 architecture;\n - Xtensa architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - ACPI drivers;\n - ATM drivers;\n - Drivers core;\n - Block device driver;\n - Network block device driver;\n - Bluetooth drivers;\n - Bus devices;\n - Character device driver;\n - Hardware random number generator core;\n - TPM device driver;\n - Clock framework and drivers;\n - Data acquisition framework and drivers;\n - CPU frequency scaling framework;\n - Hardware crypto device drivers;\n - Device frequency scaling framework;\n - DMA engine subsystem;\n - ARM SCMI message protocol;\n - EFI core;\n - Intel Stratix 10 firmware drivers;\n - GPU drivers;\n - HID subsystem;\n - Hardware monitoring drivers;\n - CoreSight HW tracing drivers;\n - IIO subsystem;\n - InfiniBand drivers;\n - Input Device core drivers;\n - Input Device (Miscellaneous) drivers;\n - Input Device (Tablet) drivers;\n - IOMMU subsystem;\n - IRQ chip drivers;\n - ISDN/mISDN subsystem;\n - Macintosh device drivers;\n - Mailbox framework;\n - Multiple devices driver;\n - Media drivers;\n - Fastrpc Driver;\n - MOST (Media Oriented Systems Transport) drivers;\n - MTD block device drivers;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - STMicroelectronics network drivers;\n - Texas Instruments network drivers;\n - Ethernet team driver;\n - MediaTek network drivers;\n - NVME drivers;\n - PA-RISC drivers;\n - PCI subsystem;\n - PCCARD (PCMCIA/CardBus) bus subsystem;\n - Performance monitor drivers;\n - Pin controllers subsystem;\n - Chrome hardware platform drivers;\n - x86 platform drivers;\n - ARM PM domains;\n - PPS (Pulse Per Second) driver;\n - PTP clock framework;\n - PWM drivers;\n - Voltage and Current Regulator drivers;\n - Remote Processor subsystem;\n - S/390 drivers;\n - SCSI subsystem;\n - Texas Instruments SoC drivers;\n - SPI subsystem;\n - Media Oriented Systems Transport (MOST) driver;\n - Realtek RTL8723BS SDIO drivers;\n - TCM subsystem;\n - Trusted Execution Environment drivers;\n - TTY drivers;\n - Userspace I/O drivers;\n - Cadence USB3 driver;\n - DesignWare USB3 driver;\n - USB Gadget drivers;\n - USB Host Controller drivers;\n - Renesas USBHS Controller drivers;\n - USB Mass Storage drivers;\n - USB Type-C Connector System Software Interface driver;\n - Virtio Host (VHOST) subsystem;\n - Backlight driver;\n - Framebuffer layer;\n - Watchdog drivers;\n - Xen hypervisor drivers;\n - AFS file system;\n - BFS file system;\n - BTRFS file system;\n - Ceph distributed file system;\n - File systems infrastructure;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - F2FS file system;\n - FUSE (File system in Userspace);\n - GFS2 file system;\n - HFS file system;\n - HFS+ file system;\n - HugeTLB file system;\n - Journaling layer for block devices (JBD2);\n - JFS file system;\n - KERNFS file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - File system notification infrastructure;\n - NTFS3 file system;\n - OCFS2 file system;\n - OrangeFS file system;\n - Proc file system;\n - Diskquota system;\n - SMB network file system;\n - SquashFS file system;\n - UDF file system;\n - XFS file system;\n - Asynchronous Transfer Mode (ATM) subsystem;\n - BPF subsystem;\n - Ethernet bridge;\n - Mellanox drivers;\n - NFS page cache wrapper;\n - Memory management;\n - Memory Management;\n - Media input infrastructure;\n - Bluetooth subsystem;\n - IP tunnels definitions;\n - Network traffic control;\n - Rose network layer;\n - Network sockets;\n - io_uring subsystem;\n - Control group (cgroup);\n - Kernel crash support code;\n - Kernel futex primitives;\n - Locking primitives;\n - PID allocator;\n - Scheduler infrastructure;\n - Shadow Call Stack mechanism;\n - Syscalls implementation;\n - Timer subsystem;\n - Tracing infrastructure;\n - 9P file system network protocol;\n - Amateur Radio drivers;\n - B.A.T.M.A.N. meshing protocol;\n - CAIF protocol;\n - Ceph Core library;\n - Networking core;\n - Devlink API;\n - Ethtool driver;\n - Handshake API;\n - HSR network protocol;\n - IPv4 networking;\n - IPv6 networking;\n - MAC80211 subsystem;\n - Multipath TCP;\n - Netfilter;\n - NET/ROM layer;\n - NFC subsystem;\n - Open vSwitch;\n - RF switch subsystem;\n - SCTP protocol;\n - SMC sockets;\n - Sun RPC protocol;\n - TIPC protocol;\n - TLS protocol;\n - VMware vSockets driver;\n - Wireless networking;\n - eXpress Data Path;\n - XFRM subsystem;\n - Integrity Measurement Architecture(IMA) framework;\n - Key management;\n - Simplified Mandatory Access Control Kernel framework;\n - FireWire sound drivers;\n - HD-audio driver;\n - Turtle Beach Wavefront ALSA driver;\n - Intel ASoC drivers;\n - QCOM ASoC drivers;\n - STMicroelectronics SoC drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2024-57795, CVE-2025-21833, CVE-2025-22022, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22111,\nCVE-2025-22113, CVE-2025-22121, CVE-2025-22124, CVE-2025-22125,\nCVE-2025-23129, CVE-2025-23130, CVE-2025-23133, CVE-2025-23143,\nCVE-2025-37860, CVE-2025-38022, CVE-2025-38105, CVE-2025-38234,\nCVE-2025-38502, CVE-2025-38556, CVE-2025-38627, CVE-2025-38643,\nCVE-2025-38709, CVE-2025-39678, CVE-2025-39697, CVE-2025-39805,\nCVE-2025-39806, CVE-2025-39807, CVE-2025-39808, CVE-2025-39810,\nCVE-2025-39811, CVE-2025-39812, CVE-2025-39813, CVE-2025-39815,\nCVE-2025-39817, CVE-2025-39819, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39825, CVE-2025-39826, CVE-2025-39827, CVE-2025-39828,\nCVE-2025-39829, CVE-2025-39832, CVE-2025-39835, CVE-2025-39836,\nCVE-2025-39838, CVE-2025-39839, CVE-2025-39841, CVE-2025-39842,\nCVE-2025-39843, CVE-2025-39844, CVE-2025-39845, CVE-2025-39846,\nCVE-2025-39847, CVE-2025-39848, CVE-2025-39849, CVE-2025-39850,\nCVE-2025-39851, CVE-2025-39852, CVE-2025-39853, CVE-2025-39854,\nCVE-2025-39857, CVE-2025-39860, CVE-2025-39861, CVE-2025-39863,\nCVE-2025-39864, CVE-2025-39865, CVE-2025-39866, CVE-2025-39869,\nCVE-2025-39870, CVE-2025-39871, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39877, CVE-2025-39880, CVE-2025-39881, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39886, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39895, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,\nCVE-2025-40221, CVE-2025-40223, CVE-2025-40226, CVE-2025-40231,\nCVE-2025-40233, CVE-2025-40235, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40240, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244,\nCVE-2025-40245, CVE-2025-40248, CVE-2025-40250, CVE-2025-40251,\nCVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40257,\nCVE-2025-40258, CVE-2025-40259, CVE-2025-40261, CVE-2025-40262,\nCVE-2025-40263, CVE-2025-40264, CVE-2025-40266, CVE-2025-40268,\nCVE-2025-40269, CVE-2025-40271, CVE-2025-40272, CVE-2025-40273,\nCVE-2025-40275, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,\nCVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,\nCVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,\nCVE-2025-40288, CVE-2025-40289, CVE-2025-40292, CVE-2025-40293,\nCVE-2025-40294, CVE-2025-40301, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40325,\nCVE-2025-40328, CVE-2025-40329, CVE-2025-40331, CVE-2025-40333,\nCVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40353,\nCVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68198,\nCVE-2025-68200, CVE-2025-68201, CVE-2025-68204, CVE-2025-68206,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68297, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68305, CVE-2025-68307,\nCVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68315, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68354,\nCVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68734, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68753, CVE-2025-68755,\nCVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759,\nCVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766,\nCVE-2025-68767, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68786,\nCVE-2025-68787, CVE-2025-68788, CVE-2025-68794, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68798, CVE-2025-68799,\nCVE-2025-68800, CVE-2025-68801, CVE-2025-68804, CVE-2025-68806,\nCVE-2025-68808, CVE-2025-68809, CVE-2025-68810, CVE-2025-68811,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71147,\nCVE-2025-71148, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2026-23060, CVE-2026-23074, CVE-2026-23111,\nCVE-2026-23112, CVE-2026-23209, CVE-2026-23231, CVE-2026-23273)\n","status":"published","published":"2026-05-07T15:54:20Z","modified":"2026-09-07T14:05:25.637433365Z","updated_at":"2026-11-02T16:58:22.951676Z"}]}}