{"id":"CVE-2025-39980","aliases":["AZL-68507","BELL-CVE-2025-39980","CLSA-2026-1791741836","CLSA-2026-1791800936","DEBIAN-CVE-2025-39980","DLA-4379-1","DLA-4404-1","DSA-6053-1","EUVD-2025-34592","GHSA-9g6c-7w9m-p2mh","MGASA-2025-0309","MGASA-2025-0310","OESA-2026-2417","OESA-2026-2418","ROOT-OS-DEBIAN-11-CVE-2025-39980","ROOT-OS-DEBIAN-12-CVE-2025-39980","ROOT-OS-UBUNTU-2404-CVE-2025-39980","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-39980","USN-8033-1","USN-8033-2","USN-8033-3","USN-8033-4","USN-8033-5","USN-8033-6","USN-8033-7","USN-8033-8","USN-8034-1","USN-8034-2","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-8141-1","USN-8163-1","USN-8163-2","USN-8165-1","USN-8243-1","USN-8261-1","openSUSE-SU-2025:20172-1"],"status":"published","title":"nexthop: Forbid FDB status change while nexthop is in a group","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","severity":{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium","from":"osv"},"epss":{"day":"2026-11-11","score":0.00233,"percentile":0.14369,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-10-15T07:56:00Z","modified":"2026-11-11T10:00:38Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.112.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.155-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.51-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.10.245","5.15.194","6.1.155","6.6.109","6.12.50","6.16.10"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.158-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.57-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.16.10-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu: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:Pro:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1100.107~20.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1110.119~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1100.109~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-170.180~20.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1094.97~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1095.101~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-170.180~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1052.52~20.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1097.103~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1095.99~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-170.180"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1100.107"],"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","fixed_in":["5.15.0-1109.118"],"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","fixed_in":["5.15.0-1109.118.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","fixed_in":["5.15.0-1100.109"],"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-gke","fixed_in":["5.15.0-1096.102"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1083.91"],"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","fixed_in":["5.15.0-1094.97"],"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-intel-iotg","fixed_in":["5.15.0-1095.101"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1092.97"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-170.180"],"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","fixed_in":["5.15.0-1095.96"],"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-nvidia-tegra","fixed_in":["5.15.0-1052.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1041.41"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1097.103"],"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-raspi","fixed_in":["5.15.0-1097.100"],"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:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1064.68"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1084.86"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1092.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1099.108"],"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:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1100.107+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1109.118+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-170.180+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1100.109+fips1"],"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-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-azure-nvidia","fixed_in":["6.8.0-1039.42"],"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-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-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-oracle","fixed_in":["6.8.0-1047.48"],"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: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-6.6"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-aws","fixed_in":["6.17.0-1003.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-azure","fixed_in":["6.17.0-1006.6"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-gcp","fixed_in":["6.17.0-1003.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-oracle","fixed_in":["6.17.0-1003.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-raspi","fixed_in":["6.17.0-1004.4"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-realtime","fixed_in":["6.17.0-1002.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-riscv","fixed_in":["6.17.0-6.6.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.112.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.151-r0"},{"fixed":"6.1.155-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.44-r0"},{"fixed":"6.12.51-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els15"}]}],"bundled":130},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els15"}]}],"bundled":197},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.8.0"},{"fixed":"5.10.245"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.194"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.155"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.109"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.50"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.16.10"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.158-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.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.16.10-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.115-1","6.12.115-2","6.12.116-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.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"]},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.158-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1","6.1.119-1~deb11u1","6.1.128-1~deb11u1","6.1.129-1~deb11u1","6.1.137-1~deb11u1","6.1.140-1~deb11u1","6.1.147-1~deb11u1","6.1.148-1~deb11u1","6.1.153-1~deb11u1"],"bundled":128},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.247-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.223-1","5.10.226-1","5.10.234-1","5.10.237-1","5.10.244-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":135},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.158-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"bundled":89},{"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","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.12.138.oe2403"}]}],"bundled":108},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.1.12.150.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu: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:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107~20.04.2"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1"]},{"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:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180~20.04.3"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.97~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.101~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.52~20.04.2"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.103~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.99~20.04.1"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108"]},{"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-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1096.102"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1083.91"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.97"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"]},{"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-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.101"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.97"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.96"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95"]},{"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-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.52"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1041.41"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.103"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102"]},{"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-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"]},{"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:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.68"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1084.86"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.94"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.108"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107"]},{"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:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1"]},{"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-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"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-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-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-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.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-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: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-6.6"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1003.3"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.6"}]}],"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"]},{"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-1003.3"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1003.3"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1004.4"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1002.3"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-6.6.1"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180~20.04.3"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.97~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1096.102"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1083.91"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.97"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.94"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.108"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-170.180+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.107~20.04.2"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.109~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.103~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.97"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.103"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.96"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.101~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1064.68"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.101"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100"],"bundled":114},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.52~20.04.2"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1"],"bundled":115},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1052.52"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51"],"bundled":115},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1041.41"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40"],"bundled":115},{"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:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"],"bundled":334},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"],"bundled":350},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"],"bundled":350},{"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:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1"],"bundled":426},{"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: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}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ac0)"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp (6ag1518-4ax00-4ac0)"}],"references":[{"url":"https://git.kernel.org/stable/c/e1e87ac0daacd51f522ecd1645cd76b5809303ed","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/0e7bfe7a268ccbd7859730c529161cafbf44637c","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/ec428fff792b7bd15b248dafca2e654b666b1304","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/24046d31f6f92220852d393d510b6062843e3fbd","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/f0e49fd13afe9dea7a09a1c9537fd00cea22badb","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/8dd4aa0122885f710930de135af2adc4ccc3238f","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/390b3a300d7872cef9588f003b204398be69ce08","tags":["web","report"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-019113.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-457936.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39980","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-9g6c-7w9m-p2mh"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-39980","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1791741836.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-55881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38465","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39969","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-100075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46199","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46230","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46327","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63919","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64034","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64545","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74717","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74736","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80534","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93228","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97517","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98374","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1791800936.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21632","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21880","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21889","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21895","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38552","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39776","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39926","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68336","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23458","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31447","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31516","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31639","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46201","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53353","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64330","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64380","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64382","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64387","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74608","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74642","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80576","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89534","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98173","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39980.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-39980","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-2026-2417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21970","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37793","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37844","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38183","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68795","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23260","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43407","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23352","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43470","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-39980","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-39980","tags":["report"]},{"url":"https://git.kernel.org/linus/390b3a300d7872cef9588f003b204398be69ce08","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8033-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8034-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8034-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-7","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8033-8","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-8141-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8165-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8243-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8261-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-53114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","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-39880","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-39907","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-39923","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-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","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-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-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-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-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","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-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","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-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","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-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","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-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","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-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","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-40215","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-40223","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-40240","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-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71162","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-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-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","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-39909","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-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-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-39944","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-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","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-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","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-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40000","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-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","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-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","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-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-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","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-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40180","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-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]},{"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-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-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-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-40297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21780","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-40040","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-68257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","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-68346","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-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-68372","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-68746","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-68764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68765","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-68771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68774","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-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-68787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68788","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-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-68803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","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-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-71066","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-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-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-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-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-71108","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-71120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","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-71136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23047","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-2023-53041","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-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-2023-53421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-54207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","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-38234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68371","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-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-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-68763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68770","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-68775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","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-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","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-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71135","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-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-2026-23112","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"]}],"sources":{"cve":[{"id":"CVE-2025-39980","title":"nexthop: Forbid FDB status change while nexthop is in a group","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T07:56:00.275Z","modified":"2026-11-10T12:37:28.09Z","updated_at":"2026-11-10T13:38:44.039016Z"}],"euvd":[{"id":"EUVD-2025-34592","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T07:56:00Z","modified":"2026-11-10T12:37:28Z","updated_at":"2026-11-10T14:21:12.343171Z"}],"ghsa":[{"id":"GHSA-9g6c-7w9m-p2mh","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T09:30:17Z","modified":"2026-10-15T03:34:59Z","updated_at":"2026-11-02T15:13:31.944762Z"}],"nvd":[{"id":"CVE-2025-39980","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T08:15:35.887Z","modified":"2026-11-10T13:17:53.767Z","updated_at":"2026-11-10T16:19:44.964795Z"}],"osv":[{"id":"OESA-2026-2417","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400Call Trace: \u0026lt;TASK\u0026gt; kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.(CVE-2024-56760)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: fix nfs_release_folio() to not deadlock via kcompactd writeback\n\nAdd PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so\nnfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.\n\nOtherwise NFS can deadlock waiting for kcompactd enduced writeback which\nrecurses back to NFS (which triggers writeback to NFSD via NFS loopback\nmount on the same host, NFSD blocks waiting for XFS\u0026apos;s call to\n__filemap_get_folio):\n\n6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.\n\n{---\n[58] \u0026quot;kcompactd0\u0026quot;\n[\u0026lt;0\u0026gt;] folio_wait_bit+0xe8/0x200\n[\u0026lt;0\u0026gt;] folio_wait_writeback+0x2b/0x80\n[\u0026lt;0\u0026gt;] nfs_wb_folio+0x80/0x1b0 [nfs]\n[\u0026lt;0\u0026gt;] nfs_release_folio+0x68/0x130 [nfs]\n[\u0026lt;0\u0026gt;] split_huge_page_to_list_to_order+0x362/0x840\n[\u0026lt;0\u0026gt;] migrate_pages_batch+0x43d/0xb90\n[\u0026lt;0\u0026gt;] migrate_pages_sync+0x9a/0x240\n[\u0026lt;0\u0026gt;] migrate_pages+0x93c/0x9f0\n[\u0026lt;0\u0026gt;] compact_zone+0x8e2/0x1030\n[\u0026lt;0\u0026gt;] compact_node+0xdb/0x120\n[\u0026lt;0\u0026gt;] kcompactd+0x121/0x2e0\n[\u0026lt;0\u0026gt;] kthread+0xcf/0x100\n[\u0026lt;0\u0026gt;] ret_from_fork+0x31/0x40\n[\u0026lt;0\u0026gt;] ret_from_fork_asm+0x1a/0x30\n---}\n\n[(CVE-2025-21908)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio\n\nCommit b15c87263a69 (\u0026quot;hwpoison, memory_hotplug: allow hwpoisoned pages to\nbe offlined) add page poison checks in do_migrate_range in order to make\noffline hwpoisoned page possible by introducing isolate_lru_page and\ntry_to_unmap for hwpoisoned page.  However folio lock must be held before\ncalling try_to_unmap.  Add it to fix this problem.\n\nWarning will be produced if folio is not locked during unmap:\n\n  ------------[ cut here ]------------\n  kernel BUG at ./include/linux/swapops.h:400!\n  Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G        W          6.13.0-rc1-00016-g3c434c7ee82a-dirty #41\n  Tainted: [W]=WARN\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n  pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : try_to_unmap_one+0xb08/0xd3c\n  lr : try_to_unmap_one+0x3dc/0xd3c\n  Call trace:\n   try_to_unmap_one+0xb08/0xd3c (P)\n   try_to_unmap_one+0x3dc/0xd3c (L)\n   rmap_walk_anon+0xdc/0x1f8\n   rmap_walk+0x3c/0x58\n   try_to_unmap+0x88/0x90\n   unmap_poisoned_folio+0x30/0xa8\n   do_migrate_range+0x4a0/0x568\n   offline_pages+0x5a4/0x670\n   memory_block_action+0x17c/0x374\n   memory_subsys_offline+0x3c/0x78\n   device_offline+0xa4/0xd0\n   state_store+0x8c/0xf0\n   dev_attr_store+0x18/0x2c\n   sysfs_kf_write+0x44/0x54\n   kernfs_fop_write_iter+0x118/0x1a8\n   vfs_write+0x3a8/0x4bc\n   ksys_write+0x6c/0xf8\n   __arm64_sys_write+0x1c/0x28\n   invoke_syscall+0x44/0x100\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x30/0xd0\n   el0t_64_sync_handler+0xc8/0xcc\n   el0t_64_sync+0x198/0x19c\n  Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000)\n  ---[ end trace 0000000000000000 ]---(CVE-2025-21931)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Bridge, fix the crash caused by LAG state check\n\nWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event is\ntriggered. Driver finds the lower devices (PFs) to flush all the\noffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns\nfalse if one of PF is unloaded. In such case,\nmlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of\nthe alive PF, and the flush is skipped.\n\nBesides, the bridge fdb entry\u0026apos;s lastuse is updated in mlx5 bridge\nevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be\nignored in this case because the upper interface for bond is deleted,\nand the entry will never be aged because lastuse is never updated.\n\nTo make things worse, as the entry is alive, mlx5 bridge workqueue\nkeeps sending that event, which is then handled by kernel bridge\nnotifier. It causes the following crash when accessing the passed bond\nnetdev which is already destroyed.\n\nTo fix this issue, remove such checks. LAG state is already checked in\ncommit 15f8f168952f (\u0026quot;net/mlx5: Bridge, verify LAG state when adding\nbond to bridge\u0026quot;), driver still need to skip offload if LAG becomes\ninvalid state after initialization.\n\n Oops: stack segment: 0000 [#1] SMP\n CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core]\n RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge]\n Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 \u0026lt;4c\u0026gt; 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7\n RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297\n RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff\n RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0\n RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8\n R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60\n R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000\n FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die_body+0x1a/0x60\n  ? die+0x38/0x60\n  ? do_trap+0x10b/0x120\n  ? do_error_trap+0x64/0xa0\n  ? exc_stack_segment+0x33/0x50\n  ? asm_exc_stack_segment+0x22/0x30\n  ? br_switchdev_event+0x2c/0x110 [bridge]\n  ? sched_balance_newidle.isra.149+0x248/0x390\n  notifier_call_chain+0x4b/0xa0\n  atomic_notifier_call_chain+0x16/0x20\n  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]\n  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]\n  process_scheduled_works+0x81/0x390\n  worker_thread+0x106/0x250\n  ? bh_worker+0x110/0x110\n  kthread+0xb7/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n  \u0026lt;/TASK\u0026gt;(CVE-2025-21970)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Prevent creation of classes with TC_H_ROOT\n\nThe function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination\ncondition when traversing up the qdisc tree to update parent backlog\ncounters. However, if a class is created with classid TC_H_ROOT, the\ntraversal terminates prematurely at this class instead of reaching the\nactual root qdisc, causing parent statistics to be incorrectly maintained.\nIn case of DRR, this could lead to a crash as reported by Mingi Cho.\n\nPrevent the creation of any Qdisc class with classid TC_H_ROOT\n(0xFFFFFFFF) across all qdisc types, as suggested by Jamal.(CVE-2025-21971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched: address a potential NULL pointer dereference in the GRED scheduler.\n\nIf kzalloc in gred_init returns a NULL pointer, the code follows the\nerror handling path, invoking gred_destroy. This, in turn, calls\ngred_offload, where memset could receive a NULL pointer as input,\npotentially leading to a kernel crash.\n\nWhen table-\u0026gt;opt is NULL in gred_init(), gred_change_table_def()\nis not called yet, so it is not necessary to call -\u0026gt;ndo_setup_tc()\nin gred_offload().(CVE-2025-21980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: switchdev: Convert blocking notification chain to a raw one\n\nA blocking notification chain uses a read-write semaphore to protect the\nintegrity of the chain. The semaphore is acquired for writing when\nadding / removing notifiers to / from the chain and acquired for reading\nwhen traversing the chain and informing notifiers about an event.\n\nIn case of the blocking switchdev notification chain, recursive\nnotifications are possible which leads to the semaphore being acquired\ntwice for reading and to lockdep warnings being generated [1].\n\nSpecifically, this can happen when the bridge driver processes a\nSWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications\nabout deferred events when calling switchdev_deferred_process().\n\nFix this by converting the notification chain to a raw notification\nchain in a similar fashion to the netdev notification chain. Protect\nthe chain using the RTNL mutex by acquiring it when modifying the chain.\nEvents are always informed under the RTNL mutex, but add an assertion in\ncall_switchdev_blocking_notifiers() to make sure this is not violated in\nthe future.\n\nMaintain the \u0026quot;blocking\u0026quot; prefix as events are always emitted from process\ncontext and listeners are allowed to block.\n\n[1]:\nWARNING: possible recursive locking detected\n6.14.0-rc4-custom-g079270089484 #1 Not tainted\n--------------------------------------------\nip/52731 is trying to acquire lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nbut task is already holding lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0\n----\nlock((switchdev_blocking_notif_chain).rwsem);\nlock((switchdev_blocking_notif_chain).rwsem);\n\n*** DEADLOCK ***\nMay be due to missing lock nesting notation\n3 locks held by ip/52731:\n #0: ffffffff84f795b0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x727/0x1dc0\n #1: ffffffff8731f628 (\u0026amp;net-\u0026gt;rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x790/0x1dc0\n #2: ffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nstack backtrace:\n...\n? __pfx_down_read+0x10/0x10\n? __pfx_mark_lock+0x10/0x10\n? __pfx_switchdev_port_attr_set_deferred+0x10/0x10\nblocking_notifier_call_chain+0x58/0xa0\nswitchdev_port_attr_notify.constprop.0+0xb3/0x1b0\n? __pfx_switchdev_port_attr_notify.constprop.0+0x10/0x10\n? mark_held_locks+0x94/0xe0\n? switchdev_deferred_process+0x11a/0x340\nswitchdev_port_attr_set_deferred+0x27/0xd0\nswitchdev_deferred_process+0x164/0x340\nbr_switchdev_port_unoffload+0xc8/0x100 [bridge]\nbr_switchdev_blocking_event+0x29f/0x580 [bridge]\nnotifier_call_chain+0xa2/0x440\nblocking_notifier_call_chain+0x6e/0xa0\nswitchdev_bridge_port_unoffload+0xde/0x1a0\n...(CVE-2025-21986)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix fence reference count leak\n\nThe last_scheduled fence leaks when an entity is being killed and adding\nthe cleanup callback fails.\n\nDecrement the reference count of prev when dma_fence_add_callback()\nfails, ensuring proper balance.\n\n[phasta: add git tag info for stable kernel](CVE-2025-21995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn\u0026apos;t have an integer wrapping bug.(CVE-2025-22001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: dummy: force synchronous probing\n\nSometimes I get a NULL pointer dereference at boot time in kobject_get()\nwith the following call stack:\n\nanatop_regulator_probe()\n devm_regulator_register()\n  regulator_register()\n   regulator_resolve_supply()\n    kobject_get()\n\nBy placing some extra BUG_ON() statements I could verify that this is\nraised because probing of the \u0026apos;dummy\u0026apos; regulator driver is not completed\n(\u0026apos;dummy_regulator_rdev\u0026apos; is still NULL).\n\nIn the JTAG debugger I can see that dummy_regulator_probe() and\nanatop_regulator_probe() can be run by different kernel threads\n(kworker/u4:*).  I haven\u0026apos;t further investigated whether this can be\nchanged or if there are other possibilities to force synchronization\nbetween these two probe routines.  On the other hand I don\u0026apos;t expect much\nboot time penalty by probing the \u0026apos;dummy\u0026apos; regulator synchronously.(CVE-2025-22009)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspufs: fix a leak in spufs_create_context()\n\nLeak fixes back in 2008 missed one case - if we are trying to set affinity\nand spufs_mkdir() fails, we need to drop the reference to neighbor.(CVE-2025-22071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;smb: client: fix TCP timers deadlock after rmmod\u0026quot;\n\nThis reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.\n\nCommit e9f2517a3e18 (\u0026quot;smb: client: fix TCP timers deadlock after\nrmmod\u0026quot;) is intended to fix a null-ptr-deref in LOCKDEP, which is\nmentioned as CVE-2024-54680, but is actually did not fix anything;\nThe issue can be reproduced on top of it. [0]\n\nAlso, it reverted the change by commit ef7134c7fc48 (\u0026quot;smb: client:\nFix use-after-free of network namespace.\u0026quot;) and introduced a real\nissue by reviving the kernel TCP socket.\n\nWhen a reconnect happens for a CIFS connection, the socket state\ntransitions to FIN_WAIT_1.  Then, inet_csk_clear_xmit_timers_sync()\nin tcp_close() stops all timers for the socket.\n\nIf an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1\nforever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.\n\nUsually, FIN can be retransmitted by the peer, but if the peer aborts\nthe connection, the issue comes into reality.\n\nI warned about this privately by pointing out the exact report [1],\nbut the bogus fix was finally merged.\n\nSo, we should not stop the timers to finally kill the connection on\nour side in that case, meaning we must not use a kernel socket for\nTCP whose sk-\u0026gt;sk_net_refcnt is 0.\n\nThe kernel socket does not have a reference to its netns to make it\npossible to tear down netns without cleaning up every resource in it.\n\nFor example, tunnel devices use a UDP socket internally, but we can\ndestroy netns without removing such devices and let it complete\nduring exit.  Otherwise, netns would be leaked when the last application\ndied.\n\nHowever, this is problematic for TCP sockets because TCP has timers to\nclose the connection gracefully even after the socket is close()d.  The\nlifetime of the socket and its netns is different from the lifetime of\nthe underlying connection.\n\nIf the socket user does not maintain the netns lifetime, the timer could\nbe fired after the socket is close()d and its netns is freed up, resulting\nin use-after-free.\n\nActually, we have seen so many similar issues and converted such sockets\nto have a reference to netns.\n\nThat\u0026apos;s why I converted the CIFS client socket to have a reference to\nnetns (sk-\u0026gt;sk_net_refcnt == 1), which is somehow mentioned as out-of-scope\nof CIFS and technically wrong in e9f2517a3e18, but **is in-scope and right\nfix**.\n\nRegarding the LOCKDEP issue, we can prevent the module unload by\nbumping the module refcount when switching the LOCKDDEP key in\nsock_lock_init_class_and_name(). [2]\n\nFor a while, let\u0026apos;s revert the bogus fix.\n\nNote that now we can use sk_net_refcnt_upgrade() for the socket\nconversion, but I\u0026apos;ll do so later separately to make backport easy.(CVE-2025-22077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: venus: hfi_parser: add check to avoid out of bound access\n\nThere is a possibility that init_codecs is invoked multiple times during\nmanipulated payload from video firmware. In such case, if codecs_count\ncan get incremented to value more than MAX_CODEC_NUM, there can be OOB\naccess. Reset the count so that it always starts from beginning.(CVE-2025-23157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.(CVE-2025-37740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.(CVE-2025-37748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix dangling pointer in krb_authenticate\n\nkrb_authenticate frees sess-\u0026gt;user and does not set the pointer\nto NULL. It calls ksmbd_krb5_authenticate to reinitialise\nsess-\u0026gt;user but that function may return without doing so. If\nthat happens then smb2_sess_setup, which calls krb_authenticate,\nwill be accessing free\u0026apos;d memory when it later uses sess-\u0026gt;user.(CVE-2025-37778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe()\n\ndevm_kasprintf() returns NULL when memory allocation fails. Currently,\navs_component_probe() does not check for this case, which results in a\nNULL pointer dereference.(CVE-2025-37793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsound/virtio: Fix cancel_sync warnings on uninitialized work_structs\n\nBetty reported hitting the following warning:\n\n[    8.709131][  T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182\n...\n[    8.713282][  T221] Call trace:\n[    8.713365][  T221]  __flush_work+0x8d0/0x914\n[    8.713468][  T221]  __cancel_work_sync+0xac/0xfc\n[    8.713570][  T221]  cancel_work_sync+0x24/0x34\n[    8.713667][  T221]  virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.713868][  T221]  virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.714035][  T221]  virtio_dev_probe+0x28c/0x390\n[    8.714139][  T221]  really_probe+0x1bc/0x4c8\n...\n\nIt seems we\u0026apos;re hitting the error path in virtsnd_probe(), which\ntriggers a virtsnd_remove() which iterates over the substreams\ncalling cancel_work_sync() on the elapsed_period work_struct.\n\nLooking at the code, from earlier in:\nvirtsnd_probe()-\u0026gt;virtsnd_build_devs()-\u0026gt;virtsnd_pcm_parse_cfg()\n\nWe set snd-\u0026gt;nsubstreams, allocate the snd-\u0026gt;substreams, and if\nwe then hit an error on the info allocation or something in\nvirtsnd_ctl_query_info() fails, we will exit without having\ninitialized the elapsed_period work_struct.\n\nWhen that error path unwinds we then call virtsnd_remove()\nwhich as long as the substreams array is allocated, will iterate\nthrough calling cancel_work_sync() on the uninitialized work\nstruct hitting this warning.\n\nTakashi Iwai suggested this fix, which initializes the substreams\nstructure right after allocation, so that if we hit the error\npaths we avoid trying to cleanup uninitialized data.\n\nNote: I have not yet managed to reproduce the issue myself, so\nthis patch has had limited testing.\n\nFeedback or thoughts would be appreciated!(CVE-2025-37805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where \u0026apos;generic_handle_irq\u0026apos; was\nreplaced with \u0026apos;handle_nested_irq\u0026apos;. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.(CVE-2025-37815)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy-\u0026gt;cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.(CVE-2025-37831)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: avoid NULL pointer dereference in dbg call\n\ncifs_server_dbg() implies server to be non-NULL so\nmove call under condition to avoid NULL pointer dereference.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37844)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: debugfs hang_hws skip GPU with MES\n\ndebugfs hang_hws is used by GPU reset test with HWS, for MES this crash\nthe kernel with NULL pointer access because dqm-\u0026gt;packet_mgr is not setup\nfor MES path.\n\nSkip GPU with MES for now, MES hang_hws debugfs interface will be\nsupported later.(CVE-2025-37853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d-\u0026gt;name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\u0026quot;ice: Fix some null pointer dereference issues in ice_ptp.c\u0026quot;).\n\nThis issue is found by our static analysis tool(CVE-2025-37881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Consistently treat platform_max as control value\n\nThis reverts commit 9bdd10d57a88 (\u0026quot;ASoC: ops: Shift tested values in\nsnd_soc_put_volsw() by +min\u0026quot;), and makes some additional related\nupdates.\n\nThere are two ways the platform_max could be interpreted; the maximum\nregister value, or the maximum value the control can be set to. The\npatch moved from treating the value as a control value to a register\none. When the patch was applied it was technically correct as\nsnd_soc_limit_volume() also used the register interpretation. However,\neven then most of the other usages treated platform_max as a\ncontrol value, and snd_soc_limit_volume() has since been updated to\nalso do so in commit fb9ad24485087 (\u0026quot;ASoC: ops: add correct range\ncheck for limiting volume\u0026quot;). That patch however, missed updating\nsnd_soc_put_volsw() back to the control interpretation, and fixing\nsnd_soc_info_volsw_range(). The control interpretation makes more\nsense as limiting is typically done from the machine driver, so it is\nappropriate to use the customer facing representation rather than the\ninternal codec representation. Update all the code to consistently use\nthis interpretation of platform_max.\n\nFinally, also add some comments to the soc_mixer_control struct to\nhopefully avoid further patches switching between the two approaches.(CVE-2025-37889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Balance device refcount when destroying devices\n\nUsing device_find_child() to lookup the proper SCMI device to destroy\ncauses an unbalance in device refcount, since device_find_child() calls an\nimplicit get_device(): this, in turns, inhibits the call of the provided\nrelease methods upon devices destruction.\n\nAs a consequence, one of the structures that is not freed properly upon\ndestruction is the internal struct device_private dev-\u0026gt;p populated by the\ndrivers subsystem core.\n\nKMemleak detects this situation since loading/unloding some SCMI driver\ncauses related devices to be created/destroyed without calling any\ndevice_release method.\n\nunreferenced object 0xffff00000f583800 (size 512):\n  comm \u0026quot;insmod\u0026quot;, pid 227, jiffies 4294912190\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 60 36 1d 8a 00 80 ff ff  ........`6......\n  backtrace (crc 114e2eed):\n    kmemleak_alloc+0xbc/0xd8\n    __kmalloc_cache_noprof+0x2dc/0x398\n    device_add+0x954/0x12d0\n    device_register+0x28/0x40\n    __scmi_device_create.part.0+0x1bc/0x380\n    scmi_device_create+0x2d0/0x390\n    scmi_create_protocol_devices+0x74/0xf8\n    scmi_device_request_notifier+0x1f8/0x2a8\n    notifier_call_chain+0x110/0x3b0\n    blocking_notifier_call_chain+0x70/0xb0\n    scmi_driver_register+0x350/0x7f0\n    0xffff80000a3b3038\n    do_one_initcall+0x12c/0x730\n    do_init_module+0x1dc/0x640\n    load_module+0x4b20/0x5b70\n    init_module_from_file+0xec/0x158\n\n$ ./scripts/faddr2line ./vmlinux device_add+0x954/0x12d0\ndevice_add+0x954/0x12d0:\nkmalloc_noprof at include/linux/slab.h:901\n(inlined by) kzalloc_noprof at include/linux/slab.h:1037\n(inlined by) device_private_init at drivers/base/core.c:3510\n(inlined by) device_add at drivers/base/core.c:3561\n\nBalance device refcount by issuing a put_device() on devices found via\ndevice_find_child().(CVE-2025-37905)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: avoid NULL pointer dereference in skb_dequeue()\n\nA NULL pointer dereference can occur in skb_dequeue() when processing a\nQCA firmware crash dump on WCN7851 (0489:e0f3).\n\n[ 93.672166] Bluetooth: hci0: ACL memdump size(589824)\n\n[ 93.672475] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[ 93.672517] Workqueue: hci0 hci_devcd_rx [bluetooth]\n[ 93.672598] RIP: 0010:skb_dequeue+0x50/0x80\n\nThe issue stems from handle_dump_pkt_qca() returning 0 even when a dump\npacket is successfully processed. This is because it incorrectly\nforwards the return value of hci_devcd_init() (which returns 0 on\nsuccess). As a result, the caller (btusb_recv_acl_qca() or\nbtusb_recv_evt_qca()) assumes the packet was not handled and passes it\nto hci_recv_frame(), leading to premature kfree() of the skb.\n\nLater, hci_devcd_rx() attempts to dequeue the same skb from the dump\nqueue, resulting in a NULL pointer dereference.\n\nFix this by:\n1. Making handle_dump_pkt_qca() return 0 on success and negative errno\n   on failure, consistent with kernel conventions.\n2. Splitting dump packet detection into separate functions for ACL\n   and event packets for better structure and readability.\n\nThis ensures dump packets are properly identified and consumed, avoiding\ndouble handling and preventing NULL pointer access.(CVE-2025-37918)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix deadlock\n\nThis patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock\nfunctions to the UCSI driver. ucsi_con_mutex_lock ensures the connector\nmutex is only locked if a connection is established and the partner pointer\nis valid. This resolves a deadlock scenario where\nucsi_displayport_remove_partner holds con-\u0026gt;mutex waiting for\ndp_altmode_work to complete while dp_altmode_work attempts to acquire it.(CVE-2025-37967)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Refactor remove call with idxd_cleanup() helper\n\nThe idxd_cleanup() helper cleans up perfmon, interrupts, internals and\nso on. Refactor remove call with the idxd_cleanup() helper to avoid code\nduplication. Note, this also fixes the missing put_device() for idxd\ngroups, enginces and wqs.(CVE-2025-38014)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Annotate FDB data races\n\nThe \u0026apos;used\u0026apos; and \u0026apos;updated\u0026apos; fields in the FDB entry structure can be\naccessed concurrently by multiple threads, leading to reports such as\n[1]. Can be reproduced using [2].\n\nSuppress these reports by annotating these accesses using\nREAD_ONCE() / WRITE_ONCE().\n\n[1]\nBUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit\n\nwrite to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0:\n vxlan_xmit+0xb29/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2:\n vxlan_xmit+0xadf/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nvalue changed: 0x00000000fffbac6e -\u0026gt; 0x00000000fffbac6f\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\n[2]\n #!/bin/bash\n\n set +H\n echo whitelist \u0026gt; /sys/kernel/debug/kcsan\n echo !vxlan_xmit \u0026gt; /sys/kernel/debug/kcsan\n\n ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1\n bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1\n taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;\n taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;(CVE-2025-38037)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Set dma_mask for ffa devices\n\nSet dma_mask for FFA devices, otherwise DMA allocation using the device pointer\nlead to following warning:\n\nWARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124(CVE-2025-38043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix use-after-free in cifs_fill_dirent\n\nThere is a race condition in the readdir concurrency process, which may\naccess the rsp buffer after it has been released, triggering the\nfollowing KASAN warning.\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs]\n Read of size 4 at addr ffff8880099b819c by task a.out/342975\n\n CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x53/0x70\n  print_report+0xce/0x640\n  kasan_report+0xb8/0xf0\n  cifs_fill_dirent+0xb03/0xb60 [cifs]\n  cifs_readdir+0x12cb/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f996f64b9f9\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89\n f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01\n f0 ff ff  0d f7 c3 0c 00 f7 d8 64 89 8\n RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e\n RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88\n R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 408:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  __kasan_slab_alloc+0x6e/0x70\n  kmem_cache_alloc_noprof+0x117/0x3d0\n  mempool_alloc_noprof+0xf2/0x2c0\n  cifs_buf_get+0x36/0x80 [cifs]\n  allocate_buffers+0x1d2/0x330 [cifs]\n  cifs_demultiplex_thread+0x22b/0x2690 [cifs]\n  kthread+0x394/0x720\n  ret_from_fork+0x34/0x70\n  ret_from_fork_asm+0x1a/0x30\n\n Freed by task 342979:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x37/0x50\n  kmem_cache_free+0x2b8/0x500\n  cifs_buf_release+0x3c/0x70 [cifs]\n  cifs_readdir+0x1c97/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents64+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n The buggy address belongs to the object at ffff8880099b8000\n  which belongs to the cache cifs_request of size 16588\n The buggy address is located 412 bytes inside of\n  freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8\n head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n anon flags: 0x80000000000040(head|node=0|zone=1)\n page_type: f5(slab)\n raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff\n head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n \u0026gt;ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                             ^\n  ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ==================================================================\n\nPOC is available in the link [1].\n\nThe problem triggering process is as follows:\n\nProcess 1                       Process 2\n-----------------------------------\n---truncated---(CVE-2025-38051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n\tInvalid read at addr 0x102877002, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\tInvalid write at addr 0x102877A44, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\t...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.(CVE-2025-38064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: CPPC: Fix NULL pointer dereference when nosmp is used\n\nWith nosmp in cmdline, other CPUs are not brought up, leaving\ntheir cpc_desc_ptr NULL. CPU0\u0026apos;s iteration via for_each_possible_cpu()\ndereferences these NULL pointers, causing panic.\n\nPanic backtrace:\n\n[    0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8\n...\n[    0.403255] [\u0026lt;ffffffff809a5818\u0026gt;] cppc_allow_fast_switch+0x6a/0xd4\n...\nKernel panic - not syncing: Attempted to kill init!\n\n[ rjw: New subject ](CVE-2025-38113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: add missing NULL check for gve_alloc_pending_packet() in TX DQO\n\ngve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()\ndid not check for this case before dereferencing the returned pointer.\n\nAdd a missing NULL check to prevent a potential NULL pointer\ndereference when allocation fails.\n\nThis improves robustness in low-memory scenarios.(CVE-2025-38122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: wwan: t7xx: Fix napi rx poll issue\n\nWhen driver handles the napi rx polling requests, the netdev might\nhave been released by the dellink logic triggered by the disconnect\noperation on user plane. However, in the logic of processing skb in\npolling, an invalid netdev is still being used, which causes a panic.\n\nBUG: kernel NULL pointer dereference, address: 00000000000000f1\nOops: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:dev_gro_receive+0x3a/0x620\n[...]\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die_body+0x68/0xb0\n ? page_fault_oops+0x379/0x3e0\n ? exc_page_fault+0x4f/0xa0\n ? asm_exc_page_fault+0x22/0x30\n ? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]\n ? dev_gro_receive+0x3a/0x620\n napi_gro_receive+0xad/0x170\n t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]\n t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]\n net_rx_action+0x103/0x470\n irq_exit_rcu+0x13a/0x310\n sysvec_apic_timer_interrupt+0x56/0x90\n \u0026lt;/IRQ\u0026gt;(CVE-2025-38123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: prevent deactivate active config while enabling the config\n\nWhile enable active config via cscfg_csdev_enable_active_config(),\nactive config could be deactivated via configfs\u0026apos; sysfs interface.\nThis could make UAF issue in below scenario:\n\nCPU0                                          CPU1\n(sysfs enable)                                load module\n                                              cscfg_load_config_sets()\n                                              activate config. // sysfs\n                                              (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\nlock(csdev-\u0026gt;cscfg_csdev_lock)\n// here load config activate by CPU1\nunlock(csdev-\u0026gt;cscfg_csdev_lock)\n\n                                              deactivate config // sysfs\n                                              (sys_activec_cnt == 0)\n                                              cscfg_unload_config_sets()\n                                              unload module\n\n// access to config_desc which freed\n// while unloading module.\ncscfg_csdev_enable_config\n\nTo address this, use cscfg_config_desc\u0026apos;s active_cnt as a reference count\n which will be holded when\n    - activate the config.\n    - enable the activated config.\nand put the module reference when config_active_cnt == 0.(CVE-2025-38131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: mscc: Fix memory leak when using one step timestamping\n\nFix memory leak when running one-step timestamping. When running\none-step sync timestamping, the HW is configured to insert the TX time\ninto the frame, so there is no reason to keep the skb anymore. As in\nthis case the HW will never generate an interrupt to say that the frame\nwas timestamped, then the frame will never released.\nFix this by freeing the frame in case of one-step timestamping.(CVE-2025-38148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix error flow upon firmware failure for RQ destruction\n\nUpon RQ destruction if the firmware command fails which is the\nlast resource to be destroyed some SW resources were already cleaned\nregardless of the failure.\n\nNow properly rollback the object to its original state upon such failure.\n\nIn order to avoid a use-after free in case someone tries to destroy the\nobject again, which results in the following kernel trace:\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE)\nCPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G           OE     -------  ---  6.12.0-54.el10.aarch64 #1\nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\nHardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : refcount_warn_saturate+0xf4/0x148\nlr : refcount_warn_saturate+0xf4/0x148\nsp : ffff80008b81b7e0\nx29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001\nx26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00\nx23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000\nx20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006\nx17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f\nx14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78\nx11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90\nx8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff\nx5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600\nCall trace:\n refcount_warn_saturate+0xf4/0x148\n mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib]\n mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib]\n mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib]\n ib_destroy_wq_user+0x30/0xc0 [ib_core]\n uverbs_free_wq+0x28/0x58 [ib_uverbs]\n destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs]\n uverbs_destroy_uobject+0x48/0x240 [ib_uverbs]\n __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs]\n uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs]\n ib_uverbs_close+0x2c/0x100 [ib_uverbs]\n __fput+0xd8/0x2f0\n __fput_sync+0x50/0x70\n __arm64_sys_close+0x40/0x90\n invoke_syscall.constprop.0+0x74/0xd0\n do_el0_svc+0x48/0xe8\n el0_svc+0x44/0x1d0\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x1a4/0x1a8(CVE-2025-38161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()\n\nBefore calling lan743x_ptp_io_event_clock_get(), the \u0026apos;channel\u0026apos; value\nis checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8).\nThis seems correct and aligns with the PTP interrupt status register\n(PTP_INT_STS) specifications.\n\nHowever, lan743x_ptp_io_event_clock_get() writes to ptp-\u0026gt;extts[] with\nonly LAN743X_PTP_N_EXTTS(4) elements, using channel as an index:\n\n    lan743x_ptp_io_event_clock_get(..., u8 channel,...)\n    {\n        ...\n        /* Update Local timestamp */\n        extts = \u0026amp;ptp-\u0026gt;extts[channel];\n        extts-\u0026gt;ts.tv_sec = sec;\n        ...\n    }\n\nTo avoid an out-of-bounds write and utilize all the supported GPIO\ninputs, set LAN743X_PTP_N_EXTTS to 8.\n\nDetected using the static analysis tool - Svace.(CVE-2025-38183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: sch_sfq: reject invalid perturb period\n\nGerrard Tai reported that SFQ perturb_period has no range check yet,\nand this can be used to trigger a race condition fixed in a separate patch.\n\nWe want to make sure ctl-\u0026gt;perturb_period * HZ will not overflow\nand is positive.\n\n\ntc qd add dev lo root sfq perturb -10   # negative value : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 1000000000 # too big : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 2000000 # acceptable value\ntc -s -d qd sh dev lo\nqdisc sfq 8005: root refcnt 2 limit 127p quantum 64Kb depth 127 flows 128 divisor 1024 perturb 2000000sec\n Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)\n backlog 0b 0p requeues 0(CVE-2025-38193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njffs2: check that raw node were preallocated before writing summary\n\nSyzkaller detected a kernel bug in jffs2_link_node_ref, caused by fault\ninjection in jffs2_prealloc_raw_node_refs. jffs2_sum_write_sumnode doesn\u0026apos;t\ncheck return value of jffs2_prealloc_raw_node_refs and simply lets any\nerror propagate into jffs2_sum_write_data, which eventually calls\njffs2_link_node_ref in order to link the summary to an expectedly allocated\nnode.\n\nkernel BUG at fs/jffs2/nodelist.c:592!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 31277 Comm: syz-executor.7 Not tainted 6.1.128-syzkaller-00139-ge10f83ca10a1 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:jffs2_link_node_ref+0x570/0x690 fs/jffs2/nodelist.c:592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n jffs2_sum_write_data fs/jffs2/summary.c:841 [inline]\n jffs2_sum_write_sumnode+0xd1a/0x1da0 fs/jffs2/summary.c:874\n jffs2_do_reserve_space+0xa18/0xd60 fs/jffs2/nodemgmt.c:388\n jffs2_reserve_space+0x55f/0xaa0 fs/jffs2/nodemgmt.c:197\n jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362\n jffs2_write_end+0x726/0x15d0 fs/jffs2/file.c:301\n generic_perform_write+0x314/0x5d0 mm/filemap.c:3856\n __generic_file_write_iter+0x2ae/0x4d0 mm/filemap.c:3973\n generic_file_write_iter+0xe3/0x350 mm/filemap.c:4005\n call_write_iter include/linux/fs.h:2265 [inline]\n do_iter_readv_writev+0x20f/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10c/0x170 fs/splice.c:950\n splice_direct_to_actor+0x337/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nFix this issue by checking return value of jffs2_prealloc_raw_node_refs\nbefore calling jffs2_sum_write_data.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-38194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix softlockup with mTHP swapin\n\nFollowing softlockup can be easily reproduced on my test machine with:\n\necho always \u0026gt; /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled\nswapon /dev/zram0 # zram0 is a 48G swap device\nmkdir -p /sys/fs/cgroup/memory/test\necho 1G \u0026gt; /sys/fs/cgroup/test/memory.max\necho $BASHPID \u0026gt; /sys/fs/cgroup/test/cgroup.procs\nwhile true; do\n    dd if=/dev/zero of=/tmp/test.img bs=1M count=5120\n    cat /tmp/test.img \u0026gt; /dev/null\n    rm /tmp/test.img\ndone\n\nThen after a while:\nwatchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787]\nModules linked in: zram virtiofs\nCPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G             L      6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)·\nTainted: [L]=SOFTLOCKUP\nHardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015\nRIP: 0010:mpol_shared_policy_lookup+0xd/0x70\nCode: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 \u0026lt;48\u0026gt; 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8\nRSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202\nRAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001\nRDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518\nRBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001\nR13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000\nFS:  00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n shmem_alloc_folio+0x31/0xc0\n shmem_swapin_folio+0x309/0xcf0\n ? filemap_get_entry+0x117/0x1e0\n ? xas_load+0xd/0xb0\n ? filemap_get_entry+0x101/0x1e0\n shmem_get_folio_gfp+0x2ed/0x5b0\n shmem_file_read_iter+0x7f/0x2e0\n vfs_read+0x252/0x330\n ksys_read+0x68/0xf0\n do_syscall_64+0x4c/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f03f9a46991\nCode: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec\nRSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991\nRDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003\nRBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380\nR10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000\nR13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\n\nThe reason is simple, readahead brought some order 0 folio in swap cache,\nand the swapin mTHP folio being allocated is in conflict with it, so\nswapcache_prepare fails and causes shmem_swap_alloc_folio to return\n-EEXIST, and shmem simply retries again and again causing this loop.\n\nFix it by applying a similar fix for anon mTHP swapin.\n\nThe performance change is very slight, time of swapin 10g zero folios\nwith shmem (test for 12 times):\nBefore:  2.47s\nAfter:   2.48s\n\n[(CVE-2025-38241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/group_cpus: fix NULL pointer dereference from group_cpus_evenly()\n\nWhile testing null_blk with configfs, echo 0 \u0026gt; poll_queues will trigger\nfollowing panic:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000010\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 27 UID: 0 PID: 920 Comm: bash Not tainted 6.15.0-02023-gadbdb95c8696-dirty #1238 PREEMPT(undef)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\nRIP: 0010:__bitmap_or+0x48/0x70\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __group_cpus_evenly+0x822/0x8c0\n group_cpus_evenly+0x2d9/0x490\n blk_mq_map_queues+0x1e/0x110\n null_map_queues+0xc9/0x170 [null_blk]\n blk_mq_update_queue_map+0xdb/0x160\n blk_mq_update_nr_hw_queues+0x22b/0x560\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_poll_queues_store+0xa4/0x130 [null_blk]\n configfs_write_iter+0x109/0x1d0\n vfs_write+0x26e/0x6f0\n ksys_write+0x79/0x180\n __x64_sys_write+0x1d/0x30\n x64_sys_call+0x45c4/0x45f0\n do_syscall_64+0xa5/0x240\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nRoot cause is that numgrps is set to 0, and ZERO_SIZE_PTR is returned from\nkcalloc(), and later ZERO_SIZE_PTR will be deferenced.\n\nFix the problem by checking numgrps first in group_cpus_evenly(), and\nreturn NULL directly if numgrps is zero.\n\n[(CVE-2025-38255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix NULL pointer deference on eir_get_service_data\n\nThe len parameter is considered optional so it can be NULL so it cannot\nbe used for skipping to next entry of EIR_SERVICE_DATA.(CVE-2025-38304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Verify content returned by parse_int_array()\n\nThe first element of the returned array stores its length. If it is 0,\nany manipulation beyond the element at index 0 ends with null-ptr-deref.(CVE-2025-38307)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Log an error when close_all_cached_dirs fails\n\nUnder low-memory conditions, close_all_cached_dirs() can\u0026apos;t move the\ndentries to a separate list to dput() them once the locks are dropped.\nThis will result in a \u0026quot;Dentry still in use\u0026quot; error, so add an error\nmessage that makes it clear this is what happened:\n\n[  495.281119] CIFS: VFS: \\\\otters.example.com\\share Out of memory while dropping dentries\n[  495.281595] ------------[ cut here ]------------\n[  495.281887] BUG: Dentry ffff888115531138{i=78,n=/}  still in use (2) [unmount of cifs cifs]\n[  495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0\n\nAlso, bail out of looping through all tcons as soon as a single\nallocation fails, since we\u0026apos;re already in trouble, and kmalloc() attempts\nfor subseqeuent tcons are likely to fail just like the first one did.(CVE-2025-38321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: fix acpi parse and parseext cache leaks\n\nACPICA commit 8829e70e1360c81e7a5a901b5d4f48330e021ea5\n\nI\u0026apos;m Seunghun Han, and I work for National Security Research Institute of\nSouth Korea.\n\nI have been doing a research on ACPI and found an ACPI cache leak in ACPI\nearly abort cases.\n\nBoot log of ACPI cache leak is as follows:\n[    0.352414] ACPI: Added _OSI(Module Device)\n[    0.353182] ACPI: Added _OSI(Processor Device)\n[    0.353182] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.353182] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.356028] ACPI: Unable to start the ACPI Interpreter\n[    0.356799] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.360215] kmem_cache_destroy Acpi-State: Slab cache still has objects\n[    0.360648] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #10\n[    0.361273] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.361873] Call Trace:\n[    0.362243]  ? dump_stack+0x5c/0x81\n[    0.362591]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.362944]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.363296]  ? acpi_os_delete_cache+0xa/0x10\n[    0.363646]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.364000]  ? acpi_terminate+0xa/0x14\n[    0.364000]  ? acpi_init+0x2af/0x34f\n[    0.364000]  ? __class_create+0x4c/0x80\n[    0.364000]  ? video_setup+0x7f/0x7f\n[    0.364000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.364000]  ? do_one_initcall+0x4e/0x1a0\n[    0.364000]  ? kernel_init_freeable+0x189/0x20a\n[    0.364000]  ? rest_init+0xc0/0xc0\n[    0.364000]  ? kernel_init+0xa/0x100\n[    0.364000]  ? ret_from_fork+0x25/0x30\n\nI analyzed this memory leak in detail. I found that “Acpi-State” cache and\n“Acpi-Parse” cache were merged because the size of cache objects was same\nslab cache size.\n\nI finally found “Acpi-Parse” cache and “Acpi-parse_ext” cache were leaked\nusing SLAB_NEVER_MERGE flag in kmem_cache_create() function.\n\nReal ACPI cache leak point is as follows:\n[    0.360101] ACPI: Added _OSI(Module Device)\n[    0.360101] ACPI: Added _OSI(Processor Device)\n[    0.360101] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.361043] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.364016] ACPI: Unable to start the ACPI Interpreter\n[    0.365061] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.368174] kmem_cache_destroy Acpi-Parse: Slab cache still has objects\n[    0.369332] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.371256] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.372000] Call Trace:\n[    0.372000]  ? dump_stack+0x5c/0x81\n[    0.372000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.372000]  ? acpi_ut_delete_caches+0x56/0x7b\n[    0.372000]  ? acpi_terminate+0xa/0x14\n[    0.372000]  ? acpi_init+0x2af/0x34f\n[    0.372000]  ? __class_create+0x4c/0x80\n[    0.372000]  ? video_setup+0x7f/0x7f\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? do_one_initcall+0x4e/0x1a0\n[    0.372000]  ? kernel_init_freeable+0x189/0x20a\n[    0.372000]  ? rest_init+0xc0/0xc0\n[    0.372000]  ? kernel_init+0xa/0x100\n[    0.372000]  ? ret_from_fork+0x25/0x30\n[    0.388039] kmem_cache_destroy Acpi-parse_ext: Slab cache still has objects\n[    0.389063] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.390557] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.392000] Call Trace:\n[    0.392000]  ? dump_stack+0x5c/0x81\n[    0.392000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.392000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.392000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.392000]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.392000]  ? acpi_terminate+0xa/0x14\n[    0.392000]  ? acpi_init+0x2af/0x3\n---truncated---(CVE-2025-38344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmaple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()\n\nTemporarily clear the preallocation flag when explicitly requesting\nallocations.  Pre-existing allocations are already counted against the\nrequest through mas_node_count_gfp(), but the allocations will not happen\nif the MA_STATE_PREALLOC flag is set.  This flag is meant to avoid\nre-allocating in bulk allocation mode, and to detect issues with\npreallocation calculations.\n\nThe MA_STATE_PREALLOC flag should also always be set on zero allocations\nso that detection of underflow allocations will print a WARN_ON() during\nconsumption.\n\nUser visible effect of this flaw is a WARN_ON() followed by a null pointer\ndereference when subsequent requests for larger number of nodes is\nignored, such as the vma merge retry in mmap_region() caused by drivers\naltering the vma flags (which happens in v6.6, at least)(CVE-2025-38364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_* TOCTOU\n\nTransport assignment may race with module unload. Protect new_transport\nfrom becoming a stale pointer.\n\nThis also takes care of an insecure call in vsock_use_local_transport();\nadd a lockdep assert.\n\nBUG: unable to handle page fault for address: fffffbfff8056000\nOops: Oops: 0000 [#1] SMP KASAN\nRIP: 0010:vsock_assign_transport+0x366/0x600\nCall Trace:\n vsock_connect+0x59c/0xc40\n __sys_connect+0xe8/0x100\n __x64_sys_connect+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38461)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_{g2h,h2g} TOCTOU\n\nvsock_find_cid() and vsock_dev_do_ioctl() may race with module unload.\ntransport_{g2h,h2g} may become NULL after the NULL check.\n\nIntroduce vsock_transport_local_cid() to protect from a potential\nnull-ptr-deref.\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_find_cid+0x47/0x90\nCall Trace:\n __vsock_bind+0x4b2/0x720\n vsock_bind+0x90/0xe0\n __sys_bind+0x14d/0x1e0\n __x64_sys_bind+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0\nCall Trace:\n __x64_sys_ioctl+0x12d/0x190\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38462)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in crypt_message when using async crypto\n\nThe CVE-2024-50047 fix removed asynchronous crypto handling from\ncrypt_message(), assuming all crypto operations are synchronous.\nHowever, when hardware crypto accelerators are used, this can cause\nuse-after-free crashes:\n\n  crypt_message()\n    // Allocate the creq buffer containing the req\n    creq = smb2_get_aead_req(..., \u0026amp;req);\n\n    // Async encryption returns -EINPROGRESS immediately\n    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);\n\n    // Free creq while async operation is still in progress\n    kvfree_sensitive(creq, ...);\n\nHardware crypto modules often implement async AEAD operations for\nperformance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,\nthe operation completes asynchronously. Without crypto_wait_req(),\nthe function immediately frees the request buffer, leading to crashes\nwhen the driver later accesses the freed memory.\n\nThis results in a use-after-free condition when the hardware crypto\ndriver later accesses the freed request structure, leading to kernel\ncrashes with NULL pointer dereferences.\n\nThe issue occurs because crypto_alloc_aead() with mask=0 doesn\u0026apos;t\nguarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in\nthe mask, async implementations can be selected.\n\nFix by restoring the async crypto handling:\n- DECLARE_CRYPTO_WAIT(wait) for completion tracking\n- aead_request_set_callback() for async completion notification\n- crypto_wait_req() to wait for operation completion\n\nThis ensures the request buffer isn\u0026apos;t freed until the crypto operation\ncompletes, whether synchronous or asynchronous, while preserving the\nCVE-2024-50047 fix.(CVE-2025-38488)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns\n\nWhat we want is to verify there is that clone won\u0026apos;t expose something\nhidden by a mount we wouldn\u0026apos;t be able to undo.  \u0026quot;Wouldn\u0026apos;t be able to undo\u0026quot;\nmay be a result of MNT_LOCKED on a child, but it may also come from\nlacking admin rights in the userns of the namespace mount belongs to.\n\nclone_private_mnt() checks the former, but not the latter.\n\nThere\u0026apos;s a number of rather confusing CAP_SYS_ADMIN checks in various\nuserns during the mount, especially with the new mount API; they serve\ndifferent purposes and in case of clone_private_mnt() they usually,\nbut not always end up covering the missing check mentioned above.(CVE-2025-38499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n\u0026apos;socket state prevent any additional subflow creation\u0026apos; protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field \u0026apos;allow_infinite_fallback\u0026apos; is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write.(CVE-2025-38552)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: use aead_request_free to match aead_request_alloc\n\nUse aead_request_free() instead of kfree() to properly free memory\nallocated by aead_request_alloc(). This ensures sensitive crypto data\nis zeroed before being freed.(CVE-2025-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Check governor before using governor-\u0026gt;name\n\nCommit 96ffcdf239de (\u0026quot;PM / devfreq: Remove redundant governor_name from\nstruct devfreq\u0026quot;) removes governor_name and uses governor-\u0026gt;name to replace\nit. But devfreq-\u0026gt;governor may be NULL and directly using\ndevfreq-\u0026gt;governor-\u0026gt;name may cause null pointer exception. Move the check of\ngovernor to before using governor-\u0026gt;name.(CVE-2025-38609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: fix refcount leak on table dump\n\nThere is a reference count leak in ctnetlink_dump_table():\n      if (res \u0026lt; 0) {\n                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general); // HERE\n                cb-\u0026gt;args[1] = (unsigned long)ct;\n                ...\n\nWhile its very unlikely, its possible that ct == last.\nIf this happens, then the refcount of ct was already incremented.\nThis 2nd increment is never undone.\n\nThis prevents the conntrack object from being released, which in turn\nkeeps prevents cnet-\u0026gt;count from dropping back to 0.\n\nThis will then block the netns dismantle (or conntrack rmmod) as\nnf_conntrack_cleanup_net_list() will wait forever.\n\nThis can be reproduced by running conntrack_resize.sh selftest in a loop.\nIt takes ~20 minutes for me on a preemptible kernel on average before\nI see a runaway kworker spinning in nf_conntrack_cleanup_net_list.\n\nOne fix would to change this to:\n        if (res \u0026lt; 0) {\n\t\tif (ct != last)\n\t                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general);\n\nBut this reference counting isn\u0026apos;t needed in the first place.\nWe can just store a cookie value instead.\n\nA followup patch will do the same for ctnetlink_exp_dump_table,\nit looks to me as if this has the same problem and like\nctnetlink_dump_table, we only need a \u0026apos;skip hint\u0026apos;, not the actual\nobject so we can apply the same cookie strategy there as well.(CVE-2025-38721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don\u0026apos;t know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don\u0026apos;t have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it\u0026apos;s\nzero length.(CVE-2025-39682)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: samsung: Fix UBSAN panic in samsung_clk_init()\n\nWith UBSAN_ARRAY_BOUNDS=y, I\u0026apos;m hitting the below panic due to\ndereferencing `ctx-\u0026gt;clk_data.hws` before setting\n`ctx-\u0026gt;clk_data.num = nr_clks`. Move that up to fix the crash.\n\n  UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n  \u0026lt;snip\u0026gt;\n  Call trace:\n   samsung_clk_init+0x110/0x124 (P)\n   samsung_clk_init+0x48/0x124 (L)\n   samsung_cmu_register_one+0x3c/0xa0\n   exynos_arm64_register_cmu+0x54/0x64\n   __gs101_cmu_top_of_clk_init_declare+0x28/0x60\n   ...(CVE-2025-39728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: Prevent file descriptor table allocations exceeding INT_MAX\n\nWhen sysctl_nr_open is set to a very high value (for example, 1073741816\nas set by systemd), processes attempting to use file descriptors near\nthe limit can trigger massive memory allocation attempts that exceed\nINT_MAX, resulting in a WARNING in mm/slub.c:\n\n  WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288\n\nThis happens because kvmalloc_array() and kvmalloc() check if the\nrequested size exceeds INT_MAX and emit a warning when the allocation is\nnot flagged with __GFP_NOWARN.\n\nSpecifically, when nr_open is set to 1073741816 (0x3ffffff8) and a\nprocess calls dup2(oldfd, 1073741880), the kernel attempts to allocate:\n- File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes\n- Multiple bitmaps: ~400MB\n- Total allocation size: \u0026gt; 8GB (exceeding INT_MAX = 2,147,483,647)\n\nReproducer:\n1. Set /proc/sys/fs/nr_open to 1073741816:\n   # echo 1073741816 \u0026gt; /proc/sys/fs/nr_open\n\n2. Run a program that uses a high file descriptor:\n   #include \u0026lt;unistd.h\u0026gt;\n   #include \u0026lt;sys/resource.h\u0026gt;\n\n   int main() {\n       struct rlimit rlim = {1073741824, 1073741824};\n       setrlimit(RLIMIT_NOFILE, \u0026amp;rlim);\n       dup2(2, 1073741880);  // Triggers the warning\n       return 0;\n   }\n\n3. Observe WARNING in dmesg at mm/slub.c:5027\n\nsystemd commit a8b627a introduced automatic bumping of fs.nr_open to the\nmaximum possible value. The rationale was that systems with memory\ncontrol groups (memcg) no longer need separate file descriptor limits\nsince memory is properly accounted. However, this change overlooked\nthat:\n\n1. The kernel\u0026apos;s allocation functions still enforce INT_MAX as a maximum\n   size regardless of memcg accounting\n2. Programs and tests that legitimately test file descriptor limits can\n   inadvertently trigger massive allocations\n3. The resulting allocations (\u0026gt;8GB) are impractical and will always fail\n\nsystemd\u0026apos;s algorithm starts with INT_MAX and keeps halving the value\nuntil the kernel accepts it. On most systems, this results in nr_open\nbeing set to 1073741816 (0x3ffffff8), which is just under 1GB of file\ndescriptors.\n\nWhile processes rarely use file descriptors near this limit in normal\noperation, certain selftests (like\ntools/testing/selftests/core/unshare_test.c) and programs that test file\ndescriptor limits can trigger this issue.\n\nFix this by adding a check in alloc_fdtable() to ensure the requested\nallocation size does not exceed INT_MAX. This causes the operation to\nfail with -EMFILE instead of triggering a kernel warning and avoids the\nimpractical \u0026gt;8GB memory allocation request.(CVE-2025-39756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM\n\nWhen performing Generic Segmentation Offload (GSO) on an IPv6 packet that\ncontains extension headers, the kernel incorrectly requests checksum offload\nif the egress device only advertises NETIF_F_IPV6_CSUM feature, which has\na strict contract: it supports checksum offload only for plain TCP or UDP\nover IPv6 and explicitly does not support packets with extension headers.\nThe current GSO logic violates this contract by failing to disable the feature\nfor packets with extension headers, such as those used in GREoIPv6 tunnels.\n\nThis violation results in the device being asked to perform an operation\nit cannot support, leading to a `skb_warn_bad_offload` warning and a collapse\nof network throughput. While device TSO/USO is correctly bypassed in favor\nof software GSO for these packets, the GSO stack must be explicitly told not\nto request checksum offload.\n\nMask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4\nin gso_features_check if the IPv6 header contains extension headers to compute\nchecksum in software.\n\nThe exception is a BIG TCP extension, which, as stated in commit\n68e068cabd2c6c53 (\u0026quot;net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\u0026quot;):\n\u0026quot;The feature is only enabled on devices that support BIG TCP TSO.\nThe header is only present for PF_PACKET taps like tcpdump,\nand not transmitted by physical devices.\u0026quot;\n\nkernel log output (truncated):\nWARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_checksum_help+0x12a/0x1f0\n validate_xmit_skb+0x1a3/0x2d0\n validate_xmit_skb_list+0x4f/0x80\n sch_direct_xmit+0x1a2/0x380\n __dev_xmit_skb+0x242/0x670\n __dev_queue_xmit+0x3fc/0x7f0\n ip6_finish_output2+0x25e/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]\n ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]\n dev_hard_start_xmit+0x63/0x1c0\n __dev_queue_xmit+0x6d0/0x7f0\n ip6_finish_output2+0x214/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n inet6_csk_xmit+0xeb/0x150\n __tcp_transmit_skb+0x555/0xa80\n tcp_write_xmit+0x32a/0xe90\n tcp_sendmsg_locked+0x437/0x1110\n tcp_sendmsg+0x2f/0x50\n...\nskb linear:   00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e\nskb linear:   00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00\nskb linear:   00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00\nskb linear:   00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00\nskb linear:   00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9\nskb linear:   00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01\nskb linear:   00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a(CVE-2025-39770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: initialize more fields in sctp_v6_from_sk()\n\nsyzbot found that sin6_scope_id was not properly initialized,\nleading to undefined behavior.\n\nClear sin6_scope_id and sin6_flowinfo.\n\nBUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983\n  sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390\n  sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452\n  sctp_get_port net/sctp/socket.c:8523 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n  x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nLocal variable addr.i.i created at:\n  sctp_get_port net/sctp/socket.c:8515 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930(CVE-2025-39812)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix buffer free/clear order in deferred receive path\n\nFix a use-after-free window by correcting the buffer release sequence in\nthe deferred receive path. The code freed the RQ buffer first and only\nthen cleared the context pointer under the lock. Concurrent paths (e.g.,\nABTS and the repost path) also inspect and release the same pointer under\nthe lock, so the old order could lead to double-free/UAF.\n\nNote that the repost path already uses the correct pattern: detach the\npointer under the lock, then free it after dropping the lock. The\ndeferred path should do the same.(CVE-2025-39841)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm\n\nWhen send a broadcast packet to a tap device, which was added to a bridge,\nbr_nf_local_in() is called to confirm the conntrack. If another conntrack\nwith the same hash value is added to the hash table, which can be\ntriggered by a normal packet to a non-bridge device, the below warning\nmay happen.\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 96 at net/bridge/br_netfilter_hooks.c:632 br_nf_local_in+0x168/0x200\n  CPU: 1 UID: 0 PID: 96 Comm: tap_send Not tainted 6.17.0-rc2-dirty #44 PREEMPT(voluntary)\n  RIP: 0010:br_nf_local_in+0x168/0x200\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   nf_hook_slow+0x3e/0xf0\n   br_pass_frame_up+0x103/0x180\n   br_handle_frame_finish+0x2de/0x5b0\n   br_nf_hook_thresh+0xc0/0x120\n   br_nf_pre_routing_finish+0x168/0x3a0\n   br_nf_pre_routing+0x237/0x5e0\n   br_handle_frame+0x1ec/0x3c0\n   __netif_receive_skb_core+0x225/0x1210\n   __netif_receive_skb_one_core+0x37/0xa0\n   netif_receive_skb+0x36/0x160\n   tun_get_user+0xa54/0x10c0\n   tun_chr_write_iter+0x65/0xb0\n   vfs_write+0x305/0x410\n   ksys_write+0x60/0xd0\n   do_syscall_64+0xa4/0x260\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nTo solve the hash conflict, nf_ct_resolve_clash() try to merge the\nconntracks, and update skb-\u0026gt;_nfct. However, br_nf_local_in() still use the\nold ct from local variable \u0026apos;nfct\u0026apos; after confirm(), which leads to this\nwarning.\n\nIf confirm() does not insert the conntrack entry and return NF_DROP, the\nwarning may also occur. There is no need to reserve the WARN_ON_ONCE, just\nremove it.(CVE-2025-39894)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer\n\nSince commit 7d5e9737efda (\u0026quot;net: rfkill: gpio: get the name and type from\ndevice property\u0026quot;) rfkill_find_type() gets called with the possibly\nuninitialized \u0026quot;const char *type_name;\u0026quot; local variable.\n\nOn x86 systems when rfkill-gpio binds to a \u0026quot;BCM4752\u0026quot; or \u0026quot;LNV4752\u0026quot;\nacpi_device, the rfkill-\u0026gt;type is set based on the ACPI acpi_device_id:\n\n        rfkill-\u0026gt;type = (unsigned)id-\u0026gt;driver_data;\n\nand there is no \u0026quot;type\u0026quot; property so device_property_read_string() will fail\nand leave type_name uninitialized, leading to a potential crash.\n\nrfkill_find_type() does accept a NULL pointer, fix the potential crash\nby initializing type_name to NULL.\n\nNote likely sofar this has not been caught because:\n\n1. Not many x86 machines actually have a \u0026quot;BCM4752\u0026quot;/\u0026quot;LNV4752\u0026quot; acpi_device\n2. The stack happened to contain NULL where type_name is stored(CVE-2025-39937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Clear tcp_sk(sk)-\u0026gt;fastopen_rsk in tcp_disconnect().\n\nsyzbot reported the splat below where a socket had tcp_sk(sk)-\u0026gt;fastopen_rsk\nin the TCP_ESTABLISHED state. [0]\n\nsyzbot reused the server-side TCP Fast Open socket as a new client before\nthe TFO socket completes 3WHS:\n\n  1. accept()\n  2. connect(AF_UNSPEC)\n  3. connect() to another destination\n\nAs of accept(), sk-\u0026gt;sk_state is TCP_SYN_RECV, and tcp_disconnect() changes\nit to TCP_CLOSE and makes connect() possible, which restarts timers.\n\nSince tcp_disconnect() forgot to clear tcp_sk(sk)-\u0026gt;fastopen_rsk, the\nretransmit timer triggered the warning and the intended packet was not\nretransmitted.\n\nLet\u0026apos;s call reqsk_fastopen_remove() in tcp_disconnect().\n\n[0]:\nWARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nModules linked in:\nCPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nCode: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 \u0026lt;0f\u0026gt; 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e\nRSP: 0018:ffffc900002f8d40 EFLAGS: 00010293\nRAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017\nRDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400\nRBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8\nR10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540\nR13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0\nFS:  0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_write_timer (net/ipv4/tcp_timer.c:738)\n call_timer_fn (kernel/time/timer.c:1747)\n __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372)\n timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135)\n tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035)\n __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1))\n tmigr_handle_remote (kernel/time/timer_migration.c:1096)\n handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580)\n irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39955)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-39980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - set NULL to qm-\u0026gt;debug.qm_diff_regs\n\nWhen the initialization of qm-\u0026gt;debug.acc_diff_reg fails,\nthe probe process does not exit. However, after qm-\u0026gt;debug.qm_diff_regs is\nfreed, it is not set to NULL. This can lead to a double free when the\nremove process attempts to free it again. Therefore, qm-\u0026gt;debug.qm_diff_regs\nshould be set to NULL after it is freed.(CVE-2025-40062)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn\u0026apos;t rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn\u0026apos;t find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.(CVE-2025-40078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - request reserved interrupt for virtual function\n\nThe device interrupt vector 3 is an error interrupt for\nphysical function and a reserved interrupt for virtual function.\nHowever, the driver has not registered the reserved interrupt for\nvirtual function. When allocating interrupts, the number of interrupts\nis allocated based on powers of two, which includes this interrupt.\nWhen the system enables GICv4 and the virtual function passthrough\nto the virtual machine, releasing the interrupt in the driver\ntriggers a warning.\n\nThe WARNING report is:\nWARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4\n\nTherefore, register a reserved interrupt for VF and set the\nIRQF_NO_AUTOEN flag to avoid that warning.(CVE-2025-40136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: avoid NULL dereference when chunk data buffer is missing\n\nchunk-\u0026gt;skb pointer is dereferenced in the if-block where it\u0026apos;s supposed\nto be NULL only.\n\nchunk-\u0026gt;skb can only be NULL if chunk-\u0026gt;head_skb is not. Check for frag_list\ninstead and do it just before replacing chunk-\u0026gt;skb. We\u0026apos;re sure that\notherwise chunk-\u0026gt;skb is non-NULL because of outer if() condition.(CVE-2025-40240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: remove never-working support for setting nsh fields\n\nThe validation of the set(nsh(...)) action is completely wrong.\nIt runs through the nsh_key_put_from_nlattr() function that is the\nsame function that validates NSH keys for the flow match and the\npush_nsh() action.  However, the set(nsh(...)) has a very different\nmemory layout.  Nested attributes in there are doubled in size in\ncase of the masked set().  That makes proper validation impossible.\n\nThere is also confusion in the code between the \u0026apos;masked\u0026apos; flag, that\nsays that the nested attributes are doubled in size containing both\nthe value and the mask, and the \u0026apos;is_mask\u0026apos; that says that the value\nwe\u0026apos;re parsing is the mask.  This is causing kernel crash on trying to\nwrite into mask part of the match with SW_FLOW_KEY_PUT() during\nvalidation, while validate_nsh() doesn\u0026apos;t allocate any memory for it:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary)\n  RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   validate_nsh+0x60/0x90 [openvswitch]\n   validate_set.constprop.0+0x270/0x3c0 [openvswitch]\n   __ovs_nla_copy_actions+0x477/0x860 [openvswitch]\n   ovs_nla_copy_actions+0x8d/0x100 [openvswitch]\n   ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch]\n   genl_family_rcv_msg_doit+0xdb/0x130\n   genl_family_rcv_msg+0x14b/0x220\n   genl_rcv_msg+0x47/0xa0\n   netlink_rcv_skb+0x53/0x100\n   genl_rcv+0x24/0x40\n   netlink_unicast+0x280/0x3b0\n   netlink_sendmsg+0x1f7/0x430\n   ____sys_sendmsg+0x36b/0x3a0\n   ___sys_sendmsg+0x87/0xd0\n   __sys_sendmsg+0x6d/0xd0\n   do_syscall_64+0x7b/0x2c0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe third issue with this process is that while trying to convert\nthe non-masked set into masked one, validate_set() copies and doubles\nthe size of the OVS_KEY_ATTR_NSH as if it didn\u0026apos;t have any nested\nattributes.  It should be copying each nested attribute and doubling\nthem in size independently.  And the process must be properly reversed\nduring the conversion back from masked to a non-masked variant during\nthe flow dump.\n\nIn the end, the only two outcomes of trying to use this action are\neither validation failure or a kernel crash.  And if somehow someone\nmanages to install a flow with such an action, it will most definitely\nnot do what it is supposed to, since all the keys and the masks are\nmixed up.\n\nFixing all the issues is a complex task as it requires re-writing\nmost of the validation code.\n\nGiven that and the fact that this functionality never worked since\nintroduction, let\u0026apos;s just remove it altogether.  It\u0026apos;s better to\nre-introduce it later with a proper implementation instead of trying\nto fix it in stable releases.(CVE-2025-40254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto\n\nsyzbot reported a possible shift-out-of-bounds [1]\n\nBlamed commit added rto_alpha_max and rto_beta_max set to 1000.\n\nIt is unclear if some sctp users are setting very large rto_alpha\nand/or rto_beta.\n\nIn order to prevent user regression, perform the test at run time.\n\nAlso add READ_ONCE() annotations as sysctl values can change under us.\n\n[1]\n\nUBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41\nshift exponent 64 is too large for 32-bit type \u0026apos;unsigned int\u0026apos;\nCPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:94 [inline]\n  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n  ubsan_epilogue lib/ubsan.c:233 [inline]\n  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494\n  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509\n  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502\n  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338\n  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]\n  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline](CVE-2025-40281)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: Prevent TOCTOU out-of-bounds write\n\nFor the following path not holding the sock lock,\n\n  sctp_diag_dump() -\u0026gt; sctp_for_each_endpoint() -\u0026gt; sctp_ep_dump()\n\nmake sure not to exceed bounds in case the address list has grown\nbetween buffer allocation (time-of-check) and write (time-of-use).(CVE-2025-40331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace BUG_ON with bounds check for map-\u0026gt;max_osd\n\nOSD indexes come from untrusted network packets. Boundary checks are\nadded to validate these against map-\u0026gt;max_osd.\n\n[ idryomov: drop BUG_ON in ceph_get_primary_affinity(), minor cosmetic\n  edits ](CVE-2025-68283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()\n\nThe len field originates from untrusted network packets. Boundary\nchecks have been added to prevent potential out-of-bounds writes when\ndecrypting the connection secret or processing service tickets.\n\n[ idryomov: changelog ](CVE-2025-68284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: lookup hci_conn on RX path on protocol side\n\nThe hdev lock/lookup/unlock/use pattern in the packet RX path doesn\u0026apos;t\nensure hci_conn* is not concurrently modified/deleted. This locking\nappears to be leftover from before conn_hash started using RCU\ncommit bf4c63252490b (\u0026quot;Bluetooth: convert conn hash to RCU\u0026quot;)\nand not clear if it had purpose since then.\n\nCurrently, there are code paths that delete hci_conn* from elsewhere\nthan the ordered hdev-\u0026gt;workqueue where the RX work runs in. E.g.\ncommit 5af1f84ed13a (\u0026quot;Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync\u0026quot;)\nintroduced some of these, and there probably were a few others before\nit.  It\u0026apos;s better to do the locking so that even if these run\nconcurrently no UAF is possible.\n\nMove the lookup of hci_conn and associated socket-specific conn to\nprotocol recv handlers, and do them within a single critical section\nto cover hci_conn* usage and lookup.\n\nsyzkaller has reported a crash that appears to be this issue:\n\n    [Task hdev-\u0026gt;workqueue]          [Task 2]\n                                    hci_disconnect_all_sync\n    l2cap_recv_acldata(hcon)\n                                      hci_conn_get(hcon)\n                                      hci_abort_conn_sync(hcon)\n                                        hci_dev_lock\n      hci_dev_lock\n                                        hci_conn_del(hcon)\n      v-------------------------------- hci_dev_unlock\n                                      hci_conn_put(hcon)\n      conn = hcon-\u0026gt;l2cap_data (UAF)(CVE-2025-68304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: Handle error code returned by ima_filter_rule_match()\n\nIn ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to\nthe rule being NULL, the function incorrectly skips the \u0026apos;if (!rc)\u0026apos; check\nand sets \u0026apos;result = true\u0026apos;. The LSM rule is considered a match, causing\nextra files to be measured by IMA.\n\nThis issue can be reproduced in the following scenario:\nAfter unloading the SELinux policy module via \u0026apos;semodule -d\u0026apos;, if an IMA\nmeasurement is triggered before ima_lsm_rules is updated,\nin ima_match_rules(), the first call to ima_filter_rule_match() returns\n-ESTALE. This causes the code to enter the \u0026apos;if (rc == -ESTALE \u0026amp;\u0026amp;\n!rule_reinitialized)\u0026apos; block, perform ima_lsm_copy_rule() and retry. In\nima_lsm_copy_rule(), since the SELinux module has been removed, the rule\nbecomes NULL, and the second call to ima_filter_rule_match() returns\n-ENOENT. This bypasses the \u0026apos;if (!rc)\u0026apos; check and results in a false match.\n\nCall trace:\n  selinux_audit_rule_match+0x310/0x3b8\n  security_audit_rule_match+0x60/0xa0\n  ima_match_rules+0x2e4/0x4a0\n  ima_match_policy+0x9c/0x1e8\n  ima_get_action+0x48/0x60\n  process_measurement+0xf8/0xa98\n  ima_bprm_check+0x98/0xd8\n  security_bprm_check+0x5c/0x78\n  search_binary_handler+0x6c/0x318\n  exec_binprm+0x58/0x1b8\n  bprm_execve+0xb8/0x130\n  do_execveat_common.isra.0+0x1a8/0x258\n  __arm64_sys_execve+0x48/0x68\n  invoke_syscall+0x50/0x128\n  el0_svc_common.constprop.0+0xc8/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x44/0x200\n  el0t_64_sync_handler+0x100/0x130\n  el0t_64_sync+0x3c8/0x3d0\n\nFix this by changing \u0026apos;if (!rc)\u0026apos; to \u0026apos;if (rc \u0026lt;= 0)\u0026apos; to ensure that error\ncodes like -ENOENT do not bypass the check and accidentally result in a\nsuccessful match.(CVE-2025-68740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u0026gt;stats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u0026lt;-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u0026gt;items[index] = \u0026amp;dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u0026gt;stats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(\u0026amp;stats-\u0026gt;syncp)\n---softirq end---\n\n  static_branch_dec(\u0026amp;cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.(CVE-2025-68742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: Avoid overflowing userspace buffer on stats query\n\nThe ethtool -S command operates across three ioctl calls:\nETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and\nETHTOOL_GSTATS for the values.\n\nIf the number of stats changes between these calls (e.g., due to device\nreconfiguration), userspace\u0026apos;s buffer allocation will be incorrect,\npotentially leading to buffer overflow.\n\nDrivers are generally expected to maintain stable stat counts, but some\ndrivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making\nthis scenario possible.\n\nSome drivers try to handle this internally:\n- bnad_get_ethtool_stats() returns early in case stats.n_stats is not\n  equal to the driver\u0026apos;s stats count.\n- micrel/ksz884x also makes sure not to write anything beyond\n  stats.n_stats and overflow the buffer.\n\nHowever, both use stats.n_stats which is already assigned with the value\nreturned from get_sset_count(), hence won\u0026apos;t solve the issue described\nhere.\n\nChange ethtool_get_strings(), ethtool_get_stats(),\nethtool_get_phy_stats() to not return anything in case of a mismatch\nbetween userspace\u0026apos;s size and get_sset_size(), to prevent buffer\noverflow.\nThe returned n_stats value will be equal to zero, to reflect that\nnothing has been returned.\n\nThis could result in one of two cases when using upstream ethtool,\ndepending on when the size change is detected:\n1. When detected in ethtool_get_strings():\n    # ethtool -S eth2\n    no stats available\n\n2. When detected in get stats, all stats will be reported as zero.\n\nBoth cases are presumably transient, and a subsequent ethtool call\nshould succeed.\n\nOther than the overflow avoidance, these two cases are very evident (no\noutput/cleared stats), which is arguably better than presenting\nincorrect/shifted stats.\nI also considered returning an error instead of a \u0026quot;silent\u0026quot; response, but\nthat seems more destructive towards userspace apps.\n\nNotes:\n- This patch does not claim to fix the inherent race, it only makes sure\n  that we do not overflow the userspace buffer, and makes for a more\n  predictable behavior.\n\n- RTNL lock is held during each ioctl, the race window exists between\n  the separate ioctl calls when the lock is released.\n\n- Userspace ethtool always fills stats.n_stats, but it is likely that\n  these stats ioctls are implemented in other userspace applications\n  which might not fill it. The added code checks that it\u0026apos;s not zero,\n  to prevent any regressions.(CVE-2025-68795)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: xattr: fix null pointer deref in ext4_raw_inode()\n\nIf ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),\niloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()\nlacks error checking, this will lead to a null pointer dereference\nin ext4_raw_inode(), called right after ext4_get_inode_loc().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68820)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: using the num_tqps in the vf driver to apply for resources\n\nCurrently, hdev-\u0026gt;htqp is allocated using hdev-\u0026gt;num_tqps, and kinfo-\u0026gt;tqp\nis allocated using kinfo-\u0026gt;num_tqps. However, kinfo-\u0026gt;num_tqps is set to\nmin(new_tqps, hdev-\u0026gt;num_tqps);  Therefore, kinfo-\u0026gt;num_tqps may be smaller\nthan hdev-\u0026gt;num_tqps, which causes some hdev-\u0026gt;htqp[i] to remain\nuninitialized in hclgevf_knic_setup().\n\nThus, this patch allocates hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp using hdev-\u0026gt;num_tqps,\nensuring that the lengths of hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp are consistent\nand that all elements are properly initialized.(CVE-2025-71064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset\n\n`qfq_class-\u0026gt;leaf_qdisc-\u0026gt;q.qlen \u0026gt; 0` does not imply that the class\nitself is active.\n\nTwo qfq_class objects may point to the same leaf_qdisc. This happens\nwhen:\n\n1. one QFQ qdisc is attached to the dev as the root qdisc, and\n\n2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()\n/ qdisc_put()) and is pending to be destroyed, as in function\ntc_new_tfilter.\n\nWhen packets are enqueued through the root QFQ qdisc, the shared\nleaf_qdisc-\u0026gt;q.qlen increases. At the same time, the second QFQ\nqdisc triggers qdisc_put and qdisc_destroy: the qdisc enters\nqfq_reset() with its own q-\u0026gt;q.qlen == 0, but its class\u0026apos;s leaf\nqdisc-\u0026gt;q.qlen \u0026gt; 0. Therefore, the qfq_reset would wrongly deactivate\nan inactive aggregate and trigger a null-deref in qfq_deactivate_agg:\n\n[    0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    0.903571] #PF: supervisor write access in kernel mode\n[    0.903860] #PF: error_code(0x0002) - not-present page\n[    0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0\n[    0.904502] Oops: Oops: 0002 [#1] SMP NOPTI\n[    0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE\n[    0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[    0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))\n[    0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0\n\nCode starting with the faulting instruction\n===========================================\n   0:\t0f 84 4d 01 00 00    \tje     0x153\n   6:\t48 89 70 18          \tmov    %rsi,0x18(%rax)\n   a:\t8b 4b 10             \tmov    0x10(%rbx),%ecx\n   d:\t48 c7 c2 ff ff ff ff \tmov    $0xffffffffffffffff,%rdx\n  14:\t48 8b 78 08          \tmov    0x8(%rax),%rdi\n  18:\t48 d3 e2             \tshl    %cl,%rdx\n  1b:\t48 21 f2             \tand    %rsi,%rdx\n  1e:\t48 2b 13             \tsub    (%rbx),%rdx\n  21:\t48 8b 30             \tmov    (%rax),%rsi\n  24:\t48 d3 ea             \tshr    %cl,%rdx\n  27:\t8b 4b 18             \tmov    0x18(%rbx),%ecx\n\t...\n[    0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246\n[    0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000\n[    0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[    0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000\n[    0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000\n[    0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880\n[    0.909179] FS:  000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000\n[    0.909572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0\n[    0.910247] PKRU: 55555554\n[    0.910391] Call Trace:\n[    0.910527]  \u0026lt;TASK\u0026gt;\n[    0.910638]  qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)\n[    0.910826]  qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)\n[    0.911040]  __qdisc_destroy (net/sched/sch_generic.c:1076)\n[    0.911236]  tc_new_tfilter (net/sched/cls_api.c:2447)\n[    0.911447]  rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\n[    0.911663]  ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)\n[    0.911894]  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n[    0.912100]  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n[    0.912296]  ? __alloc_skb (net/core/skbuff.c:706)\n[    0.912484]  netlink_sendmsg (net/netlink/af\n---truncated---(CVE-2026-22976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix reference count leak in bpf_prog_test_run_xdp()\n\nsyzbot is reporting\n\n  unregister_netdevice: waiting for sit0 to become free. Usage count = 2\n\nproblem. A debug printk() patch found that a refcount is obtained at\nxdp_convert_md_to_buff() from bpf_prog_test_run_xdp().\n\nAccording to commit ec94670fcb3b (\u0026quot;bpf: Support specifying ingress via\nxdp_md context in BPF_PROG_TEST_RUN\u0026quot;), the refcount obtained by\nxdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().\n\nTherefore, we can consider that the error handling path introduced by\ncommit 1c1949982524 (\u0026quot;bpf: introduce frags support to\nbpf_prog_test_run_xdp()\u0026quot;) forgot to call xdp_convert_buff_to_md().(CVE-2026-22994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a deadlock involving nfs_release_folio()\n\nWang Zhaolong reports a deadlock involving NFSv4.1 state recovery\nwaiting on kthreadd, which is attempting to reclaim memory by calling\nnfs_release_folio(). The latter cannot make progress due to state\nrecovery being needed.\n\nIt seems that the only safe thing to do here is to kick off a writeback\nof the folio, without waiting for completion, or else kicking off an\nasynchronous commit.(CVE-2026-23053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: implement mremap in uacce_vm_ops to return -EPERM\n\nThe current uacce_vm_ops does not support the mremap operation of\nvm_operations_struct. Implement .mremap to return -EPERM to remind\nusers.\n\nThe reason we need to explicitly disable mremap is that when the\ndriver does not implement .mremap, it uses the default mremap\nmethod. This could lead to a risk scenario:\n\nAn application might first mmap address p1, then mremap to p2,\nfollowed by munmap(p1), and finally munmap(p2). Since the default\nmremap copies the original vma\u0026apos;s vm_private_data (i.e., q) to the\nnew vma, both munmap operations would trigger vma_close, causing\nq-\u0026gt;qfr to be freed twice(qfr will be set to null here, so repeated\nrelease is ok).(CVE-2026-23056)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: ensure safe queue release with state management\n\nDirectly calling `put_queue` carries risks since it cannot\nguarantee that resources of `uacce_queue` have been fully released\nbeforehand. So adding a `stop_queue` operation for the\nUACCE_CMD_PUT_Q command and leaving the `put_queue` operation to\nthe final resource release ensures safety.\n\nQueue states are defined as follows:\n- UACCE_Q_ZOMBIE: Initial state\n- UACCE_Q_INIT: After opening `uacce`\n- UACCE_Q_STARTED: After `start` is issued via `ioctl`\n\nWhen executing `poweroff -f` in virt while accelerator are still\nworking, `uacce_fops_release` and `uacce_remove` may execute\nconcurrently. This can cause `uacce_put_queue` within\n`uacce_fops_release` to access a NULL `ops` pointer. Therefore, add\nstate checks to prevent accessing freed pointers.(CVE-2026-23063)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: maple: free entry on mas_store_gfp() failure\n\nregcache_maple_write() allocates a new block (\u0026apos;entry\u0026apos;) to merge\nadjacent ranges and then stores it with mas_store_gfp().\nWhen mas_store_gfp() fails, the new \u0026apos;entry\u0026apos; remains allocated and\nis never freed, leaking memory.\n\nFree \u0026apos;entry\u0026apos; on the failure path; on success continue freeing the\nreplaced neighbor blocks (\u0026apos;lower\u0026apos;, \u0026apos;upper\u0026apos;).(CVE-2026-23260)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: observe an RCU grace period in macvlan_common_newlink() error path\n\nvalis reported that a race condition still happens after my prior patch.\n\nmacvlan_common_newlink() might have made @dev visible before\ndetecting an error, and its caller will directly call free_netdev(dev).\n\nWe must respect an RCU period, either in macvlan or the core networking\nstack.\n\nAfter adding a temporary mdelay(1000) in macvlan_forward_source_one()\nto open the race window, valis repro was:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\nip link add mv0 link p2 type macvlan mode source\n\n(ip link add invalid% link p2 type macvlan mode source macaddr add\n00:00:00:00:00:20 \u0026amp;) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4\nPING 1.2.3.4 (1.2.3.4): 56 data bytes\nRTNETLINK answers: Invalid argument\n\nBUG: KASAN: slab-use-after-free in macvlan_forward_source\n(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nRead of size 8 at addr ffff888016bb89c0 by task e/175\n\nCPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\nCall Trace:\n\u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:123)\nprint_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nkasan_report (mm/kasan/report.c:597)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nmacvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\n? tasklet_init (kernel/softirq.c:983)\nmacvlan_handle_frame (drivers/net/macvlan.c:501)\n\nAllocated by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\n__kasan_kmalloc (mm/kasan/common.c:419)\n__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657\nmm/slub.c:7140)\nalloc_netdev_mqs (net/core/dev.c:12012)\nrtnl_create_link (net/core/rtnetlink.c:3648)\nrtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nFreed by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\nkasan_save_free_info (mm/kasan/generic.c:587)\n__kasan_slab_free (mm/kasan/common.c:287)\nkfree (mm/slub.c:6674 mm/slub.c:6882)\nrtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)(CVE-2026-23273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: reject mount if bigalloc with s_first_data_block != 0\n\nbigalloc with s_first_data_block != 0 is not supported, reject mounting\nit.(CVE-2026-31447)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: Check to ensure report responses match the request\n\nIt is possible for a malicious (or clumsy) device to respond to a\nspecific report\u0026apos;s feature request using a completely different report\nID.  This can cause confusion in the HID core resulting in nasty\nside-effects such as OOB writes.\n\nAdd a check to ensure that the report ID in the response, matches the\none that was requested.  If it doesn\u0026apos;t, omit reporting the raw event and\nreturn early.(CVE-2026-43047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Mitigate potential OOB by removing bogus memset()\n\nThe memset() in hid_report_raw_event() has the good intention of\nclearing out bogus data by zeroing the area from the end of the incoming\ndata string to the assumed end of the buffer.  However, as we have\npreviously seen, doing so can easily result in OOB reads and writes in\nthe subsequent thread of execution.\n\nThe current suggestion from one of the HID maintainers is to remove the\nmemset() and simply return if the incoming event buffer size is not\nlarge enough to fill the associated report.\n\nSuggested-by Benjamin Tissoires \u0026lt;(CVE-2026-43048)\n\nIn the Linux kernel, there is a potential out-of-bounds access vulnerability in the ceph_handle_auth_reply() function of the libceph component. When processing messages of type CEPH_MSG_AUTH_REPLY, the value of the payload_len field is stored in a variable of type int. A value greater than INT_MAX leads to integer overflow and is interpreted as a negative value, which causes the pointer address to be decremented and subsequently accessed because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation. The vulnerability is fixed by changing the data type of payload_len to u32 and introducing additional sanity checks.(CVE-2026-43407)","status":"published","published":"2026-05-22T11:11:22Z","modified":"2026-08-18T01:20:03.128754584Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"OESA-2026-2418","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MMWe currently assume that there is at least one VMA in a MM, which isn ttrue.So we might end up having find_vma() return NULL, to then de-referenceNULL.  So properly handle find_vma() returning NULL.This fixes the report:Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline]RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194Code: ...RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8FS:  00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400Call Trace: \u0026lt;TASK\u0026gt; kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f[akpm@linux-foundation.org: add unlikely()](CVE-2024-56611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle lack of irqdomain gracefully\n\nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a\nRISCV platform which does not provide PCI/MSI support:\n\n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32\n __pci_enable_msix_range+0x30c/0x596\n pci_msi_setup_msi_irqs+0x2c/0x32\n pci_alloc_irq_vectors_affinity+0xb8/0xe2\n\nRISCV uses hierarchical interrupt domains and correctly does not implement\nthe legacy fallback. The warning triggers from the legacy fallback stub.\n\nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent\ndomain is associated with the device or not. There is a check for MSI-X,\nwhich has a legacy assumption. But that legacy fallback assumption is only\nvalid when legacy support is enabled, but otherwise the check should simply\nreturn -ENOTSUPP.\n\nLoongarch tripped over the same problem and blindly enabled legacy support\nwithout implementing the legacy fallbacks. There are weak implementations\nwhich return an error, so the problem was papered over.\n\nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add\nthe missing supported check into the MSI enable path to complete it.(CVE-2024-56760)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: fix nfs_release_folio() to not deadlock via kcompactd writeback\n\nAdd PF_KCOMPACTD flag and current_is_kcompactd() helper to check for it so\nnfs_release_folio() can skip calling nfs_wb_folio() from kcompactd.\n\nOtherwise NFS can deadlock waiting for kcompactd enduced writeback which\nrecurses back to NFS (which triggers writeback to NFSD via NFS loopback\nmount on the same host, NFSD blocks waiting for XFS\u0026apos;s call to\n__filemap_get_folio):\n\n6070.550357] INFO: task kcompactd0:58 blocked for more than 4435 seconds.\n\n{---\n[58] \u0026quot;kcompactd0\u0026quot;\n[\u0026lt;0\u0026gt;] folio_wait_bit+0xe8/0x200\n[\u0026lt;0\u0026gt;] folio_wait_writeback+0x2b/0x80\n[\u0026lt;0\u0026gt;] nfs_wb_folio+0x80/0x1b0 [nfs]\n[\u0026lt;0\u0026gt;] nfs_release_folio+0x68/0x130 [nfs]\n[\u0026lt;0\u0026gt;] split_huge_page_to_list_to_order+0x362/0x840\n[\u0026lt;0\u0026gt;] migrate_pages_batch+0x43d/0xb90\n[\u0026lt;0\u0026gt;] migrate_pages_sync+0x9a/0x240\n[\u0026lt;0\u0026gt;] migrate_pages+0x93c/0x9f0\n[\u0026lt;0\u0026gt;] compact_zone+0x8e2/0x1030\n[\u0026lt;0\u0026gt;] compact_node+0xdb/0x120\n[\u0026lt;0\u0026gt;] kcompactd+0x121/0x2e0\n[\u0026lt;0\u0026gt;] kthread+0xcf/0x100\n[\u0026lt;0\u0026gt;] ret_from_fork+0x31/0x40\n[\u0026lt;0\u0026gt;] ret_from_fork_asm+0x1a/0x30\n---}\n\n[(CVE-2025-21908)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio\n\nCommit b15c87263a69 (\u0026quot;hwpoison, memory_hotplug: allow hwpoisoned pages to\nbe offlined) add page poison checks in do_migrate_range in order to make\noffline hwpoisoned page possible by introducing isolate_lru_page and\ntry_to_unmap for hwpoisoned page.  However folio lock must be held before\ncalling try_to_unmap.  Add it to fix this problem.\n\nWarning will be produced if folio is not locked during unmap:\n\n  ------------[ cut here ]------------\n  kernel BUG at ./include/linux/swapops.h:400!\n  Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 4 UID: 0 PID: 411 Comm: bash Tainted: G        W          6.13.0-rc1-00016-g3c434c7ee82a-dirty #41\n  Tainted: [W]=WARN\n  Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n  pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  pc : try_to_unmap_one+0xb08/0xd3c\n  lr : try_to_unmap_one+0x3dc/0xd3c\n  Call trace:\n   try_to_unmap_one+0xb08/0xd3c (P)\n   try_to_unmap_one+0x3dc/0xd3c (L)\n   rmap_walk_anon+0xdc/0x1f8\n   rmap_walk+0x3c/0x58\n   try_to_unmap+0x88/0x90\n   unmap_poisoned_folio+0x30/0xa8\n   do_migrate_range+0x4a0/0x568\n   offline_pages+0x5a4/0x670\n   memory_block_action+0x17c/0x374\n   memory_subsys_offline+0x3c/0x78\n   device_offline+0xa4/0xd0\n   state_store+0x8c/0xf0\n   dev_attr_store+0x18/0x2c\n   sysfs_kf_write+0x44/0x54\n   kernfs_fop_write_iter+0x118/0x1a8\n   vfs_write+0x3a8/0x4bc\n   ksys_write+0x6c/0xf8\n   __arm64_sys_write+0x1c/0x28\n   invoke_syscall+0x44/0x100\n   el0_svc_common.constprop.0+0x40/0xe0\n   do_el0_svc+0x1c/0x28\n   el0_svc+0x30/0xd0\n   el0t_64_sync_handler+0xc8/0xcc\n   el0t_64_sync+0x198/0x19c\n  Code: f9407be0 b5fff320 d4210000 17ffff97 (d4210000)\n  ---[ end trace 0000000000000000 ]---(CVE-2025-21931)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Bridge, fix the crash caused by LAG state check\n\nWhen removing LAG device from bridge, NETDEV_CHANGEUPPER event is\ntriggered. Driver finds the lower devices (PFs) to flush all the\noffloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns\nfalse if one of PF is unloaded. In such case,\nmlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of\nthe alive PF, and the flush is skipped.\n\nBesides, the bridge fdb entry\u0026apos;s lastuse is updated in mlx5 bridge\nevent handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be\nignored in this case because the upper interface for bond is deleted,\nand the entry will never be aged because lastuse is never updated.\n\nTo make things worse, as the entry is alive, mlx5 bridge workqueue\nkeeps sending that event, which is then handled by kernel bridge\nnotifier. It causes the following crash when accessing the passed bond\nnetdev which is already destroyed.\n\nTo fix this issue, remove such checks. LAG state is already checked in\ncommit 15f8f168952f (\u0026quot;net/mlx5: Bridge, verify LAG state when adding\nbond to bridge\u0026quot;), driver still need to skip offload if LAG becomes\ninvalid state after initialization.\n\n Oops: stack segment: 0000 [#1] SMP\n CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G           OE      6.11.0_mlnx #1\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n Workqueue: mlx5_bridge_wq mlx5_esw_bridge_update_work [mlx5_core]\n RIP: 0010:br_switchdev_event+0x2c/0x110 [bridge]\n Code: 44 00 00 48 8b 02 48 f7 00 00 02 00 00 74 69 41 54 55 53 48 83 ec 08 48 8b a8 08 01 00 00 48 85 ed 74 4a 48 83 fe 02 48 89 d3 \u0026lt;4c\u0026gt; 8b 65 00 74 23 76 49 48 83 fe 05 74 7e 48 83 fe 06 75 2f 0f b7\n RSP: 0018:ffffc900092cfda0 EFLAGS: 00010297\n RAX: ffff888123bfe000 RBX: ffffc900092cfe08 RCX: 00000000ffffffff\n RDX: ffffc900092cfe08 RSI: 0000000000000001 RDI: ffffffffa0c585f0\n RBP: 6669746f6e690a30 R08: 0000000000000000 R09: ffff888123ae92c8\n R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888123ae9c60\n R13: 0000000000000001 R14: ffffc900092cfe08 R15: 0000000000000000\n FS:  0000000000000000(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f15914c8734 CR3: 0000000002830005 CR4: 0000000000770ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ? __die_body+0x1a/0x60\n  ? die+0x38/0x60\n  ? do_trap+0x10b/0x120\n  ? do_error_trap+0x64/0xa0\n  ? exc_stack_segment+0x33/0x50\n  ? asm_exc_stack_segment+0x22/0x30\n  ? br_switchdev_event+0x2c/0x110 [bridge]\n  ? sched_balance_newidle.isra.149+0x248/0x390\n  notifier_call_chain+0x4b/0xa0\n  atomic_notifier_call_chain+0x16/0x20\n  mlx5_esw_bridge_update+0xec/0x170 [mlx5_core]\n  mlx5_esw_bridge_update_work+0x19/0x40 [mlx5_core]\n  process_scheduled_works+0x81/0x390\n  worker_thread+0x106/0x250\n  ? bh_worker+0x110/0x110\n  kthread+0xb7/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n  \u0026lt;/TASK\u0026gt;(CVE-2025-21970)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: Prevent creation of classes with TC_H_ROOT\n\nThe function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination\ncondition when traversing up the qdisc tree to update parent backlog\ncounters. However, if a class is created with classid TC_H_ROOT, the\ntraversal terminates prematurely at this class instead of reaching the\nactual root qdisc, causing parent statistics to be incorrectly maintained.\nIn case of DRR, this could lead to a crash as reported by Mingi Cho.\n\nPrevent the creation of any Qdisc class with classid TC_H_ROOT\n(0xFFFFFFFF) across all qdisc types, as suggested by Jamal.(CVE-2025-21971)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched: address a potential NULL pointer dereference in the GRED scheduler.\n\nIf kzalloc in gred_init returns a NULL pointer, the code follows the\nerror handling path, invoking gred_destroy. This, in turn, calls\ngred_offload, where memset could receive a NULL pointer as input,\npotentially leading to a kernel crash.\n\nWhen table-\u0026gt;opt is NULL in gred_init(), gred_change_table_def()\nis not called yet, so it is not necessary to call -\u0026gt;ndo_setup_tc()\nin gred_offload().(CVE-2025-21980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix memory leak in aRFS after reset\n\nFix aRFS (accelerated Receive Flow Steering) structures memory leak by\nadding a checker to verify if aRFS memory is already allocated while\nconfiguring VSI. aRFS objects are allocated in two cases:\n- as part of VSI initialization (at probe), and\n- as part of reset handling\n\nHowever, VSI reconfiguration executed during reset involves memory\nallocation one more time, without prior releasing already allocated\nresources. This led to the memory leak with the following signature:\n\n[root@os-delivery ~]# cat /sys/kernel/debug/kmemleak\nunreferenced object 0xff3c1ca7252e6000 (size 8192):\n  comm \u0026quot;kworker/0:0\u0026quot;, pid 8, jiffies 4296833052\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [\u0026lt;ffffffff991ec485\u0026gt;] __kmalloc_cache_noprof+0x275/0x340\n    [\u0026lt;ffffffffc0a6e06a\u0026gt;] ice_init_arfs+0x3a/0xe0 [ice]\n    [\u0026lt;ffffffffc09f1027\u0026gt;] ice_vsi_cfg_def+0x607/0x850 [ice]\n    [\u0026lt;ffffffffc09f244b\u0026gt;] ice_vsi_setup+0x5b/0x130 [ice]\n    [\u0026lt;ffffffffc09c2131\u0026gt;] ice_init+0x1c1/0x460 [ice]\n    [\u0026lt;ffffffffc09c64af\u0026gt;] ice_probe+0x2af/0x520 [ice]\n    [\u0026lt;ffffffff994fbcd3\u0026gt;] local_pci_probe+0x43/0xa0\n    [\u0026lt;ffffffff98f07103\u0026gt;] work_for_cpu_fn+0x13/0x20\n    [\u0026lt;ffffffff98f0b6d9\u0026gt;] process_one_work+0x179/0x390\n    [\u0026lt;ffffffff98f0c1e9\u0026gt;] worker_thread+0x239/0x340\n    [\u0026lt;ffffffff98f14abc\u0026gt;] kthread+0xcc/0x100\n    [\u0026lt;ffffffff98e45a6d\u0026gt;] ret_from_fork+0x2d/0x50\n    [\u0026lt;ffffffff98e083ba\u0026gt;] ret_from_fork_asm+0x1a/0x30\n    ...(CVE-2025-21981)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: switchdev: Convert blocking notification chain to a raw one\n\nA blocking notification chain uses a read-write semaphore to protect the\nintegrity of the chain. The semaphore is acquired for writing when\nadding / removing notifiers to / from the chain and acquired for reading\nwhen traversing the chain and informing notifiers about an event.\n\nIn case of the blocking switchdev notification chain, recursive\nnotifications are possible which leads to the semaphore being acquired\ntwice for reading and to lockdep warnings being generated [1].\n\nSpecifically, this can happen when the bridge driver processes a\nSWITCHDEV_BRPORT_UNOFFLOADED event which causes it to emit notifications\nabout deferred events when calling switchdev_deferred_process().\n\nFix this by converting the notification chain to a raw notification\nchain in a similar fashion to the netdev notification chain. Protect\nthe chain using the RTNL mutex by acquiring it when modifying the chain.\nEvents are always informed under the RTNL mutex, but add an assertion in\ncall_switchdev_blocking_notifiers() to make sure this is not violated in\nthe future.\n\nMaintain the \u0026quot;blocking\u0026quot; prefix as events are always emitted from process\ncontext and listeners are allowed to block.\n\n[1]:\nWARNING: possible recursive locking detected\n6.14.0-rc4-custom-g079270089484 #1 Not tainted\n--------------------------------------------\nip/52731 is trying to acquire lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nbut task is already holding lock:\nffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nother info that might help us debug this:\nPossible unsafe locking scenario:\nCPU0\n----\nlock((switchdev_blocking_notif_chain).rwsem);\nlock((switchdev_blocking_notif_chain).rwsem);\n\n*** DEADLOCK ***\nMay be due to missing lock nesting notation\n3 locks held by ip/52731:\n #0: ffffffff84f795b0 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x727/0x1dc0\n #1: ffffffff8731f628 (\u0026amp;net-\u0026gt;rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x790/0x1dc0\n #2: ffffffff850918d8 ((switchdev_blocking_notif_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x58/0xa0\n\nstack backtrace:\n...\n? __pfx_down_read+0x10/0x10\n? __pfx_mark_lock+0x10/0x10\n? __pfx_switchdev_port_attr_set_deferred+0x10/0x10\nblocking_notifier_call_chain+0x58/0xa0\nswitchdev_port_attr_notify.constprop.0+0xb3/0x1b0\n? __pfx_switchdev_port_attr_notify.constprop.0+0x10/0x10\n? mark_held_locks+0x94/0xe0\n? switchdev_deferred_process+0x11a/0x340\nswitchdev_port_attr_set_deferred+0x27/0xd0\nswitchdev_deferred_process+0x164/0x340\nbr_switchdev_port_unoffload+0xc8/0x100 [bridge]\nbr_switchdev_blocking_event+0x29f/0x580 [bridge]\nnotifier_call_chain+0xa2/0x440\nblocking_notifier_call_chain+0x6e/0xa0\nswitchdev_bridge_port_unoffload+0xde/0x1a0\n...(CVE-2025-21986)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix fence reference count leak\n\nThe last_scheduled fence leaks when an entity is being killed and adding\nthe cleanup callback fails.\n\nDecrement the reference count of prev when dma_fence_add_callback()\nfails, ensuring proper balance.\n\n[phasta: add git tag info for stable kernel](CVE-2025-21995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/qaic: Fix integer overflow in qaic_validate_req()\n\nThese are u64 variables that come from the user via\nqaic_attach_slice_bo_ioctl().  Use check_add_overflow() to ensure that\nthe math doesn\u0026apos;t have an integer wrapping bug.(CVE-2025-22001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: dummy: force synchronous probing\n\nSometimes I get a NULL pointer dereference at boot time in kobject_get()\nwith the following call stack:\n\nanatop_regulator_probe()\n devm_regulator_register()\n  regulator_register()\n   regulator_resolve_supply()\n    kobject_get()\n\nBy placing some extra BUG_ON() statements I could verify that this is\nraised because probing of the \u0026apos;dummy\u0026apos; regulator driver is not completed\n(\u0026apos;dummy_regulator_rdev\u0026apos; is still NULL).\n\nIn the JTAG debugger I can see that dummy_regulator_probe() and\nanatop_regulator_probe() can be run by different kernel threads\n(kworker/u4:*).  I haven\u0026apos;t further investigated whether this can be\nchanged or if there are other possibilities to force synchronization\nbetween these two probe routines.  On the other hand I don\u0026apos;t expect much\nboot time penalty by probing the \u0026apos;dummy\u0026apos; regulator synchronously.(CVE-2025-22009)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspufs: fix a leak in spufs_create_context()\n\nLeak fixes back in 2008 missed one case - if we are trying to set affinity\nand spufs_mkdir() fails, we need to drop the reference to neighbor.(CVE-2025-22071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;smb: client: fix TCP timers deadlock after rmmod\u0026quot;\n\nThis reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.\n\nCommit e9f2517a3e18 (\u0026quot;smb: client: fix TCP timers deadlock after\nrmmod\u0026quot;) is intended to fix a null-ptr-deref in LOCKDEP, which is\nmentioned as CVE-2024-54680, but is actually did not fix anything;\nThe issue can be reproduced on top of it. [0]\n\nAlso, it reverted the change by commit ef7134c7fc48 (\u0026quot;smb: client:\nFix use-after-free of network namespace.\u0026quot;) and introduced a real\nissue by reviving the kernel TCP socket.\n\nWhen a reconnect happens for a CIFS connection, the socket state\ntransitions to FIN_WAIT_1.  Then, inet_csk_clear_xmit_timers_sync()\nin tcp_close() stops all timers for the socket.\n\nIf an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1\nforever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.\n\nUsually, FIN can be retransmitted by the peer, but if the peer aborts\nthe connection, the issue comes into reality.\n\nI warned about this privately by pointing out the exact report [1],\nbut the bogus fix was finally merged.\n\nSo, we should not stop the timers to finally kill the connection on\nour side in that case, meaning we must not use a kernel socket for\nTCP whose sk-\u0026gt;sk_net_refcnt is 0.\n\nThe kernel socket does not have a reference to its netns to make it\npossible to tear down netns without cleaning up every resource in it.\n\nFor example, tunnel devices use a UDP socket internally, but we can\ndestroy netns without removing such devices and let it complete\nduring exit.  Otherwise, netns would be leaked when the last application\ndied.\n\nHowever, this is problematic for TCP sockets because TCP has timers to\nclose the connection gracefully even after the socket is close()d.  The\nlifetime of the socket and its netns is different from the lifetime of\nthe underlying connection.\n\nIf the socket user does not maintain the netns lifetime, the timer could\nbe fired after the socket is close()d and its netns is freed up, resulting\nin use-after-free.\n\nActually, we have seen so many similar issues and converted such sockets\nto have a reference to netns.\n\nThat\u0026apos;s why I converted the CIFS client socket to have a reference to\nnetns (sk-\u0026gt;sk_net_refcnt == 1), which is somehow mentioned as out-of-scope\nof CIFS and technically wrong in e9f2517a3e18, but **is in-scope and right\nfix**.\n\nRegarding the LOCKDEP issue, we can prevent the module unload by\nbumping the module refcount when switching the LOCKDDEP key in\nsock_lock_init_class_and_name(). [2]\n\nFor a while, let\u0026apos;s revert the bogus fix.\n\nNote that now we can use sk_net_refcnt_upgrade() for the socket\nconversion, but I\u0026apos;ll do so later separately to make backport easy.(CVE-2025-22077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwatch_queue: fix pipe accounting mismatch\n\nCurrently, watch_queue_set_size() modifies the pipe buffers charged to\nuser-\u0026gt;pipe_bufs without updating the pipe-\u0026gt;nr_accounted on the pipe\nitself, due to the if (!pipe_has_watch_queue()) test in\npipe_resize_ring(). This means that when the pipe is ultimately freed,\nwe decrement user-\u0026gt;pipe_bufs by something other than what than we had\ncharged to it, potentially leading to an underflow. This in turn can\ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.\n\nTo remedy this, explicitly account for the pipe usage in\nwatch_queue_set_size() to match the number set via account_pipe_buffers()\n\n(It\u0026apos;s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)(CVE-2025-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: venus: hfi_parser: add check to avoid out of bound access\n\nThere is a possibility that init_codecs is invoked multiple times during\nmanipulated payload from video firmware. In such case, if codecs_count\ncan get incremented to value more than MAX_CODEC_NUM, there can be OOB\naccess. Reset the count so that it always starts from beginning.(CVE-2025-23157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add sanity check for agwidth in dbMount\n\nThe width in dmapctl of the AG is zero, it trigger a divide error when\ncalculating the control page level in dbAllocAG.\n\nTo avoid this issue, add a check for agwidth in dbAllocAG.(CVE-2025-37740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group\n\nCurrently, mtk_iommu calls during probe iommu_device_register before\nthe hw_list from driver data is initialized. Since iommu probing issue\nfix, it leads to NULL pointer dereference in mtk_iommu_device_group when\nhw_list is accessed with list_first_entry (not null safe).\n\nSo, change the call order to ensure iommu_device_register is called\nafter the driver data are initialized.(CVE-2025-37748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37766)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: Prevent division by zero\n\nThe user can set any speed value.\nIf speed is greater than UINT_MAX/8, division by zero is possible.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix dangling pointer in krb_authenticate\n\nkrb_authenticate frees sess-\u0026gt;user and does not set the pointer\nto NULL. It calls ksmbd_krb5_authenticate to reinitialise\nsess-\u0026gt;user but that function may return without doing so. If\nthat happens then smb2_sess_setup, which calls krb_authenticate,\nwill be accessing free\u0026apos;d memory when it later uses sess-\u0026gt;user.(CVE-2025-37778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Fix null-ptr-deref in avs_component_probe()\n\ndevm_kasprintf() returns NULL when memory allocation fails. Currently,\navs_component_probe() does not check for this case, which results in a\nNULL pointer dereference.(CVE-2025-37793)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsound/virtio: Fix cancel_sync warnings on uninitialized work_structs\n\nBetty reported hitting the following warning:\n\n[    8.709131][  T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182\n...\n[    8.713282][  T221] Call trace:\n[    8.713365][  T221]  __flush_work+0x8d0/0x914\n[    8.713468][  T221]  __cancel_work_sync+0xac/0xfc\n[    8.713570][  T221]  cancel_work_sync+0x24/0x34\n[    8.713667][  T221]  virtsnd_remove+0xa8/0xf8 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.713868][  T221]  virtsnd_probe+0x48c/0x664 [virtio_snd ab15f34d0dd772f6d11327e08a81d46dc9c36276]\n[    8.714035][  T221]  virtio_dev_probe+0x28c/0x390\n[    8.714139][  T221]  really_probe+0x1bc/0x4c8\n...\n\nIt seems we\u0026apos;re hitting the error path in virtsnd_probe(), which\ntriggers a virtsnd_remove() which iterates over the substreams\ncalling cancel_work_sync() on the elapsed_period work_struct.\n\nLooking at the code, from earlier in:\nvirtsnd_probe()-\u0026gt;virtsnd_build_devs()-\u0026gt;virtsnd_pcm_parse_cfg()\n\nWe set snd-\u0026gt;nsubstreams, allocate the snd-\u0026gt;substreams, and if\nwe then hit an error on the info allocation or something in\nvirtsnd_ctl_query_info() fails, we will exit without having\ninitialized the elapsed_period work_struct.\n\nWhen that error path unwinds we then call virtsnd_remove()\nwhich as long as the substreams array is allocated, will iterate\nthrough calling cancel_work_sync() on the uninitialized work\nstruct hitting this warning.\n\nTakashi Iwai suggested this fix, which initializes the substreams\nstructure right after allocation, so that if we hit the error\npaths we avoid trying to cleanup uninitialized data.\n\nNote: I have not yet managed to reproduce the issue myself, so\nthis patch has had limited testing.\n\nFeedback or thoughts would be appreciated!(CVE-2025-37805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration\n\nResolve kernel panic while accessing IRQ handler associated with the\ngenerated IRQ. This is done by acquiring the spinlock and storing the\ncurrent interrupt state before handling the interrupt request using\ngeneric_handle_irq.\n\nA previous fix patch was submitted where \u0026apos;generic_handle_irq\u0026apos; was\nreplaced with \u0026apos;handle_nested_irq\u0026apos;. However, this change also causes\nthe kernel panic where after determining which GPIO triggered the\ninterrupt and attempting to call handle_nested_irq with the mapped\nIRQ number, leads to a failure in locating the registered handler.(CVE-2025-37815)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: apple-soc: Fix null-ptr-deref in apple_soc_cpufreq_get_rate()\n\ncpufreq_cpu_get_raw() can return NULL when the target CPU is not present\nin the policy-\u0026gt;cpus mask. apple_soc_cpufreq_get_rate() does not check\nfor this case, which results in a NULL pointer dereference.(CVE-2025-37831)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: avoid NULL pointer dereference in dbg call\n\ncifs_server_dbg() implies server to be non-NULL so\nmove call under condition to avoid NULL pointer dereference.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37844)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: debugfs hang_hws skip GPU with MES\n\ndebugfs hang_hws is used by GPU reset test with HWS, for MES this crash\nthe kernel with NULL pointer access because dqm-\u0026gt;packet_mgr is not setup\nfor MES path.\n\nSkip GPU with MES for now, MES hang_hws debugfs interface will be\nsupported later.(CVE-2025-37853)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d-\u0026gt;name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\u0026quot;ice: Fix some null pointer dereference issues in ice_ptp.c\u0026quot;).\n\nThis issue is found by our static analysis tool(CVE-2025-37881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Consistently treat platform_max as control value\n\nThis reverts commit 9bdd10d57a88 (\u0026quot;ASoC: ops: Shift tested values in\nsnd_soc_put_volsw() by +min\u0026quot;), and makes some additional related\nupdates.\n\nThere are two ways the platform_max could be interpreted; the maximum\nregister value, or the maximum value the control can be set to. The\npatch moved from treating the value as a control value to a register\none. When the patch was applied it was technically correct as\nsnd_soc_limit_volume() also used the register interpretation. However,\neven then most of the other usages treated platform_max as a\ncontrol value, and snd_soc_limit_volume() has since been updated to\nalso do so in commit fb9ad24485087 (\u0026quot;ASoC: ops: add correct range\ncheck for limiting volume\u0026quot;). That patch however, missed updating\nsnd_soc_put_volsw() back to the control interpretation, and fixing\nsnd_soc_info_volsw_range(). The control interpretation makes more\nsense as limiting is typically done from the machine driver, so it is\nappropriate to use the customer facing representation rather than the\ninternal codec representation. Update all the code to consistently use\nthis interpretation of platform_max.\n\nFinally, also add some comments to the soc_mixer_control struct to\nhopefully avoid further patches switching between the two approaches.(CVE-2025-37889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Balance device refcount when destroying devices\n\nUsing device_find_child() to lookup the proper SCMI device to destroy\ncauses an unbalance in device refcount, since device_find_child() calls an\nimplicit get_device(): this, in turns, inhibits the call of the provided\nrelease methods upon devices destruction.\n\nAs a consequence, one of the structures that is not freed properly upon\ndestruction is the internal struct device_private dev-\u0026gt;p populated by the\ndrivers subsystem core.\n\nKMemleak detects this situation since loading/unloding some SCMI driver\ncauses related devices to be created/destroyed without calling any\ndevice_release method.\n\nunreferenced object 0xffff00000f583800 (size 512):\n  comm \u0026quot;insmod\u0026quot;, pid 227, jiffies 4294912190\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 60 36 1d 8a 00 80 ff ff  ........`6......\n  backtrace (crc 114e2eed):\n    kmemleak_alloc+0xbc/0xd8\n    __kmalloc_cache_noprof+0x2dc/0x398\n    device_add+0x954/0x12d0\n    device_register+0x28/0x40\n    __scmi_device_create.part.0+0x1bc/0x380\n    scmi_device_create+0x2d0/0x390\n    scmi_create_protocol_devices+0x74/0xf8\n    scmi_device_request_notifier+0x1f8/0x2a8\n    notifier_call_chain+0x110/0x3b0\n    blocking_notifier_call_chain+0x70/0xb0\n    scmi_driver_register+0x350/0x7f0\n    0xffff80000a3b3038\n    do_one_initcall+0x12c/0x730\n    do_init_module+0x1dc/0x640\n    load_module+0x4b20/0x5b70\n    init_module_from_file+0xec/0x158\n\n$ ./scripts/faddr2line ./vmlinux device_add+0x954/0x12d0\ndevice_add+0x954/0x12d0:\nkmalloc_noprof at include/linux/slab.h:901\n(inlined by) kzalloc_noprof at include/linux/slab.h:1037\n(inlined by) device_private_init at drivers/base/core.c:3510\n(inlined by) device_add at drivers/base/core.c:3561\n\nBalance device refcount by issuing a put_device() on devices found via\ndevice_find_child().(CVE-2025-37905)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: avoid NULL pointer dereference in skb_dequeue()\n\nA NULL pointer dereference can occur in skb_dequeue() when processing a\nQCA firmware crash dump on WCN7851 (0489:e0f3).\n\n[ 93.672166] Bluetooth: hci0: ACL memdump size(589824)\n\n[ 93.672475] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[ 93.672517] Workqueue: hci0 hci_devcd_rx [bluetooth]\n[ 93.672598] RIP: 0010:skb_dequeue+0x50/0x80\n\nThe issue stems from handle_dump_pkt_qca() returning 0 even when a dump\npacket is successfully processed. This is because it incorrectly\nforwards the return value of hci_devcd_init() (which returns 0 on\nsuccess). As a result, the caller (btusb_recv_acl_qca() or\nbtusb_recv_evt_qca()) assumes the packet was not handled and passes it\nto hci_recv_frame(), leading to premature kfree() of the skb.\n\nLater, hci_devcd_rx() attempts to dequeue the same skb from the dump\nqueue, resulting in a NULL pointer dereference.\n\nFix this by:\n1. Making handle_dump_pkt_qca() return 0 on success and negative errno\n   on failure, consistent with kernel conventions.\n2. Splitting dump packet detection into separate functions for ACL\n   and event packets for better structure and readability.\n\nThis ensures dump packets are properly identified and consumed, avoiding\ndouble handling and preventing NULL pointer access.(CVE-2025-37918)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: prevent out-of-bounds stream writes by validating *pos\n\nksmbd_vfs_stream_write() did not validate whether the write offset\n(*pos) was within the bounds of the existing stream data length (v_len).\nIf *pos was greater than or equal to v_len, this could lead to an\nout-of-bounds memory write.\n\nThis patch adds a check to ensure *pos is less than v_len before\nproceeding. If the condition fails, -EINVAL is returned.(CVE-2025-37947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix deadlock\n\nThis patch introduces the ucsi_con_mutex_lock / ucsi_con_mutex_unlock\nfunctions to the UCSI driver. ucsi_con_mutex_lock ensures the connector\nmutex is only locked if a connection is established and the partner pointer\nis valid. This resolves a deadlock scenario where\nucsi_displayport_remove_partner holds con-\u0026gt;mutex waiting for\ndp_altmode_work to complete while dp_altmode_work attempts to acquire it.(CVE-2025-37967)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Refactor remove call with idxd_cleanup() helper\n\nThe idxd_cleanup() helper cleans up perfmon, interrupts, internals and\nso on. Refactor remove call with the idxd_cleanup() helper to avoid code\nduplication. Note, this also fixes the missing put_device() for idxd\ngroups, enginces and wqs.(CVE-2025-38014)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: Annotate FDB data races\n\nThe \u0026apos;used\u0026apos; and \u0026apos;updated\u0026apos; fields in the FDB entry structure can be\naccessed concurrently by multiple threads, leading to reports such as\n[1]. Can be reproduced using [2].\n\nSuppress these reports by annotating these accesses using\nREAD_ONCE() / WRITE_ONCE().\n\n[1]\nBUG: KCSAN: data-race in vxlan_xmit / vxlan_xmit\n\nwrite to 0xffff942604d263a8 of 8 bytes by task 286 on cpu 0:\n vxlan_xmit+0xb29/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff942604d263a8 of 8 bytes by task 287 on cpu 2:\n vxlan_xmit+0xadf/0x2380\n dev_hard_start_xmit+0x84/0x2f0\n __dev_queue_xmit+0x45a/0x1650\n packet_xmit+0x100/0x150\n packet_sendmsg+0x2114/0x2ac0\n __sys_sendto+0x318/0x330\n __x64_sys_sendto+0x76/0x90\n x64_sys_call+0x14e8/0x1c00\n do_syscall_64+0x9e/0x1a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nvalue changed: 0x00000000fffbac6e -\u0026gt; 0x00000000fffbac6f\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 2 UID: 0 PID: 287 Comm: mausezahn Not tainted 6.13.0-rc7-01544-gb4b270f11a02 #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014\n\n[2]\n #!/bin/bash\n\n set +H\n echo whitelist \u0026gt; /sys/kernel/debug/kcsan\n echo !vxlan_xmit \u0026gt; /sys/kernel/debug/kcsan\n\n ip link add name vx0 up type vxlan id 10010 dstport 4789 local 192.0.2.1\n bridge fdb add 00:11:22:33:44:55 dev vx0 self static dst 198.51.100.1\n taskset -c 0 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;\n taskset -c 2 mausezahn vx0 -a own -b 00:11:22:33:44:55 -c 0 -q \u0026amp;(CVE-2025-38037)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_ffa: Set dma_mask for ffa devices\n\nSet dma_mask for FFA devices, otherwise DMA allocation using the device pointer\nlead to following warning:\n\nWARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dma_alloc_attrs+0xe0/0x124(CVE-2025-38043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix use-after-free in cifs_fill_dirent\n\nThere is a race condition in the readdir concurrency process, which may\naccess the rsp buffer after it has been released, triggering the\nfollowing KASAN warning.\n\n ==================================================================\n BUG: KASAN: slab-use-after-free in cifs_fill_dirent+0xb03/0xb60 [cifs]\n Read of size 4 at addr ffff8880099b819c by task a.out/342975\n\n CPU: 2 UID: 0 PID: 342975 Comm: a.out Not tainted 6.15.0-rc6+ #240 PREEMPT(full)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x53/0x70\n  print_report+0xce/0x640\n  kasan_report+0xb8/0xf0\n  cifs_fill_dirent+0xb03/0xb60 [cifs]\n  cifs_readdir+0x12cb/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f996f64b9f9\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89\n f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01\n f0 ff ff  0d f7 c3 0c 00 f7 d8 64 89 8\n RSP: 002b:00007f996f53de78 EFLAGS: 00000207 ORIG_RAX: 000000000000004e\n RAX: ffffffffffffffda RBX: 00007f996f53ecdc RCX: 00007f996f64b9f9\n RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\n RBP: 00007f996f53dea0 R08: 0000000000000000 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000207 R12: ffffffffffffff88\n R13: 0000000000000000 R14: 00007ffc8cd9a500 R15: 00007f996f51e000\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 408:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  __kasan_slab_alloc+0x6e/0x70\n  kmem_cache_alloc_noprof+0x117/0x3d0\n  mempool_alloc_noprof+0xf2/0x2c0\n  cifs_buf_get+0x36/0x80 [cifs]\n  allocate_buffers+0x1d2/0x330 [cifs]\n  cifs_demultiplex_thread+0x22b/0x2690 [cifs]\n  kthread+0x394/0x720\n  ret_from_fork+0x34/0x70\n  ret_from_fork_asm+0x1a/0x30\n\n Freed by task 342979:\n  kasan_save_stack+0x20/0x40\n  kasan_save_track+0x14/0x30\n  kasan_save_free_info+0x3b/0x60\n  __kasan_slab_free+0x37/0x50\n  kmem_cache_free+0x2b8/0x500\n  cifs_buf_release+0x3c/0x70 [cifs]\n  cifs_readdir+0x1c97/0x3190 [cifs]\n  iterate_dir+0x1a1/0x520\n  __x64_sys_getdents64+0x134/0x220\n  do_syscall_64+0x4b/0x110\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n The buggy address belongs to the object at ffff8880099b8000\n  which belongs to the cache cifs_request of size 16588\n The buggy address is located 412 bytes inside of\n  freed 16588-byte region [ffff8880099b8000, ffff8880099bc0cc)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99b8\n head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n anon flags: 0x80000000000040(head|node=0|zone=1)\n page_type: f5(slab)\n raw: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n raw: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000040 ffff888001e03400 0000000000000000 dead000000000001\n head: 0000000000000000 0000000000010001 00000000f5000000 0000000000000000\n head: 0080000000000003 ffffea0000266e01 00000000ffffffff 00000000ffffffff\n head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffff8880099b8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n \u0026gt;ffff8880099b8180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                             ^\n  ffff8880099b8200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n  ffff8880099b8280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n ==================================================================\n\nPOC is available in the link [1].\n\nThe problem triggering process is as follows:\n\nProcess 1                       Process 2\n-----------------------------------\n---truncated---(CVE-2025-38051)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n\tInvalid read at addr 0x102877002, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\tInvalid write at addr 0x102877A44, size 2, region \u0026apos;(null)\u0026apos;, reason: rejected\n\t...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.(CVE-2025-38064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: CPPC: Fix NULL pointer dereference when nosmp is used\n\nWith nosmp in cmdline, other CPUs are not brought up, leaving\ntheir cpc_desc_ptr NULL. CPU0\u0026apos;s iteration via for_each_possible_cpu()\ndereferences these NULL pointers, causing panic.\n\nPanic backtrace:\n\n[    0.401123] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000b8\n...\n[    0.403255] [\u0026lt;ffffffff809a5818\u0026gt;] cppc_allow_fast_switch+0x6a/0xd4\n...\nKernel panic - not syncing: Attempted to kill init!\n\n[ rjw: New subject ](CVE-2025-38113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngve: add missing NULL check for gve_alloc_pending_packet() in TX DQO\n\ngve_alloc_pending_packet() can return NULL, but gve_tx_add_skb_dqo()\ndid not check for this case before dereferencing the returned pointer.\n\nAdd a missing NULL check to prevent a potential NULL pointer\ndereference when allocation fails.\n\nThis improves robustness in low-memory scenarios.(CVE-2025-38122)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: wwan: t7xx: Fix napi rx poll issue\n\nWhen driver handles the napi rx polling requests, the netdev might\nhave been released by the dellink logic triggered by the disconnect\noperation on user plane. However, in the logic of processing skb in\npolling, an invalid netdev is still being used, which causes a panic.\n\nBUG: kernel NULL pointer dereference, address: 00000000000000f1\nOops: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:dev_gro_receive+0x3a/0x620\n[...]\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n ? __die_body+0x68/0xb0\n ? page_fault_oops+0x379/0x3e0\n ? exc_page_fault+0x4f/0xa0\n ? asm_exc_page_fault+0x22/0x30\n ? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]\n ? dev_gro_receive+0x3a/0x620\n napi_gro_receive+0xad/0x170\n t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]\n t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]\n net_rx_action+0x103/0x470\n irq_exit_rcu+0x13a/0x310\n sysvec_apic_timer_interrupt+0x56/0x90\n \u0026lt;/IRQ\u0026gt;(CVE-2025-38123)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: prevent deactivate active config while enabling the config\n\nWhile enable active config via cscfg_csdev_enable_active_config(),\nactive config could be deactivated via configfs\u0026apos; sysfs interface.\nThis could make UAF issue in below scenario:\n\nCPU0                                          CPU1\n(sysfs enable)                                load module\n                                              cscfg_load_config_sets()\n                                              activate config. // sysfs\n                                              (sys_active_cnt == 1)\n...\ncscfg_csdev_enable_active_config()\nlock(csdev-\u0026gt;cscfg_csdev_lock)\n// here load config activate by CPU1\nunlock(csdev-\u0026gt;cscfg_csdev_lock)\n\n                                              deactivate config // sysfs\n                                              (sys_activec_cnt == 0)\n                                              cscfg_unload_config_sets()\n                                              unload module\n\n// access to config_desc which freed\n// while unloading module.\ncscfg_csdev_enable_config\n\nTo address this, use cscfg_config_desc\u0026apos;s active_cnt as a reference count\n which will be holded when\n    - activate the config.\n    - enable the activated config.\nand put the module reference when config_active_cnt == 0.(CVE-2025-38131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: mscc: Fix memory leak when using one step timestamping\n\nFix memory leak when running one-step timestamping. When running\none-step sync timestamping, the HW is configured to insert the TX time\ninto the frame, so there is no reason to keep the skb anymore. As in\nthis case the HW will never generate an interrupt to say that the frame\nwas timestamped, then the frame will never released.\nFix this by freeing the frame in case of one-step timestamping.(CVE-2025-38148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix error flow upon firmware failure for RQ destruction\n\nUpon RQ destruction if the firmware command fails which is the\nlast resource to be destroyed some SW resources were already cleaned\nregardless of the failure.\n\nNow properly rollback the object to its original state upon such failure.\n\nIn order to avoid a use-after free in case someone tries to destroy the\nobject again, which results in the following kernel trace:\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 0 PID: 37589 at lib/refcount.c:28 refcount_warn_saturate+0xf4/0x148\nModules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) rfkill mlx5_core(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) psample mlxfw(OE) mlx_compat(OE) macsec tls pci_hyperv_intf sunrpc vfat fat virtio_net net_failover failover fuse loop nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_console virtio_gpu virtio_blk virtio_dma_buf virtio_mmio dm_mirror dm_region_hash dm_log dm_mod xpmem(OE)\nCPU: 0 UID: 0 PID: 37589 Comm: python3 Kdump: loaded Tainted: G           OE     -------  ---  6.12.0-54.el10.aarch64 #1\nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\nHardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : refcount_warn_saturate+0xf4/0x148\nlr : refcount_warn_saturate+0xf4/0x148\nsp : ffff80008b81b7e0\nx29: ffff80008b81b7e0 x28: ffff000133d51600 x27: 0000000000000001\nx26: 0000000000000000 x25: 00000000ffffffea x24: ffff00010ae80f00\nx23: ffff00010ae80f80 x22: ffff0000c66e5d08 x21: 0000000000000000\nx20: ffff0000c66e0000 x19: ffff00010ae80340 x18: 0000000000000006\nx17: 0000000000000000 x16: 0000000000000020 x15: ffff80008b81b37f\nx14: 0000000000000000 x13: 2e656572662d7265 x12: ffff80008283ef78\nx11: ffff80008257efd0 x10: ffff80008283efd0 x9 : ffff80008021ed90\nx8 : 0000000000000001 x7 : 00000000000bffe8 x6 : c0000000ffff7fff\nx5 : ffff0001fb8e3408 x4 : 0000000000000000 x3 : ffff800179993000\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000133d51600\nCall trace:\n refcount_warn_saturate+0xf4/0x148\n mlx5_core_put_rsc+0x88/0xa0 [mlx5_ib]\n mlx5_core_destroy_rq_tracked+0x64/0x98 [mlx5_ib]\n mlx5_ib_destroy_wq+0x34/0x80 [mlx5_ib]\n ib_destroy_wq_user+0x30/0xc0 [ib_core]\n uverbs_free_wq+0x28/0x58 [ib_uverbs]\n destroy_hw_idr_uobject+0x34/0x78 [ib_uverbs]\n uverbs_destroy_uobject+0x48/0x240 [ib_uverbs]\n __uverbs_cleanup_ufile+0xd4/0x1a8 [ib_uverbs]\n uverbs_destroy_ufile_hw+0x48/0x120 [ib_uverbs]\n ib_uverbs_close+0x2c/0x100 [ib_uverbs]\n __fput+0xd8/0x2f0\n __fput_sync+0x50/0x70\n __arm64_sys_close+0x40/0x90\n invoke_syscall.constprop.0+0x74/0xd0\n do_el0_svc+0x48/0xe8\n el0_svc+0x44/0x1d0\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x1a4/0x1a8(CVE-2025-38161)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()\n\nBefore calling lan743x_ptp_io_event_clock_get(), the \u0026apos;channel\u0026apos; value\nis checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8).\nThis seems correct and aligns with the PTP interrupt status register\n(PTP_INT_STS) specifications.\n\nHowever, lan743x_ptp_io_event_clock_get() writes to ptp-\u0026gt;extts[] with\nonly LAN743X_PTP_N_EXTTS(4) elements, using channel as an index:\n\n    lan743x_ptp_io_event_clock_get(..., u8 channel,...)\n    {\n        ...\n        /* Update Local timestamp */\n        extts = \u0026amp;ptp-\u0026gt;extts[channel];\n        extts-\u0026gt;ts.tv_sec = sec;\n        ...\n    }\n\nTo avoid an out-of-bounds write and utilize all the supported GPIO\ninputs, set LAN743X_PTP_N_EXTTS to 8.\n\nDetected using the static analysis tool - Svace.(CVE-2025-38183)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: sch_sfq: reject invalid perturb period\n\nGerrard Tai reported that SFQ perturb_period has no range check yet,\nand this can be used to trigger a race condition fixed in a separate patch.\n\nWe want to make sure ctl-\u0026gt;perturb_period * HZ will not overflow\nand is positive.\n\n\ntc qd add dev lo root sfq perturb -10   # negative value : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 1000000000 # too big : error\nError: sch_sfq: invalid perturb period.\n\ntc qd add dev lo root sfq perturb 2000000 # acceptable value\ntc -s -d qd sh dev lo\nqdisc sfq 8005: root refcnt 2 limit 127p quantum 64Kb depth 127 flows 128 divisor 1024 perturb 2000000sec\n Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)\n backlog 0b 0p requeues 0(CVE-2025-38193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njffs2: check that raw node were preallocated before writing summary\n\nSyzkaller detected a kernel bug in jffs2_link_node_ref, caused by fault\ninjection in jffs2_prealloc_raw_node_refs. jffs2_sum_write_sumnode doesn\u0026apos;t\ncheck return value of jffs2_prealloc_raw_node_refs and simply lets any\nerror propagate into jffs2_sum_write_data, which eventually calls\njffs2_link_node_ref in order to link the summary to an expectedly allocated\nnode.\n\nkernel BUG at fs/jffs2/nodelist.c:592!\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 31277 Comm: syz-executor.7 Not tainted 6.1.128-syzkaller-00139-ge10f83ca10a1 #0\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:jffs2_link_node_ref+0x570/0x690 fs/jffs2/nodelist.c:592\nCall Trace:\n \u0026lt;TASK\u0026gt;\n jffs2_sum_write_data fs/jffs2/summary.c:841 [inline]\n jffs2_sum_write_sumnode+0xd1a/0x1da0 fs/jffs2/summary.c:874\n jffs2_do_reserve_space+0xa18/0xd60 fs/jffs2/nodemgmt.c:388\n jffs2_reserve_space+0x55f/0xaa0 fs/jffs2/nodemgmt.c:197\n jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362\n jffs2_write_end+0x726/0x15d0 fs/jffs2/file.c:301\n generic_perform_write+0x314/0x5d0 mm/filemap.c:3856\n __generic_file_write_iter+0x2ae/0x4d0 mm/filemap.c:3973\n generic_file_write_iter+0xe3/0x350 mm/filemap.c:4005\n call_write_iter include/linux/fs.h:2265 [inline]\n do_iter_readv_writev+0x20f/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10c/0x170 fs/splice.c:950\n splice_direct_to_actor+0x337/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nFix this issue by checking return value of jffs2_prealloc_raw_node_refs\nbefore calling jffs2_sum_write_data.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2025-38194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem, swap: fix softlockup with mTHP swapin\n\nFollowing softlockup can be easily reproduced on my test machine with:\n\necho always \u0026gt; /sys/kernel/mm/transparent_hugepage/hugepages-64kB/enabled\nswapon /dev/zram0 # zram0 is a 48G swap device\nmkdir -p /sys/fs/cgroup/memory/test\necho 1G \u0026gt; /sys/fs/cgroup/test/memory.max\necho $BASHPID \u0026gt; /sys/fs/cgroup/test/cgroup.procs\nwhile true; do\n    dd if=/dev/zero of=/tmp/test.img bs=1M count=5120\n    cat /tmp/test.img \u0026gt; /dev/null\n    rm /tmp/test.img\ndone\n\nThen after a while:\nwatchdog: BUG: soft lockup - CPU#0 stuck for 763s! [cat:5787]\nModules linked in: zram virtiofs\nCPU: 0 UID: 0 PID: 5787 Comm: cat Kdump: loaded Tainted: G             L      6.15.0.orig-gf3021d9246bc-dirty #118 PREEMPT(voluntary)·\nTainted: [L]=SOFTLOCKUP\nHardware name: Red Hat KVM/RHEL-AV, BIOS 0.0.0 02/06/2015\nRIP: 0010:mpol_shared_policy_lookup+0xd/0x70\nCode: e9 b8 b4 ff ff 31 c0 c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 41 54 55 53 \u0026lt;48\u0026gt; 8b 1f 48 85 db 74 41 4c 8d 67 08 48 89 fb 48 89 f5 4c 89 e7 e8\nRSP: 0018:ffffc90002b1fc28 EFLAGS: 00000202\nRAX: 00000000001c20ca RBX: 0000000000724e1e RCX: 0000000000000001\nRDX: ffff888118e214c8 RSI: 0000000000057d42 RDI: ffff888118e21518\nRBP: 000000000002bec8 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000bf4 R11: 0000000000000000 R12: 0000000000000001\nR13: 00000000001c20ca R14: 00000000001c20ca R15: 0000000000000000\nFS:  00007f03f995c740(0000) GS:ffff88a07ad9a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f03f98f1000 CR3: 0000000144626004 CR4: 0000000000770eb0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n shmem_alloc_folio+0x31/0xc0\n shmem_swapin_folio+0x309/0xcf0\n ? filemap_get_entry+0x117/0x1e0\n ? xas_load+0xd/0xb0\n ? filemap_get_entry+0x101/0x1e0\n shmem_get_folio_gfp+0x2ed/0x5b0\n shmem_file_read_iter+0x7f/0x2e0\n vfs_read+0x252/0x330\n ksys_read+0x68/0xf0\n do_syscall_64+0x4c/0x1c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7f03f9a46991\nCode: 00 48 8b 15 81 14 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d 35 97 10 00 00 74 13 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec\nRSP: 002b:00007fff3c52bd28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007f03f9a46991\nRDX: 0000000000040000 RSI: 00007f03f98ba000 RDI: 0000000000000003\nRBP: 00007fff3c52bd50 R08: 0000000000000000 R09: 00007f03f9b9a380\nR10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000\nR13: 00007f03f98ba000 R14: 0000000000000003 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\n\nThe reason is simple, readahead brought some order 0 folio in swap cache,\nand the swapin mTHP folio being allocated is in conflict with it, so\nswapcache_prepare fails and causes shmem_swap_alloc_folio to return\n-EEXIST, and shmem simply retries again and again causing this loop.\n\nFix it by applying a similar fix for anon mTHP swapin.\n\nThe performance change is very slight, time of swapin 10g zero folios\nwith shmem (test for 12 times):\nBefore:  2.47s\nAfter:   2.48s\n\n[(CVE-2025-38241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlib/group_cpus: fix NULL pointer dereference from group_cpus_evenly()\n\nWhile testing null_blk with configfs, echo 0 \u0026gt; poll_queues will trigger\nfollowing panic:\n\nBUG: kernel NULL pointer dereference, address: 0000000000000010\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 27 UID: 0 PID: 920 Comm: bash Not tainted 6.15.0-02023-gadbdb95c8696-dirty #1238 PREEMPT(undef)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014\nRIP: 0010:__bitmap_or+0x48/0x70\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __group_cpus_evenly+0x822/0x8c0\n group_cpus_evenly+0x2d9/0x490\n blk_mq_map_queues+0x1e/0x110\n null_map_queues+0xc9/0x170 [null_blk]\n blk_mq_update_queue_map+0xdb/0x160\n blk_mq_update_nr_hw_queues+0x22b/0x560\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_poll_queues_store+0xa4/0x130 [null_blk]\n configfs_write_iter+0x109/0x1d0\n vfs_write+0x26e/0x6f0\n ksys_write+0x79/0x180\n __x64_sys_write+0x1d/0x30\n x64_sys_call+0x45c4/0x45f0\n do_syscall_64+0xa5/0x240\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nRoot cause is that numgrps is set to 0, and ZERO_SIZE_PTR is returned from\nkcalloc(), and later ZERO_SIZE_PTR will be deferenced.\n\nFix the problem by checking numgrps first in group_cpus_evenly(), and\nreturn NULL directly if numgrps is zero.\n\n[(CVE-2025-38255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Fix NULL pointer deference on eir_get_service_data\n\nThe len parameter is considered optional so it can be NULL so it cannot\nbe used for skipping to next entry of EIR_SERVICE_DATA.(CVE-2025-38304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: avs: Verify content returned by parse_int_array()\n\nThe first element of the returned array stores its length. If it is 0,\nany manipulation beyond the element at index 0 ends with null-ptr-deref.(CVE-2025-38307)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: Log an error when close_all_cached_dirs fails\n\nUnder low-memory conditions, close_all_cached_dirs() can\u0026apos;t move the\ndentries to a separate list to dput() them once the locks are dropped.\nThis will result in a \u0026quot;Dentry still in use\u0026quot; error, so add an error\nmessage that makes it clear this is what happened:\n\n[  495.281119] CIFS: VFS: \\\\otters.example.com\\share Out of memory while dropping dentries\n[  495.281595] ------------[ cut here ]------------\n[  495.281887] BUG: Dentry ffff888115531138{i=78,n=/}  still in use (2) [unmount of cifs cifs]\n[  495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0\n\nAlso, bail out of looping through all tcons as soon as a single\nallocation fails, since we\u0026apos;re already in trouble, and kmalloc() attempts\nfor subseqeuent tcons are likely to fail just like the first one did.(CVE-2025-38321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: fix acpi parse and parseext cache leaks\n\nACPICA commit 8829e70e1360c81e7a5a901b5d4f48330e021ea5\n\nI\u0026apos;m Seunghun Han, and I work for National Security Research Institute of\nSouth Korea.\n\nI have been doing a research on ACPI and found an ACPI cache leak in ACPI\nearly abort cases.\n\nBoot log of ACPI cache leak is as follows:\n[    0.352414] ACPI: Added _OSI(Module Device)\n[    0.353182] ACPI: Added _OSI(Processor Device)\n[    0.353182] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.353182] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.356028] ACPI: Unable to start the ACPI Interpreter\n[    0.356799] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.360215] kmem_cache_destroy Acpi-State: Slab cache still has objects\n[    0.360648] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #10\n[    0.361273] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.361873] Call Trace:\n[    0.362243]  ? dump_stack+0x5c/0x81\n[    0.362591]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.362944]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.363296]  ? acpi_os_delete_cache+0xa/0x10\n[    0.363646]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.364000]  ? acpi_terminate+0xa/0x14\n[    0.364000]  ? acpi_init+0x2af/0x34f\n[    0.364000]  ? __class_create+0x4c/0x80\n[    0.364000]  ? video_setup+0x7f/0x7f\n[    0.364000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.364000]  ? do_one_initcall+0x4e/0x1a0\n[    0.364000]  ? kernel_init_freeable+0x189/0x20a\n[    0.364000]  ? rest_init+0xc0/0xc0\n[    0.364000]  ? kernel_init+0xa/0x100\n[    0.364000]  ? ret_from_fork+0x25/0x30\n\nI analyzed this memory leak in detail. I found that “Acpi-State” cache and\n“Acpi-Parse” cache were merged because the size of cache objects was same\nslab cache size.\n\nI finally found “Acpi-Parse” cache and “Acpi-parse_ext” cache were leaked\nusing SLAB_NEVER_MERGE flag in kmem_cache_create() function.\n\nReal ACPI cache leak point is as follows:\n[    0.360101] ACPI: Added _OSI(Module Device)\n[    0.360101] ACPI: Added _OSI(Processor Device)\n[    0.360101] ACPI: Added _OSI(3.0 _SCP Extensions)\n[    0.361043] ACPI: Added _OSI(Processor Aggregator Device)\n[    0.364016] ACPI: Unable to start the ACPI Interpreter\n[    0.365061] ACPI Error: Could not remove SCI handler (20170303/evmisc-281)\n[    0.368174] kmem_cache_destroy Acpi-Parse: Slab cache still has objects\n[    0.369332] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.371256] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.372000] Call Trace:\n[    0.372000]  ? dump_stack+0x5c/0x81\n[    0.372000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.372000]  ? acpi_ut_delete_caches+0x56/0x7b\n[    0.372000]  ? acpi_terminate+0xa/0x14\n[    0.372000]  ? acpi_init+0x2af/0x34f\n[    0.372000]  ? __class_create+0x4c/0x80\n[    0.372000]  ? video_setup+0x7f/0x7f\n[    0.372000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.372000]  ? do_one_initcall+0x4e/0x1a0\n[    0.372000]  ? kernel_init_freeable+0x189/0x20a\n[    0.372000]  ? rest_init+0xc0/0xc0\n[    0.372000]  ? kernel_init+0xa/0x100\n[    0.372000]  ? ret_from_fork+0x25/0x30\n[    0.388039] kmem_cache_destroy Acpi-parse_ext: Slab cache still has objects\n[    0.389063] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W\n4.12.0-rc4-next-20170608+ #8\n[    0.390557] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS\nvirtual_box 12/01/2006\n[    0.392000] Call Trace:\n[    0.392000]  ? dump_stack+0x5c/0x81\n[    0.392000]  ? kmem_cache_destroy+0x1aa/0x1c0\n[    0.392000]  ? acpi_sleep_proc_init+0x27/0x27\n[    0.392000]  ? acpi_os_delete_cache+0xa/0x10\n[    0.392000]  ? acpi_ut_delete_caches+0x6d/0x7b\n[    0.392000]  ? acpi_terminate+0xa/0x14\n[    0.392000]  ? acpi_init+0x2af/0x3\n---truncated---(CVE-2025-38344)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmaple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate()\n\nTemporarily clear the preallocation flag when explicitly requesting\nallocations.  Pre-existing allocations are already counted against the\nrequest through mas_node_count_gfp(), but the allocations will not happen\nif the MA_STATE_PREALLOC flag is set.  This flag is meant to avoid\nre-allocating in bulk allocation mode, and to detect issues with\npreallocation calculations.\n\nThe MA_STATE_PREALLOC flag should also always be set on zero allocations\nso that detection of underflow allocations will print a WARN_ON() during\nconsumption.\n\nUser visible effect of this flaw is a WARN_ON() followed by a null pointer\ndereference when subsequent requests for larger number of nodes is\nignored, such as the vma merge retry in mmap_region() caused by drivers\naltering the vma flags (which happens in v6.6, at least)(CVE-2025-38364)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_* TOCTOU\n\nTransport assignment may race with module unload. Protect new_transport\nfrom becoming a stale pointer.\n\nThis also takes care of an insecure call in vsock_use_local_transport();\nadd a lockdep assert.\n\nBUG: unable to handle page fault for address: fffffbfff8056000\nOops: Oops: 0000 [#1] SMP KASAN\nRIP: 0010:vsock_assign_transport+0x366/0x600\nCall Trace:\n vsock_connect+0x59c/0xc40\n __sys_connect+0xe8/0x100\n __x64_sys_connect+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38461)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock: Fix transport_{g2h,h2g} TOCTOU\n\nvsock_find_cid() and vsock_dev_do_ioctl() may race with module unload.\ntransport_{g2h,h2g} may become NULL after the NULL check.\n\nIntroduce vsock_transport_local_cid() to protect from a potential\nnull-ptr-deref.\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_find_cid+0x47/0x90\nCall Trace:\n __vsock_bind+0x4b2/0x720\n vsock_bind+0x90/0xe0\n __sys_bind+0x14d/0x1e0\n __x64_sys_bind+0x6e/0xc0\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nKASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f]\nRIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0\nCall Trace:\n __x64_sys_ioctl+0x12d/0x190\n do_syscall_64+0x92/0x1c0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-38462)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in crypt_message when using async crypto\n\nThe CVE-2024-50047 fix removed asynchronous crypto handling from\ncrypt_message(), assuming all crypto operations are synchronous.\nHowever, when hardware crypto accelerators are used, this can cause\nuse-after-free crashes:\n\n  crypt_message()\n    // Allocate the creq buffer containing the req\n    creq = smb2_get_aead_req(..., \u0026amp;req);\n\n    // Async encryption returns -EINPROGRESS immediately\n    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);\n\n    // Free creq while async operation is still in progress\n    kvfree_sensitive(creq, ...);\n\nHardware crypto modules often implement async AEAD operations for\nperformance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,\nthe operation completes asynchronously. Without crypto_wait_req(),\nthe function immediately frees the request buffer, leading to crashes\nwhen the driver later accesses the freed memory.\n\nThis results in a use-after-free condition when the hardware crypto\ndriver later accesses the freed request structure, leading to kernel\ncrashes with NULL pointer dereferences.\n\nThe issue occurs because crypto_alloc_aead() with mask=0 doesn\u0026apos;t\nguarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in\nthe mask, async implementations can be selected.\n\nFix by restoring the async crypto handling:\n- DECLARE_CRYPTO_WAIT(wait) for completion tracking\n- aead_request_set_callback() for async completion notification\n- crypto_wait_req() to wait for operation completion\n\nThis ensures the request buffer isn\u0026apos;t freed until the crypto operation\ncompletes, whether synchronous or asynchronous, while preserving the\nCVE-2024-50047 fix.(CVE-2025-38488)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns\n\nWhat we want is to verify there is that clone won\u0026apos;t expose something\nhidden by a mount we wouldn\u0026apos;t be able to undo.  \u0026quot;Wouldn\u0026apos;t be able to undo\u0026quot;\nmay be a result of MNT_LOCKED on a child, but it may also come from\nlacking admin rights in the userns of the namespace mount belongs to.\n\nclone_private_mnt() checks the former, but not the latter.\n\nThere\u0026apos;s a number of rather confusing CAP_SYS_ADMIN checks in various\nuserns during the mount, especially with the new mount API; they serve\ndifferent purposes and in case of clone_private_mnt() they usually,\nbut not always end up covering the missing check mentioned above.(CVE-2025-38499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n\u0026apos;socket state prevent any additional subflow creation\u0026apos; protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field \u0026apos;allow_infinite_fallback\u0026apos; is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write.(CVE-2025-38552)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: use aead_request_free to match aead_request_alloc\n\nUse aead_request_free() instead of kfree() to properly free memory\nallocated by aead_request_alloc(). This ensures sensitive crypto data\nis zeroed before being freed.(CVE-2025-38575)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Check governor before using governor-\u0026gt;name\n\nCommit 96ffcdf239de (\u0026quot;PM / devfreq: Remove redundant governor_name from\nstruct devfreq\u0026quot;) removes governor_name and uses governor-\u0026gt;name to replace\nit. But devfreq-\u0026gt;governor may be NULL and directly using\ndevfreq-\u0026gt;governor-\u0026gt;name may cause null pointer exception. Move the check of\ngovernor to before using governor-\u0026gt;name.(CVE-2025-38609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: fix refcount leak on table dump\n\nThere is a reference count leak in ctnetlink_dump_table():\n      if (res \u0026lt; 0) {\n                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general); // HERE\n                cb-\u0026gt;args[1] = (unsigned long)ct;\n                ...\n\nWhile its very unlikely, its possible that ct == last.\nIf this happens, then the refcount of ct was already incremented.\nThis 2nd increment is never undone.\n\nThis prevents the conntrack object from being released, which in turn\nkeeps prevents cnet-\u0026gt;count from dropping back to 0.\n\nThis will then block the netns dismantle (or conntrack rmmod) as\nnf_conntrack_cleanup_net_list() will wait forever.\n\nThis can be reproduced by running conntrack_resize.sh selftest in a loop.\nIt takes ~20 minutes for me on a preemptible kernel on average before\nI see a runaway kworker spinning in nf_conntrack_cleanup_net_list.\n\nOne fix would to change this to:\n        if (res \u0026lt; 0) {\n\t\tif (ct != last)\n\t                nf_conntrack_get(\u0026amp;ct-\u0026gt;ct_general);\n\nBut this reference counting isn\u0026apos;t needed in the first place.\nWe can just store a cookie value instead.\n\nA followup patch will do the same for ctnetlink_exp_dump_table,\nit looks to me as if this has the same problem and like\nctnetlink_dump_table, we only need a \u0026apos;skip hint\u0026apos;, not the actual\nobject so we can apply the same cookie strategy there as well.(CVE-2025-38721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla4xxx: Prevent a potential error pointer dereference\n\nThe qla4xxx_get_ep_fwdb() function is supposed to return NULL on error,\nbut qla4xxx_ep_connect() returns error pointers.  Propagating the error\npointers will lead to an Oops in the caller, so change the error pointers\nto NULL.(CVE-2025-39676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don\u0026apos;t know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don\u0026apos;t have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it\u0026apos;s\nzero length.(CVE-2025-39682)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: Fix MAC comparison to be constant-time\n\nTo prevent timing attacks, MACs need to be compared in constant time.\nUse the appropriate helper function for this.(CVE-2025-39702)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclk: samsung: Fix UBSAN panic in samsung_clk_init()\n\nWith UBSAN_ARRAY_BOUNDS=y, I\u0026apos;m hitting the below panic due to\ndereferencing `ctx-\u0026gt;clk_data.hws` before setting\n`ctx-\u0026gt;clk_data.num = nr_clks`. Move that up to fix the crash.\n\n  UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP\n  \u0026lt;snip\u0026gt;\n  Call trace:\n   samsung_clk_init+0x110/0x124 (P)\n   samsung_clk_init+0x48/0x124 (L)\n   samsung_cmu_register_one+0x3c/0xa0\n   exynos_arm64_register_cmu+0x54/0x64\n   __gs101_cmu_top_of_clk_init_declare+0x28/0x60\n   ...(CVE-2025-39728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: Prevent file descriptor table allocations exceeding INT_MAX\n\nWhen sysctl_nr_open is set to a very high value (for example, 1073741816\nas set by systemd), processes attempting to use file descriptors near\nthe limit can trigger massive memory allocation attempts that exceed\nINT_MAX, resulting in a WARNING in mm/slub.c:\n\n  WARNING: CPU: 0 PID: 44 at mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288\n\nThis happens because kvmalloc_array() and kvmalloc() check if the\nrequested size exceeds INT_MAX and emit a warning when the allocation is\nnot flagged with __GFP_NOWARN.\n\nSpecifically, when nr_open is set to 1073741816 (0x3ffffff8) and a\nprocess calls dup2(oldfd, 1073741880), the kernel attempts to allocate:\n- File descriptor array: 1073741880 * 8 bytes = 8,589,935,040 bytes\n- Multiple bitmaps: ~400MB\n- Total allocation size: \u0026gt; 8GB (exceeding INT_MAX = 2,147,483,647)\n\nReproducer:\n1. Set /proc/sys/fs/nr_open to 1073741816:\n   # echo 1073741816 \u0026gt; /proc/sys/fs/nr_open\n\n2. Run a program that uses a high file descriptor:\n   #include \u0026lt;unistd.h\u0026gt;\n   #include \u0026lt;sys/resource.h\u0026gt;\n\n   int main() {\n       struct rlimit rlim = {1073741824, 1073741824};\n       setrlimit(RLIMIT_NOFILE, \u0026amp;rlim);\n       dup2(2, 1073741880);  // Triggers the warning\n       return 0;\n   }\n\n3. Observe WARNING in dmesg at mm/slub.c:5027\n\nsystemd commit a8b627a introduced automatic bumping of fs.nr_open to the\nmaximum possible value. The rationale was that systems with memory\ncontrol groups (memcg) no longer need separate file descriptor limits\nsince memory is properly accounted. However, this change overlooked\nthat:\n\n1. The kernel\u0026apos;s allocation functions still enforce INT_MAX as a maximum\n   size regardless of memcg accounting\n2. Programs and tests that legitimately test file descriptor limits can\n   inadvertently trigger massive allocations\n3. The resulting allocations (\u0026gt;8GB) are impractical and will always fail\n\nsystemd\u0026apos;s algorithm starts with INT_MAX and keeps halving the value\nuntil the kernel accepts it. On most systems, this results in nr_open\nbeing set to 1073741816 (0x3ffffff8), which is just under 1GB of file\ndescriptors.\n\nWhile processes rarely use file descriptors near this limit in normal\noperation, certain selftests (like\ntools/testing/selftests/core/unshare_test.c) and programs that test file\ndescriptor limits can trigger this issue.\n\nFix this by adding a check in alloc_fdtable() to ensure the requested\nallocation size does not exceed INT_MAX. This causes the operation to\nfail with -EMFILE instead of triggering a kernel warning and avoids the\nimpractical \u0026gt;8GB memory allocation request.(CVE-2025-39756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM\n\nWhen performing Generic Segmentation Offload (GSO) on an IPv6 packet that\ncontains extension headers, the kernel incorrectly requests checksum offload\nif the egress device only advertises NETIF_F_IPV6_CSUM feature, which has\na strict contract: it supports checksum offload only for plain TCP or UDP\nover IPv6 and explicitly does not support packets with extension headers.\nThe current GSO logic violates this contract by failing to disable the feature\nfor packets with extension headers, such as those used in GREoIPv6 tunnels.\n\nThis violation results in the device being asked to perform an operation\nit cannot support, leading to a `skb_warn_bad_offload` warning and a collapse\nof network throughput. While device TSO/USO is correctly bypassed in favor\nof software GSO for these packets, the GSO stack must be explicitly told not\nto request checksum offload.\n\nMask NETIF_F_IPV6_CSUM, NETIF_F_TSO6 and NETIF_F_GSO_UDP_L4\nin gso_features_check if the IPv6 header contains extension headers to compute\nchecksum in software.\n\nThe exception is a BIG TCP extension, which, as stated in commit\n68e068cabd2c6c53 (\u0026quot;net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets\u0026quot;):\n\u0026quot;The feature is only enabled on devices that support BIG TCP TSO.\nThe header is only present for PF_PACKET taps like tcpdump,\nand not transmitted by physical devices.\u0026quot;\n\nkernel log output (truncated):\nWARNING: CPU: 1 PID: 5273 at net/core/dev.c:3535 skb_warn_bad_offload+0x81/0x140\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_checksum_help+0x12a/0x1f0\n validate_xmit_skb+0x1a3/0x2d0\n validate_xmit_skb_list+0x4f/0x80\n sch_direct_xmit+0x1a2/0x380\n __dev_xmit_skb+0x242/0x670\n __dev_queue_xmit+0x3fc/0x7f0\n ip6_finish_output2+0x25e/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_tnl_xmit+0x608/0xc00 [ip6_tunnel]\n ip6gre_tunnel_xmit+0x1c0/0x390 [ip6_gre]\n dev_hard_start_xmit+0x63/0x1c0\n __dev_queue_xmit+0x6d0/0x7f0\n ip6_finish_output2+0x214/0x5d0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n ip6_finish_output+0x1fc/0x3f0\n ip6_xmit+0x2ca/0x6f0\n inet6_csk_xmit+0xeb/0x150\n __tcp_transmit_skb+0x555/0xa80\n tcp_write_xmit+0x32a/0xe90\n tcp_sendmsg_locked+0x437/0x1110\n tcp_sendmsg+0x2f/0x50\n...\nskb linear:   00000000: e4 3d 1a 7d ec 30 e4 3d 1a 7e 5d 90 86 dd 60 0e\nskb linear:   00000010: 00 0a 1b 34 3c 40 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000020: 00 00 00 00 00 12 20 11 00 00 00 00 00 00 00 00\nskb linear:   00000030: 00 00 00 00 00 11 2f 00 04 01 04 01 01 00 00 00\nskb linear:   00000040: 86 dd 60 0e 00 0a 1b 00 06 40 20 23 00 00 00 00\nskb linear:   00000050: 00 00 00 00 00 00 00 00 00 12 20 23 00 00 00 00\nskb linear:   00000060: 00 00 00 00 00 00 00 00 00 11 bf 96 14 51 13 f9\nskb linear:   00000070: ae 27 a0 a8 2b e3 80 18 00 40 5b 6f 00 00 01 01\nskb linear:   00000080: 08 0a 42 d4 50 d5 4b 70 f8 1a(CVE-2025-39770)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: initialize more fields in sctp_v6_from_sk()\n\nsyzbot found that sin6_scope_id was not properly initialized,\nleading to undefined behavior.\n\nClear sin6_scope_id and sin6_flowinfo.\n\nBUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649\n  sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983\n  sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390\n  sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452\n  sctp_get_port net/sctp/socket.c:8523 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930\n  x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nLocal variable addr.i.i created at:\n  sctp_get_port net/sctp/socket.c:8515 [inline]\n  sctp_listen_start net/sctp/socket.c:8567 [inline]\n  sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636\n  __sys_listen_socket net/socket.c:1912 [inline]\n  __sys_listen net/socket.c:1927 [inline]\n  __do_sys_listen net/socket.c:1932 [inline]\n  __se_sys_listen net/socket.c:1930 [inline]\n  __x64_sys_listen+0x343/0x4c0 net/socket.c:1930(CVE-2025-39812)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: lpfc: Fix buffer free/clear order in deferred receive path\n\nFix a use-after-free window by correcting the buffer release sequence in\nthe deferred receive path. The code freed the RQ buffer first and only\nthen cleared the context pointer under the lock. Concurrent paths (e.g.,\nABTS and the repost path) also inspect and release the same pointer under\nthe lock, so the old order could lead to double-free/UAF.\n\nNote that the repost path already uses the correct pattern: detach the\npointer under the lock, then free it after dropping the lock. The\ndeferred path should do the same.(CVE-2025-39841)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm\n\nWhen send a broadcast packet to a tap device, which was added to a bridge,\nbr_nf_local_in() is called to confirm the conntrack. If another conntrack\nwith the same hash value is added to the hash table, which can be\ntriggered by a normal packet to a non-bridge device, the below warning\nmay happen.\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 1 PID: 96 at net/bridge/br_netfilter_hooks.c:632 br_nf_local_in+0x168/0x200\n  CPU: 1 UID: 0 PID: 96 Comm: tap_send Not tainted 6.17.0-rc2-dirty #44 PREEMPT(voluntary)\n  RIP: 0010:br_nf_local_in+0x168/0x200\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   nf_hook_slow+0x3e/0xf0\n   br_pass_frame_up+0x103/0x180\n   br_handle_frame_finish+0x2de/0x5b0\n   br_nf_hook_thresh+0xc0/0x120\n   br_nf_pre_routing_finish+0x168/0x3a0\n   br_nf_pre_routing+0x237/0x5e0\n   br_handle_frame+0x1ec/0x3c0\n   __netif_receive_skb_core+0x225/0x1210\n   __netif_receive_skb_one_core+0x37/0xa0\n   netif_receive_skb+0x36/0x160\n   tun_get_user+0xa54/0x10c0\n   tun_chr_write_iter+0x65/0xb0\n   vfs_write+0x305/0x410\n   ksys_write+0x60/0xd0\n   do_syscall_64+0xa4/0x260\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nTo solve the hash conflict, nf_ct_resolve_clash() try to merge the\nconntracks, and update skb-\u0026gt;_nfct. However, br_nf_local_in() still use the\nold ct from local variable \u0026apos;nfct\u0026apos; after confirm(), which leads to this\nwarning.\n\nIf confirm() does not insert the conntrack entry and return NF_DROP, the\nwarning may also occur. There is no need to reserve the WARN_ON_ONCE, just\nremove it.(CVE-2025-39894)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer\n\nSince commit 7d5e9737efda (\u0026quot;net: rfkill: gpio: get the name and type from\ndevice property\u0026quot;) rfkill_find_type() gets called with the possibly\nuninitialized \u0026quot;const char *type_name;\u0026quot; local variable.\n\nOn x86 systems when rfkill-gpio binds to a \u0026quot;BCM4752\u0026quot; or \u0026quot;LNV4752\u0026quot;\nacpi_device, the rfkill-\u0026gt;type is set based on the ACPI acpi_device_id:\n\n        rfkill-\u0026gt;type = (unsigned)id-\u0026gt;driver_data;\n\nand there is no \u0026quot;type\u0026quot; property so device_property_read_string() will fail\nand leave type_name uninitialized, leading to a potential crash.\n\nrfkill_find_type() does accept a NULL pointer, fix the potential crash\nby initializing type_name to NULL.\n\nNote likely sofar this has not been caught because:\n\n1. Not many x86 machines actually have a \u0026quot;BCM4752\u0026quot;/\u0026quot;LNV4752\u0026quot; acpi_device\n2. The stack happened to contain NULL where type_name is stored(CVE-2025-39937)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Clear tcp_sk(sk)-\u0026gt;fastopen_rsk in tcp_disconnect().\n\nsyzbot reported the splat below where a socket had tcp_sk(sk)-\u0026gt;fastopen_rsk\nin the TCP_ESTABLISHED state. [0]\n\nsyzbot reused the server-side TCP Fast Open socket as a new client before\nthe TFO socket completes 3WHS:\n\n  1. accept()\n  2. connect(AF_UNSPEC)\n  3. connect() to another destination\n\nAs of accept(), sk-\u0026gt;sk_state is TCP_SYN_RECV, and tcp_disconnect() changes\nit to TCP_CLOSE and makes connect() possible, which restarts timers.\n\nSince tcp_disconnect() forgot to clear tcp_sk(sk)-\u0026gt;fastopen_rsk, the\nretransmit timer triggered the warning and the intended packet was not\nretransmitted.\n\nLet\u0026apos;s call reqsk_fastopen_remove() in tcp_disconnect().\n\n[0]:\nWARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nModules linked in:\nCPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\nRIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7))\nCode: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 \u0026lt;0f\u0026gt; 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e\nRSP: 0018:ffffc900002f8d40 EFLAGS: 00010293\nRAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017\nRDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400\nRBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8\nR10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540\nR13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0\nFS:  0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_write_timer (net/ipv4/tcp_timer.c:738)\n call_timer_fn (kernel/time/timer.c:1747)\n __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372)\n timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135)\n tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035)\n __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1))\n tmigr_handle_remote (kernel/time/timer_migration.c:1096)\n handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580)\n irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-39955)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-39980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: Defer ip_vs_ftp unregister during netns cleanup\n\nOn the netns cleanup path, __ip_vs_ftp_exit() may unregister ip_vs_ftp\nbefore connections with valid cp-\u0026gt;app pointers are flushed, leading to a\nuse-after-free.\n\nFix this by introducing a global `exiting_module` flag, set to true in\nip_vs_ftp_exit() before unregistering the pernet subsystem. In\n__ip_vs_ftp_exit(), skip ip_vs_ftp unregister if called during netns\ncleanup (when exiting_module is false) and defer it to\n__ip_vs_cleanup_batch(), which unregisters all apps after all connections\nare flushed. If called during module exit, unregister ip_vs_ftp\nimmediately.(CVE-2025-40018)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - set NULL to qm-\u0026gt;debug.qm_diff_regs\n\nWhen the initialization of qm-\u0026gt;debug.acc_diff_reg fails,\nthe probe process does not exit. However, after qm-\u0026gt;debug.qm_diff_regs is\nfreed, it is not set to NULL. This can lead to a double free when the\nremove process attempts to free it again. Therefore, qm-\u0026gt;debug.qm_diff_regs\nshould be set to NULL after it is freed.(CVE-2025-40062)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn\u0026apos;t rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn\u0026apos;t find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.(CVE-2025-40078)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: hisilicon/qm - request reserved interrupt for virtual function\n\nThe device interrupt vector 3 is an error interrupt for\nphysical function and a reserved interrupt for virtual function.\nHowever, the driver has not registered the reserved interrupt for\nvirtual function. When allocating interrupts, the number of interrupts\nis allocated based on powers of two, which includes this interrupt.\nWhen the system enables GICv4 and the virtual function passthrough\nto the virtual machine, releasing the interrupt in the driver\ntriggers a warning.\n\nThe WARNING report is:\nWARNING: CPU: 62 PID: 14889 at arch/arm64/kvm/vgic/vgic-its.c:852 its_free_ite+0x94/0xb4\n\nTherefore, register a reserved interrupt for VF and set the\nIRQF_NO_AUTOEN flag to avoid that warning.(CVE-2025-40136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: avoid NULL dereference when chunk data buffer is missing\n\nchunk-\u0026gt;skb pointer is dereferenced in the if-block where it\u0026apos;s supposed\nto be NULL only.\n\nchunk-\u0026gt;skb can only be NULL if chunk-\u0026gt;head_skb is not. Check for frag_list\ninstead and do it just before replacing chunk-\u0026gt;skb. We\u0026apos;re sure that\notherwise chunk-\u0026gt;skb is non-NULL because of outer if() condition.(CVE-2025-40240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: remove never-working support for setting nsh fields\n\nThe validation of the set(nsh(...)) action is completely wrong.\nIt runs through the nsh_key_put_from_nlattr() function that is the\nsame function that validates NSH keys for the flow match and the\npush_nsh() action.  However, the set(nsh(...)) has a very different\nmemory layout.  Nested attributes in there are doubled in size in\ncase of the masked set().  That makes proper validation impossible.\n\nThere is also confusion in the code between the \u0026apos;masked\u0026apos; flag, that\nsays that the nested attributes are doubled in size containing both\nthe value and the mask, and the \u0026apos;is_mask\u0026apos; that says that the value\nwe\u0026apos;re parsing is the mask.  This is causing kernel crash on trying to\nwrite into mask part of the match with SW_FLOW_KEY_PUT() during\nvalidation, while validate_nsh() doesn\u0026apos;t allocate any memory for it:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 1c2383067 P4D 1c2383067 PUD 20b703067 PMD 0\n  Oops: Oops: 0000 [#1] SMP NOPTI\n  CPU: 8 UID: 0 Kdump: loaded Not tainted 6.17.0-rc4+ #107 PREEMPT(voluntary)\n  RIP: 0010:nsh_key_put_from_nlattr+0x19d/0x610 [openvswitch]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   validate_nsh+0x60/0x90 [openvswitch]\n   validate_set.constprop.0+0x270/0x3c0 [openvswitch]\n   __ovs_nla_copy_actions+0x477/0x860 [openvswitch]\n   ovs_nla_copy_actions+0x8d/0x100 [openvswitch]\n   ovs_packet_cmd_execute+0x1cc/0x310 [openvswitch]\n   genl_family_rcv_msg_doit+0xdb/0x130\n   genl_family_rcv_msg+0x14b/0x220\n   genl_rcv_msg+0x47/0xa0\n   netlink_rcv_skb+0x53/0x100\n   genl_rcv+0x24/0x40\n   netlink_unicast+0x280/0x3b0\n   netlink_sendmsg+0x1f7/0x430\n   ____sys_sendmsg+0x36b/0x3a0\n   ___sys_sendmsg+0x87/0xd0\n   __sys_sendmsg+0x6d/0xd0\n   do_syscall_64+0x7b/0x2c0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe third issue with this process is that while trying to convert\nthe non-masked set into masked one, validate_set() copies and doubles\nthe size of the OVS_KEY_ATTR_NSH as if it didn\u0026apos;t have any nested\nattributes.  It should be copying each nested attribute and doubling\nthem in size independently.  And the process must be properly reversed\nduring the conversion back from masked to a non-masked variant during\nthe flow dump.\n\nIn the end, the only two outcomes of trying to use this action are\neither validation failure or a kernel crash.  And if somehow someone\nmanages to install a flow with such an action, it will most definitely\nnot do what it is supposed to, since all the keys and the masks are\nmixed up.\n\nFixing all the issues is a complex task as it requires re-writing\nmost of the validation code.\n\nGiven that and the fact that this functionality never worked since\nintroduction, let\u0026apos;s just remove it altogether.  It\u0026apos;s better to\nre-introduce it later with a proper implementation instead of trying\nto fix it in stable releases.(CVE-2025-40254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: Fix use-after-free in tipc_mon_reinit_self().\n\nsyzbot reported use-after-free of tipc_net(net)-\u0026gt;monitors[]\nin tipc_mon_reinit_self(). [0]\n\nThe array is protected by RTNL, but tipc_mon_reinit_self()\niterates over it without RTNL.\n\ntipc_mon_reinit_self() is called from tipc_net_finalize(),\nwhich is always under RTNL except for tipc_net_finalize_work().\n\nLet\u0026apos;s hold RTNL in tipc_net_finalize_work().\n\n[0]:\nBUG: KASAN: slab-use-after-free in __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\nBUG: KASAN: slab-use-after-free in _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\nRead of size 1 at addr ffff88805eae1030 by task kworker/0:7/5989\n\nCPU: 0 UID: 0 PID: 5989 Comm: kworker/0:7 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025\nWorkqueue: events tipc_net_finalize_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xca/0x240 mm/kasan/report.c:482\n kasan_report+0x118/0x150 mm/kasan/report.c:595\n __kasan_check_byte+0x2a/0x40 mm/kasan/common.c:568\n kasan_check_byte include/linux/kasan.h:399 [inline]\n lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5842\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162\n rtlock_slowlock kernel/locking/rtmutex.c:1894 [inline]\n rwbase_rtmutex_lock_state kernel/locking/spinlock_rt.c:160 [inline]\n rwbase_write_lock+0xd3/0x7e0 kernel/locking/rwbase_rt.c:244\n rt_write_lock+0x76/0x110 kernel/locking/spinlock_rt.c:243\n write_lock_bh include/linux/rwlock_rt.h:99 [inline]\n tipc_mon_reinit_self+0x79/0x430 net/tipc/monitor.c:718\n tipc_net_finalize+0x115/0x190 net/tipc/net.c:140\n process_one_work kernel/workqueue.c:3236 [inline]\n process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x439/0x7d0 arch/x86/kernel/process.c:148\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 6089:\n kasan_save_stack mm/kasan/common.c:47 [inline]\n kasan_save_track+0x3e/0x80 mm/kasan/common.c:68\n poison_kmalloc_redzone mm/kasan/common.c:388 [inline]\n __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:405\n kasan_kmalloc include/linux/kasan.h:260 [inline]\n __kmalloc_cache_noprof+0x1a8/0x320 mm/slub.c:4407\n kmalloc_noprof include/linux/slab.h:905 [inline]\n kzalloc_noprof include/linux/slab.h:1039 [inline]\n tipc_mon_create+0xc3/0x4d0 net/tipc/monitor.c:657\n tipc_enable_bearer net/tipc/bearer.c:357 [inline]\n __tipc_nl_bearer_enable+0xe16/0x13f0 net/tipc/bearer.c:1047\n __tipc_nl_compat_doit net/tipc/netlink_compat.c:371 [inline]\n tipc_nl_compat_doit+0x3bc/0x5f0 net/tipc/netlink_compat.c:393\n tipc_nl_compat_handle net/tipc/netlink_compat.c:-1 [inline]\n tipc_nl_compat_recv+0x83c/0xbe0 net/tipc/netlink_compat.c:1321\n genl_family_rcv_msg_doit+0x215/0x300 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x60e/0x790 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x846/0xa10 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:729\n ____sys_sendmsg+0x508/0x820 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x1a1/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/\n---truncated---(CVE-2025-40280)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto\n\nsyzbot reported a possible shift-out-of-bounds [1]\n\nBlamed commit added rto_alpha_max and rto_beta_max set to 1000.\n\nIt is unclear if some sctp users are setting very large rto_alpha\nand/or rto_beta.\n\nIn order to prevent user regression, perform the test at run time.\n\nAlso add READ_ONCE() annotations as sysctl values can change under us.\n\n[1]\n\nUBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41\nshift exponent 64 is too large for 32-bit type \u0026apos;unsigned int\u0026apos;\nCPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  __dump_stack lib/dump_stack.c:94 [inline]\n  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120\n  ubsan_epilogue lib/ubsan.c:233 [inline]\n  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494\n  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509\n  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502\n  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338\n  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]\n  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline](CVE-2025-40281)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: Prevent TOCTOU out-of-bounds write\n\nFor the following path not holding the sock lock,\n\n  sctp_diag_dump() -\u0026gt; sctp_for_each_endpoint() -\u0026gt; sctp_ep_dump()\n\nmake sure not to exceed bounds in case the address list has grown\nbetween buffer allocation (time-of-check) and write (time-of-use).(CVE-2025-40331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace BUG_ON with bounds check for map-\u0026gt;max_osd\n\nOSD indexes come from untrusted network packets. Boundary checks are\nadded to validate these against map-\u0026gt;max_osd.\n\n[ idryomov: drop BUG_ON in ceph_get_primary_affinity(), minor cosmetic\n  edits ](CVE-2025-68283)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds writes in handle_auth_session_key()\n\nThe len field originates from untrusted network packets. Boundary\nchecks have been added to prevent potential out-of-bounds writes when\ndecrypting the connection secret or processing service tickets.\n\n[ idryomov: changelog ](CVE-2025-68284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix potential use-after-free in have_mon_and_osd_map()\n\nThe wait loop in __ceph_open_session() can race with the client\nreceiving a new monmap or osdmap shortly after the initial map is\nreceived.  Both ceph_monc_handle_map() and handle_one_map() install\na new map immediately after freeing the old one\n\n    kfree(monc-\u0026gt;monmap);\n    monc-\u0026gt;monmap = monmap;\n\n    ceph_osdmap_destroy(osdc-\u0026gt;osdmap);\n    osdc-\u0026gt;osdmap = newmap;\n\nunder client-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock respectively, but\nbecause neither is taken in have_mon_and_osd_map() it\u0026apos;s possible for\nclient-\u0026gt;monc.monmap-\u0026gt;epoch and client-\u0026gt;osdc.osdmap-\u0026gt;epoch arms in\n\n    client-\u0026gt;monc.monmap \u0026amp;\u0026amp; client-\u0026gt;monc.monmap-\u0026gt;epoch \u0026amp;\u0026amp;\n        client-\u0026gt;osdc.osdmap \u0026amp;\u0026amp; client-\u0026gt;osdc.osdmap-\u0026gt;epoch;\n\ncondition to dereference an already freed map.  This happens to be\nreproducible with generic/395 and generic/397 with KASAN enabled:\n\n    BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70\n    Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305\n    CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266\n    ...\n    Call Trace:\n    \u0026lt;TASK\u0026gt;\n    have_mon_and_osd_map+0x56/0x70\n    ceph_open_session+0x182/0x290\n    ceph_get_tree+0x333/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u0026lt;/TASK\u0026gt;\n\n    Allocated by task 13305:\n    ceph_osdmap_alloc+0x16/0x130\n    ceph_osdc_init+0x27a/0x4c0\n    ceph_create_client+0x153/0x190\n    create_fs_client+0x50/0x2a0\n    ceph_get_tree+0xff/0x680\n    vfs_get_tree+0x49/0x180\n    do_new_mount+0x1a3/0x2d0\n    path_mount+0x6dd/0x730\n    do_mount+0x99/0xe0\n    __do_sys_mount+0x141/0x180\n    do_syscall_64+0x9f/0x100\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n    Freed by task 9475:\n    kfree+0x212/0x290\n    handle_one_map+0x23c/0x3b0\n    ceph_osdc_handle_map+0x3c9/0x590\n    mon_dispatch+0x655/0x6f0\n    ceph_con_process_message+0xc3/0xe0\n    ceph_con_v1_try_read+0x614/0x760\n    ceph_con_workfn+0x2de/0x650\n    process_one_work+0x486/0x7c0\n    process_scheduled_works+0x73/0x90\n    worker_thread+0x1c8/0x2a0\n    kthread+0x2ec/0x300\n    ret_from_fork+0x24/0x40\n    ret_from_fork_asm+0x1a/0x30\n\nRewrite the wait loop to check the above condition directly with\nclient-\u0026gt;monc.mutex and client-\u0026gt;osdc.lock taken as appropriate.  While\nat it, improve the timeout handling (previously mount_timeout could be\nexceeded in case wait_event_interruptible_timeout() slept more than\nonce) and access client-\u0026gt;auth_err under client-\u0026gt;monc.mutex to match\nhow it\u0026apos;s set in finish_auth().\n\nmonmap_show() and osdmap_show() now take the respective lock before\naccessing the map as well.(CVE-2025-68285)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: lookup hci_conn on RX path on protocol side\n\nThe hdev lock/lookup/unlock/use pattern in the packet RX path doesn\u0026apos;t\nensure hci_conn* is not concurrently modified/deleted. This locking\nappears to be leftover from before conn_hash started using RCU\ncommit bf4c63252490b (\u0026quot;Bluetooth: convert conn hash to RCU\u0026quot;)\nand not clear if it had purpose since then.\n\nCurrently, there are code paths that delete hci_conn* from elsewhere\nthan the ordered hdev-\u0026gt;workqueue where the RX work runs in. E.g.\ncommit 5af1f84ed13a (\u0026quot;Bluetooth: hci_sync: Fix UAF on hci_abort_conn_sync\u0026quot;)\nintroduced some of these, and there probably were a few others before\nit.  It\u0026apos;s better to do the locking so that even if these run\nconcurrently no UAF is possible.\n\nMove the lookup of hci_conn and associated socket-specific conn to\nprotocol recv handlers, and do them within a single critical section\nto cover hci_conn* usage and lookup.\n\nsyzkaller has reported a crash that appears to be this issue:\n\n    [Task hdev-\u0026gt;workqueue]          [Task 2]\n                                    hci_disconnect_all_sync\n    l2cap_recv_acldata(hcon)\n                                      hci_conn_get(hcon)\n                                      hci_abort_conn_sync(hcon)\n                                        hci_dev_lock\n      hci_dev_lock\n                                        hci_conn_del(hcon)\n      v-------------------------------- hci_dev_unlock\n                                      hci_conn_put(hcon)\n      conn = hcon-\u0026gt;l2cap_data (UAF)(CVE-2025-68304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nima: Handle error code returned by ima_filter_rule_match()\n\nIn ima_match_rules(), if ima_filter_rule_match() returns -ENOENT due to\nthe rule being NULL, the function incorrectly skips the \u0026apos;if (!rc)\u0026apos; check\nand sets \u0026apos;result = true\u0026apos;. The LSM rule is considered a match, causing\nextra files to be measured by IMA.\n\nThis issue can be reproduced in the following scenario:\nAfter unloading the SELinux policy module via \u0026apos;semodule -d\u0026apos;, if an IMA\nmeasurement is triggered before ima_lsm_rules is updated,\nin ima_match_rules(), the first call to ima_filter_rule_match() returns\n-ESTALE. This causes the code to enter the \u0026apos;if (rc == -ESTALE \u0026amp;\u0026amp;\n!rule_reinitialized)\u0026apos; block, perform ima_lsm_copy_rule() and retry. In\nima_lsm_copy_rule(), since the SELinux module has been removed, the rule\nbecomes NULL, and the second call to ima_filter_rule_match() returns\n-ENOENT. This bypasses the \u0026apos;if (!rc)\u0026apos; check and results in a false match.\n\nCall trace:\n  selinux_audit_rule_match+0x310/0x3b8\n  security_audit_rule_match+0x60/0xa0\n  ima_match_rules+0x2e4/0x4a0\n  ima_match_policy+0x9c/0x1e8\n  ima_get_action+0x48/0x60\n  process_measurement+0xf8/0xa98\n  ima_bprm_check+0x98/0xd8\n  security_bprm_check+0x5c/0x78\n  search_binary_handler+0x6c/0x318\n  exec_binprm+0x58/0x1b8\n  bprm_execve+0xb8/0x130\n  do_execveat_common.isra.0+0x1a8/0x258\n  __arm64_sys_execve+0x48/0x68\n  invoke_syscall+0x50/0x128\n  el0_svc_common.constprop.0+0xc8/0xf0\n  do_el0_svc+0x24/0x38\n  el0_svc+0x44/0x200\n  el0t_64_sync_handler+0x100/0x130\n  el0t_64_sync+0x3c8/0x3d0\n\nFix this by changing \u0026apos;if (!rc)\u0026apos; to \u0026apos;if (rc \u0026lt;= 0)\u0026apos; to ensure that error\ncodes like -ENOENT do not bypass the check and accidentally result in a\nsuccessful match.(CVE-2025-68740)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u0026gt;stats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u0026lt;-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u0026gt;items[index] = \u0026amp;dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u0026gt;stats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(\u0026amp;stats-\u0026gt;syncp)\n---softirq end---\n\n  static_branch_dec(\u0026amp;cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.(CVE-2025-68742)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nethtool: Avoid overflowing userspace buffer on stats query\n\nThe ethtool -S command operates across three ioctl calls:\nETHTOOL_GSSET_INFO for the size, ETHTOOL_GSTRINGS for the names, and\nETHTOOL_GSTATS for the values.\n\nIf the number of stats changes between these calls (e.g., due to device\nreconfiguration), userspace\u0026apos;s buffer allocation will be incorrect,\npotentially leading to buffer overflow.\n\nDrivers are generally expected to maintain stable stat counts, but some\ndrivers (e.g., mlx5, bnx2x, bna, ksz884x) use dynamic counters, making\nthis scenario possible.\n\nSome drivers try to handle this internally:\n- bnad_get_ethtool_stats() returns early in case stats.n_stats is not\n  equal to the driver\u0026apos;s stats count.\n- micrel/ksz884x also makes sure not to write anything beyond\n  stats.n_stats and overflow the buffer.\n\nHowever, both use stats.n_stats which is already assigned with the value\nreturned from get_sset_count(), hence won\u0026apos;t solve the issue described\nhere.\n\nChange ethtool_get_strings(), ethtool_get_stats(),\nethtool_get_phy_stats() to not return anything in case of a mismatch\nbetween userspace\u0026apos;s size and get_sset_size(), to prevent buffer\noverflow.\nThe returned n_stats value will be equal to zero, to reflect that\nnothing has been returned.\n\nThis could result in one of two cases when using upstream ethtool,\ndepending on when the size change is detected:\n1. When detected in ethtool_get_strings():\n    # ethtool -S eth2\n    no stats available\n\n2. When detected in get stats, all stats will be reported as zero.\n\nBoth cases are presumably transient, and a subsequent ethtool call\nshould succeed.\n\nOther than the overflow avoidance, these two cases are very evident (no\noutput/cleared stats), which is arguably better than presenting\nincorrect/shifted stats.\nI also considered returning an error instead of a \u0026quot;silent\u0026quot; response, but\nthat seems more destructive towards userspace apps.\n\nNotes:\n- This patch does not claim to fix the inherent race, it only makes sure\n  that we do not overflow the userspace buffer, and makes for a more\n  predictable behavior.\n\n- RTNL lock is held during each ioctl, the race window exists between\n  the separate ioctl calls when the lock is released.\n\n- Userspace ethtool always fills stats.n_stats, but it is likely that\n  these stats ioctls are implemented in other userspace applications\n  which might not fill it. The added code checks that it\u0026apos;s not zero,\n  to prevent any regressions.(CVE-2025-68795)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: xattr: fix null pointer deref in ext4_raw_inode()\n\nIf ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),\niloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()\nlacks error checking, this will lead to a null pointer dereference\nin ext4_raw_inode(), called right after ext4_get_inode_loc().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68820)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: using the num_tqps in the vf driver to apply for resources\n\nCurrently, hdev-\u0026gt;htqp is allocated using hdev-\u0026gt;num_tqps, and kinfo-\u0026gt;tqp\nis allocated using kinfo-\u0026gt;num_tqps. However, kinfo-\u0026gt;num_tqps is set to\nmin(new_tqps, hdev-\u0026gt;num_tqps);  Therefore, kinfo-\u0026gt;num_tqps may be smaller\nthan hdev-\u0026gt;num_tqps, which causes some hdev-\u0026gt;htqp[i] to remain\nuninitialized in hclgevf_knic_setup().\n\nThus, this patch allocates hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp using hdev-\u0026gt;num_tqps,\nensuring that the lengths of hdev-\u0026gt;htqp and kinfo-\u0026gt;tqp are consistent\nand that all elements are properly initialized.(CVE-2025-71064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset\n\n`qfq_class-\u0026gt;leaf_qdisc-\u0026gt;q.qlen \u0026gt; 0` does not imply that the class\nitself is active.\n\nTwo qfq_class objects may point to the same leaf_qdisc. This happens\nwhen:\n\n1. one QFQ qdisc is attached to the dev as the root qdisc, and\n\n2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()\n/ qdisc_put()) and is pending to be destroyed, as in function\ntc_new_tfilter.\n\nWhen packets are enqueued through the root QFQ qdisc, the shared\nleaf_qdisc-\u0026gt;q.qlen increases. At the same time, the second QFQ\nqdisc triggers qdisc_put and qdisc_destroy: the qdisc enters\nqfq_reset() with its own q-\u0026gt;q.qlen == 0, but its class\u0026apos;s leaf\nqdisc-\u0026gt;q.qlen \u0026gt; 0. Therefore, the qfq_reset would wrongly deactivate\nan inactive aggregate and trigger a null-deref in qfq_deactivate_agg:\n\n[    0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    0.903571] #PF: supervisor write access in kernel mode\n[    0.903860] #PF: error_code(0x0002) - not-present page\n[    0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0\n[    0.904502] Oops: Oops: 0002 [#1] SMP NOPTI\n[    0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE\n[    0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[    0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))\n[    0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0\n\nCode starting with the faulting instruction\n===========================================\n   0:\t0f 84 4d 01 00 00    \tje     0x153\n   6:\t48 89 70 18          \tmov    %rsi,0x18(%rax)\n   a:\t8b 4b 10             \tmov    0x10(%rbx),%ecx\n   d:\t48 c7 c2 ff ff ff ff \tmov    $0xffffffffffffffff,%rdx\n  14:\t48 8b 78 08          \tmov    0x8(%rax),%rdi\n  18:\t48 d3 e2             \tshl    %cl,%rdx\n  1b:\t48 21 f2             \tand    %rsi,%rdx\n  1e:\t48 2b 13             \tsub    (%rbx),%rdx\n  21:\t48 8b 30             \tmov    (%rax),%rsi\n  24:\t48 d3 ea             \tshr    %cl,%rdx\n  27:\t8b 4b 18             \tmov    0x18(%rbx),%ecx\n\t...\n[    0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246\n[    0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000\n[    0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[    0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000\n[    0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000\n[    0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880\n[    0.909179] FS:  000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000\n[    0.909572] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0\n[    0.910247] PKRU: 55555554\n[    0.910391] Call Trace:\n[    0.910527]  \u0026lt;TASK\u0026gt;\n[    0.910638]  qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)\n[    0.910826]  qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)\n[    0.911040]  __qdisc_destroy (net/sched/sch_generic.c:1076)\n[    0.911236]  tc_new_tfilter (net/sched/cls_api.c:2447)\n[    0.911447]  rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\n[    0.911663]  ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)\n[    0.911894]  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n[    0.912100]  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n[    0.912296]  ? __alloc_skb (net/core/skbuff.c:706)\n[    0.912484]  netlink_sendmsg (net/netlink/af\n---truncated---(CVE-2026-22976)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix reference count leak in bpf_prog_test_run_xdp()\n\nsyzbot is reporting\n\n  unregister_netdevice: waiting for sit0 to become free. Usage count = 2\n\nproblem. A debug printk() patch found that a refcount is obtained at\nxdp_convert_md_to_buff() from bpf_prog_test_run_xdp().\n\nAccording to commit ec94670fcb3b (\u0026quot;bpf: Support specifying ingress via\nxdp_md context in BPF_PROG_TEST_RUN\u0026quot;), the refcount obtained by\nxdp_convert_md_to_buff() will be released by xdp_convert_buff_to_md().\n\nTherefore, we can consider that the error handling path introduced by\ncommit 1c1949982524 (\u0026quot;bpf: introduce frags support to\nbpf_prog_test_run_xdp()\u0026quot;) forgot to call xdp_convert_buff_to_md().(CVE-2026-22994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a deadlock involving nfs_release_folio()\n\nWang Zhaolong reports a deadlock involving NFSv4.1 state recovery\nwaiting on kthreadd, which is attempting to reclaim memory by calling\nnfs_release_folio(). The latter cannot make progress due to state\nrecovery being needed.\n\nIt seems that the only safe thing to do here is to kick off a writeback\nof the folio, without waiting for completion, or else kicking off an\nasynchronous commit.(CVE-2026-23053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-core: fix wrong reinitialization of ringbuffer on reopen\n\ndvb_dvr_open() calls dvb_ringbuffer_init() when a new reader opens the\nDVR device.  dvb_ringbuffer_init() calls init_waitqueue_head(), which\nreinitializes the waitqueue list head to empty.\n\nSince dmxdev-\u0026gt;dvr_buffer.queue is a shared waitqueue (all opens of the\nsame DVR device share it), this orphans any existing waitqueue entries\nfrom io_uring poll or epoll, leaving them with stale prev/next pointers\nwhile the list head is reset to {self, self}.\n\nThe waitqueue and spinlock in dvr_buffer are already properly\ninitialized once in dvb_dmxdev_init().  The open path only needs to\nreset the buffer data pointer, size, and read/write positions.\n\nReplace the dvb_ringbuffer_init() call in dvb_dvr_open() with direct\nassignment of data/size and a call to dvb_ringbuffer_reset(), which\nproperly resets pread, pwrite, and error with correct memory ordering\nwithout touching the waitqueue or spinlock.(CVE-2026-23253)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: maple: free entry on mas_store_gfp() failure\n\nregcache_maple_write() allocates a new block (\u0026apos;entry\u0026apos;) to merge\nadjacent ranges and then stores it with mas_store_gfp().\nWhen mas_store_gfp() fails, the new \u0026apos;entry\u0026apos; remains allocated and\nis never freed, leaking memory.\n\nFree \u0026apos;entry\u0026apos; on the failure path; on success continue freeing the\nreplaced neighbor blocks (\u0026apos;lower\u0026apos;, \u0026apos;upper\u0026apos;).(CVE-2026-23260)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix unprivileged local user can do privileged policy management\n\nAn unprivileged local user can load, replace, and remove profiles by\nopening the apparmorfs interfaces, via a confused deputy attack, by\npassing the opened fd to a privileged process, and getting the\nprivileged process to write to the interface.\n\nThis does require a privileged target that can be manipulated to do\nthe write for the unprivileged process, but once such access is\nachieved full policy management is possible and all the possible\nimplications that implies: removing confinement, DoS of system or\ntarget applications by denying all execution, by-passing the\nunprivileged user namespace restriction, to exploiting kernel bugs for\na local privilege escalation.\n\nThe policy management interface can not have its permissions simply\nchanged from 0666 to 0600 because non-root processes need to be able\nto load policy to different policy namespaces.\n\nInstead ensure the task writing the interface has privileges that\nare a subset of the task that opened the interface. This is already\ndone via policy for confined processes, but unconfined can delegate\naccess to the opened fd, by-passing the usual policy check.(CVE-2026-23268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix __perf_event_overflow() vs perf_remove_from_context() race\n\nMake sure that __perf_event_overflow() runs with IRQs disabled for all\npossible callchains. Specifically the software events can end up running\nit with only preemption disabled.\n\nThis opens up a race vs perf_event_exit_event() and friends that will go\nand free various things the overflow path expects to be present, like\nthe BPF program.(CVE-2026-23271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: observe an RCU grace period in macvlan_common_newlink() error path\n\nvalis reported that a race condition still happens after my prior patch.\n\nmacvlan_common_newlink() might have made @dev visible before\ndetecting an error, and its caller will directly call free_netdev(dev).\n\nWe must respect an RCU period, either in macvlan or the core networking\nstack.\n\nAfter adding a temporary mdelay(1000) in macvlan_forward_source_one()\nto open the race window, valis repro was:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\nip link add mv0 link p2 type macvlan mode source\n\n(ip link add invalid% link p2 type macvlan mode source macaddr add\n00:00:00:00:00:20 \u0026amp;) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4\nPING 1.2.3.4 (1.2.3.4): 56 data bytes\nRTNETLINK answers: Invalid argument\n\nBUG: KASAN: slab-use-after-free in macvlan_forward_source\n(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nRead of size 8 at addr ffff888016bb89c0 by task e/175\n\nCPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014\nCall Trace:\n\u0026lt;IRQ\u0026gt;\ndump_stack_lvl (lib/dump_stack.c:123)\nprint_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nkasan_report (mm/kasan/report.c:597)\n? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\nmacvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)\n? tasklet_init (kernel/softirq.c:983)\nmacvlan_handle_frame (drivers/net/macvlan.c:501)\n\nAllocated by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\n__kasan_kmalloc (mm/kasan/common.c:419)\n__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657\nmm/slub.c:7140)\nalloc_netdev_mqs (net/core/dev.c:12012)\nrtnl_create_link (net/core/rtnetlink.c:3648)\nrtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)\n\nFreed by task 169:\nkasan_save_stack (mm/kasan/common.c:58)\nkasan_save_track (./arch/x86/include/asm/current.h:25\nmm/kasan/common.c:70 mm/kasan/common.c:79)\nkasan_save_free_info (mm/kasan/generic.c:587)\n__kasan_slab_free (mm/kasan/common.c:287)\nkfree (mm/slub.c:6674 mm/slub.c:6882)\nrtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957\nnet/core/rtnetlink.c:4072)\nrtnetlink_rcv_msg (net/core/rtnetlink.c:6958)\nnetlink_rcv_skb (net/netlink/af_netlink.c:2550)\nnetlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\nnetlink_sendmsg (net/netlink/af_netlink.c:1894)\n__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)\n__x64_sys_sendto (net/socket.c:2209)\ndo_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\nentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)(CVE-2026-23273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Fix recursive locking in __configfs_open_file()\n\nIn flush_write_buffer, \u0026amp;p-\u0026gt;frag_sem is acquired and then the loaded store\nfunction is called, which, here, is target_core_item_dbroot_store().  This\nfunction called filp_open(), following which these functions were called\n(in reverse order), according to the call trace:\n\n  down_read\n  __configfs_open_file\n  do_dentry_open\n  vfs_open\n  do_open\n  path_openat\n  do_filp_open\n  file_open_name\n  filp_open\n  target_core_item_dbroot_store\n  flush_write_buffer\n  configfs_write_iter\n\ntarget_core_item_dbroot_store() tries to validate the new file path by\ntrying to open the file path provided to it; however, in this case, the bug\nreport shows:\n\ndb_root: not a directory: /sys/kernel/config/target/dbroot\n\nindicating that the same configfs file was tried to be opened, on which it\nis currently working on. Thus, it is trying to acquire frag_sem semaphore\nof the same file of which it already holds the semaphore obtained in\nflush_write_buffer(), leading to acquiring the semaphore in a nested manner\nand a possibility of recursive locking.\n\nFix this by modifying target_core_item_dbroot_store() to use kern_path()\ninstead of filp_open() to avoid opening the file using filesystem-specific\nfunction __configfs_open_file(), and further modifying it to make this fix\ncompatible.(CVE-2026-23292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix refcount leak for tagset_refcnt\n\nThis leak will cause a hang when tearing down the SCSI host. For example,\niscsid hangs with the following call trace:\n\n[130120.652718] scsi_alloc_sdev: Allocation failure during SCSI scanning, some SCSI devices might not be configured\n\nPID: 2528     TASK: ffff9d0408974e00  CPU: 3    COMMAND: \u0026quot;iscsid\u0026quot;\n #0 [ffffb5b9c134b9e0] __schedule at ffffffff860657d4\n #1 [ffffb5b9c134ba28] schedule at ffffffff86065c6f\n #2 [ffffb5b9c134ba40] schedule_timeout at ffffffff86069fb0\n #3 [ffffb5b9c134bab0] __wait_for_common at ffffffff8606674f\n #4 [ffffb5b9c134bb10] scsi_remove_host at ffffffff85bfe84b\n #5 [ffffb5b9c134bb30] iscsi_sw_tcp_session_destroy at ffffffffc03031c4 [iscsi_tcp]\n #6 [ffffb5b9c134bb48] iscsi_if_recv_msg at ffffffffc0292692 [scsi_transport_iscsi]\n #7 [ffffb5b9c134bb98] iscsi_if_rx at ffffffffc02929c2 [scsi_transport_iscsi]\n #8 [ffffb5b9c134bbf0] netlink_unicast at ffffffff85e551d6\n #9 [ffffb5b9c134bc38] netlink_sendmsg at ffffffff85e554ef(CVE-2026-23296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix preempt count leak in napi poll tracepoint\n\nUsing get_cpu() in the tracepoint assignment causes an obvious preempt\ncount leak because nothing invokes put_cpu() to undo it:\n\n  softirq: huh, entered softirq 3 NET_RX with preempt_count 00000100, exited with 00000101?\n\nThis clearly has seen a lot of testing in the last 3+ years...\n\nUse smp_processor_id() instead.(CVE-2026-23313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Return the correct value in vmw_translate_ptr functions\n\nBefore the referenced fixes these functions used a lookup function that\nreturned a pointer. This was changed to another lookup function that\nreturned an error code with the pointer becoming an out parameter.\n\nThe error path when the lookup failed was not changed to reflect this\nchange and the code continued to return the PTR_ERR of the now\nuninitialized pointer. This could cause the vmw_translate_ptr functions\nto return success when they actually failed causing further uninitialized\nand OOB accesses.(CVE-2026-23317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim\n\nThe root cause of this bug is that when \u0026apos;bpf_link_put\u0026apos; reduces the\nrefcount of \u0026apos;shim_link-\u0026gt;link.link\u0026apos; to zero, the resource is considered\nreleased but may still be referenced via \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;cgroup_shim_find\u0026apos;. The actual cleanup of \u0026apos;tr-\u0026gt;progs_hlist\u0026apos; in\n\u0026apos;bpf_shim_tramp_link_release\u0026apos; is deferred. During this window, another\nprocess can cause a use-after-free via \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n\nBased on Martin KaFai Lau\u0026apos;s suggestions, I have created a simple patch.\n\nTo fix this:\n   Add an atomic non-zero check in \u0026apos;bpf_trampoline_link_cgroup_shim\u0026apos;.\n   Only increment the refcount if it is not already zero.\n\nTesting:\n   I verified the fix by adding a delay in\n   \u0026apos;bpf_shim_tramp_link_release\u0026apos; to make the bug easier to trigger:\n\nstatic void bpf_shim_tramp_link_release(struct bpf_link *link)\n{\n\t/* ... */\n\tif (!shim_link-\u0026gt;trampoline)\n\t\treturn;\n\n+\tmsleep(100);\n\tWARN_ON_ONCE(bpf_trampoline_unlink_prog(\u0026amp;shim_link-\u0026gt;link,\n\t\tshim_link-\u0026gt;trampoline, NULL));\n\tbpf_trampoline_put(shim_link-\u0026gt;trampoline);\n}\n\nBefore the patch, running a PoC easily reproduced the crash(almost 100%)\nwith a call trace similar to KaiyanM\u0026apos;s report.\nAfter the patch, the bug no longer occurs even after millions of\niterations.(CVE-2026-23319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/efi: defer freeing of boot services memory\n\nefi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE\nand EFI_BOOT_SERVICES_DATA using memblock_free_late().\n\nThere are two issue with that: memblock_free_late() should be used for\nmemory allocated with memblock_alloc() while the memory reserved with\nmemblock_reserve() should be freed with free_reserved_area().\n\nMore acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y\nefi_free_boot_services() is called before deferred initialization of the\nmemory map is complete.\n\nBenjamin Herrenschmidt reports that this causes a leak of ~140MB of\nRAM on EC2 t3a.nano instances which only have 512MB or RAM.\n\nIf the freed memory resides in the areas that memory map for them is\nstill uninitialized, they won\u0026apos;t be actually freed because\nmemblock_free_late() calls memblock_free_pages() and the latter skips\nuninitialized pages.\n\nUsing free_reserved_area() at this point is also problematic because\n__free_page() accesses the buddy of the freed page and that again might\nend up in uninitialized part of the memory map.\n\nDelaying the entire efi_free_boot_services() could be problematic\nbecause in addition to freeing boot services memory it updates\nefi.memmap without any synchronization and that\u0026apos;s undesirable late in\nboot when there is concurrency.\n\nMore robust approach is to only defer freeing of the EFI boot services\nmemory.\n\nSplit efi_free_boot_services() in two. First efi_unmap_boot_services()\ncollects ranges that should be freed into an array then\nefi_free_boot_services() later frees them after deferred init is complete.(CVE-2026-23352)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stack-out-of-bounds write in devmap\n\nget_upper_ifindexes() iterates over all upper devices and writes their\nindices into an array without checking bounds.\n\nAlso the callers assume that the max number of upper devices is\nMAX_NEST_DEV and allocate excluded_devices[1+MAX_NEST_DEV] on the stack,\nbut that assumption is not correct and the number of upper devices could\nbe larger than MAX_NEST_DEV (e.g., many macvlans), causing a\nstack-out-of-bounds write.\n\nAdd a max parameter to get_upper_ifindexes() to avoid the issue.\nWhen there are too many upper devices, return -EOVERFLOW and abort the\nredirect.\n\nTo reproduce, create more than MAX_NEST_DEV(8) macvlans on a device with\nan XDP program attached using BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS.\nThen send a packet to the device to trigger the XDP redirect path.(CVE-2026-23359)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin queue leak on controller reset\n\nWhen nvme_alloc_admin_tag_set() is called during a controller reset,\na previous admin queue may still exist. Release it properly before\nallocating a new one to avoid orphaning the old queue.\n\nThis fixes a regression introduced by commit 03b3bcd319b3 (\u0026quot;nvme: fix\nadmin request_queue lifetime\u0026quot;).(CVE-2026-23360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblktrace: fix __this_cpu_read/write in preemptible context\n\ntracing_record_cmdline() internally uses __this_cpu_read() and\n__this_cpu_write() on the per-CPU variable trace_cmdline_save, and\ntrace_save_cmdline() explicitly asserts preemption is disabled via\nlockdep_assert_preemption_disabled(). These operations are only safe\nwhen preemption is off, as they were designed to be called from the\nscheduler context (probe_wakeup_sched_switch() / probe_wakeup()).\n\n__blk_add_trace() was calling tracing_record_cmdline(current) early in\nthe blk_tracer path, before ring buffer reservation, from process\ncontext where preemption is fully enabled. This triggers the following\nusing blktests/blktrace/002:\n\nblktrace/002 (blktrace ftrace corruption with sysfs trace)   [failed]\n    runtime  0.367s  ...  0.437s\n    something found in dmesg:\n    [   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n    [   81.239580] null_blk: disk nullb1 created\n    [   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n    [   81.362842] caller is tracing_record_cmdline+0x10/0x40\n    [   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n    [   81.362877] Tainted: [N]=TEST\n    [   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n    [   81.362881] Call Trace:\n    [   81.362884]  \u0026lt;TASK\u0026gt;\n    [   81.362886]  dump_stack_lvl+0x8d/0xb0\n    ...\n    (See \u0026apos;/mnt/sda/blktests/results/nodev/blktrace/002.dmesg\u0026apos; for the entire message)\n\n[   81.211018] run blktests blktrace/002 at 2026-02-25 22:24:33\n[   81.239580] null_blk: disk nullb1 created\n[   81.357294] BUG: using __this_cpu_read() in preemptible [00000000] code: dd/2516\n[   81.362842] caller is tracing_record_cmdline+0x10/0x40\n[   81.362872] CPU: 16 UID: 0 PID: 2516 Comm: dd Tainted: G                 N  7.0.0-rc1lblk+ #84 PREEMPT(full)\n[   81.362877] Tainted: [N]=TEST\n[   81.362878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014\n[   81.362881] Call Trace:\n[   81.362884]  \u0026lt;TASK\u0026gt;\n[   81.362886]  dump_stack_lvl+0x8d/0xb0\n[   81.362895]  check_preemption_disabled+0xce/0xe0\n[   81.362902]  tracing_record_cmdline+0x10/0x40\n[   81.362923]  __blk_add_trace+0x307/0x5d0\n[   81.362934]  ? lock_acquire+0xe0/0x300\n[   81.362940]  ? iov_iter_extract_pages+0x101/0xa30\n[   81.362959]  blk_add_trace_bio+0x106/0x1e0\n[   81.362968]  submit_bio_noacct_nocheck+0x24b/0x3a0\n[   81.362979]  ? lockdep_init_map_type+0x58/0x260\n[   81.362988]  submit_bio_wait+0x56/0x90\n[   81.363009]  __blkdev_direct_IO_simple+0x16c/0x250\n[   81.363026]  ? __pfx_submit_bio_wait_endio+0x10/0x10\n[   81.363038]  ? rcu_read_lock_any_held+0x73/0xa0\n[   81.363051]  blkdev_read_iter+0xc1/0x140\n[   81.363059]  vfs_read+0x20b/0x330\n[   81.363083]  ksys_read+0x67/0xe0\n[   81.363090]  do_syscall_64+0xbf/0xf00\n[   81.363102]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   81.363106] RIP: 0033:0x7f281906029d\n[   81.363111] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d 66 63 0a 00 e8 59 ff 01 00 66 0f 1f 84 00 00 00 00 00 80 3d 41 33 0e 00 00 74 17 31 c0 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec\n[   81.363113] RSP: 002b:00007ffca127dd48 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\n[   81.363120] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f281906029d\n[   81.363122] RDX: 0000000000001000 RSI: 0000559f8bfae000 RDI: 0000000000000000\n[   81.363123] RBP: 0000000000001000 R08: 0000002863a10a81 R09: 00007f281915f000\n[   81.363124] R10: 00007f2818f77b60 R11: 0000000000000246 R12: 0000559f8bfae000\n[   81.363126] R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000a\n[   81.363142]  \u0026lt;/TASK\u0026gt;\n\nThe same BUG fires from blk_add_trace_plug(), blk_add_trace_unplug(),\nand blk_add_trace_rq() paths as well.\n\nThe purpose of tracin\n---truncated---(CVE-2026-23374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing\n\nstruct bpf_plt contains a u64 target field. Currently, the BPF JIT\nallocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT\nbuffer.\n\nBecause the base address of the JIT buffer can be 4-byte aligned (e.g.,\nending in 0x4 or 0xc), the relative padding logic in build_plt() fails\nto ensure that target lands on an 8-byte boundary.\n\nThis leads to two issues:\n1. UBSAN reports misaligned-access warnings when dereferencing the\n   structure.\n2. More critically, target is updated concurrently via WRITE_ONCE() in\n   bpf_arch_text_poke() while the JIT\u0026apos;d code executes ldr. On arm64,\n   64-bit loads/stores are only guaranteed to be single-copy atomic if\n   they are 64-bit aligned. A misaligned target risks a torn read,\n   causing the JIT to jump to a corrupted address.\n\nFix this by increasing the allocation alignment requirement to 8 bytes\n(sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of\nthe JIT buffer to an 8-byte boundary, allowing the relative padding math\nin build_plt() to correctly align the target field.(CVE-2026-23383)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: check metadata block offset is within range\n\nSyzkaller reports a \u0026quot;general protection fault in squashfs_copy_data\u0026quot;\n\nThis is ultimately caused by a corrupted index look-up table, which\nproduces a negative metadata block offset.\n\nThis is subsequently passed to squashfs_copy_data (via\nsquashfs_read_metadata) where the negative offset causes an out of bounds\naccess.\n\nThe fix is to check that the offset is within range in\nsquashfs_read_metadata.  This will trap this and other cases.(CVE-2026-23388)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: reject mount if bigalloc with s_first_data_block != 0\n\nbigalloc with s_first_data_block != 0 is not supported, reject mounting\nit.(CVE-2026-31447)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: Check to ensure report responses match the request\n\nIt is possible for a malicious (or clumsy) device to respond to a\nspecific report\u0026apos;s feature request using a completely different report\nID.  This can cause confusion in the HID core resulting in nasty\nside-effects such as OOB writes.\n\nAdd a check to ensure that the report ID in the response, matches the\none that was requested.  If it doesn\u0026apos;t, omit reporting the raw event and\nreturn early.(CVE-2026-43047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Mitigate potential OOB by removing bogus memset()\n\nThe memset() in hid_report_raw_event() has the good intention of\nclearing out bogus data by zeroing the area from the end of the incoming\ndata string to the assumed end of the buffer.  However, as we have\npreviously seen, doing so can easily result in OOB reads and writes in\nthe subsequent thread of execution.\n\nThe current suggestion from one of the HID maintainers is to remove the\nmemset() and simply return if the incoming event buffer size is not\nlarge enough to fill the associated report.\n\nSuggested-by Benjamin Tissoires \u0026lt;(CVE-2026-43048)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: close crash window in attr dabtree inactivation\n\nWhen inactivating an inode with node-format extended attributes,\nxfs_attr3_node_inactive() invalidates all child leaf/node blocks via\nxfs_trans_binval(), but intentionally does not remove the corresponding\nentries from their parent node blocks.  The implicit assumption is that\nxfs_attr_inactive() will truncate the entire attr fork to zero extents\nafterwards, so log recovery will never reach the root node and follow\nthose stale pointers.\n\nHowever, if a log shutdown occurs after the leaf/node block cancellations\ncommit but before the attr bmap truncation commits, this assumption\nbreaks.  Recovery replays the attr bmap intact (the inode still has\nattr fork extents), but suppresses replay of all cancelled leaf/node\nblocks, maybe leaving them as stale data on disk.  On the next mount,\nxlog_recover_process_iunlinks() retries inactivation and attempts to\nread the root node via the attr bmap. If the root node was not replayed,\nreading the unreplayed root block triggers a metadata verification\nfailure immediately; if it was replayed, following its child pointers\nto unreplayed child blocks triggers the same failure:\n\n XFS (pmem0): Metadata corruption detected at\n xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78\n XFS (pmem0): Unmount and run xfs_repair\n XFS (pmem0): First 128 bytes of corrupted metadata buffer:\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n XFS (pmem0): metadata I/O error in \u0026quot;xfs_da_read_buf+0x104/0x190\u0026quot; at daddr 0x78 len 8 error 117\n\nFix this in two places:\n\nIn xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a\nchild block, immediately remove the entry that references it from the\nparent node in the same transaction.  This eliminates the window where\nthe parent holds a pointer to a cancelled block.  Once all children are\nremoved, the now-empty root node is converted to a leaf block within the\nsame transaction. This node-to-leaf conversion is necessary for crash\nsafety. If the system shutdown after the empty node is written to the\nlog but before the second-phase bmap truncation commits, log recovery\nwill attempt to verify the root block on disk. xfs_da3_node_verify()\ndoes not permit a node block with count == 0; such a block will fail\nverification and trigger a metadata corruption shutdown. on the other\nhand, leaf blocks are allowed to have this transient state.\n\nIn xfs_attr_inactive(), split the attr fork truncation into two explicit\nphases.  First, truncate all extents beyond the root block (the child\nextents whose parent references have already been removed above).\nSecond, invalidate the root block and truncate the attr bmap to zero in\na single transaction.  The two operations in the second phase must be\natomic: as long as the attr bmap has any non-zero length, recovery can\nfollow it to the root block, so the root block invalidation must commit\ntogether with the bmap-to-zero truncation.(CVE-2026-43053)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRevert \u0026quot;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV\u0026quot;\n\nThis reverts commit 05703271c3cd (\u0026quot;PCI/IOV: Add PCI rescan-remove locking\nwhen enabling/disabling SR-IOV\u0026quot;), which causes a deadlock by recursively\ntaking pci_rescan_remove_lock when sriov_del_vfs() is called as part of\npci_stop_and_remove_bus_device(). For example with the following sequence\nof commands:\n\n  $ echo \u0026lt;NUM\u0026gt; \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/sriov_numvfs\n  $ echo 1 \u0026gt; /sys/bus/pci/devices/\u0026lt;pf\u0026gt;/remove\n\nA trimmed trace of the deadlock on a mlx5 device is as below:\n\n  zsh/5715 is trying to acquire lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140\n\n  but task is already holding lock:\n  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80\n  ...\n  Call Trace:\n   [\u0026lt;00000259778c4f90\u0026gt;] dump_stack_lvl+0xc0/0x110\n   [\u0026lt;00000259779c844e\u0026gt;] print_deadlock_bug+0x31e/0x330\n   [\u0026lt;00000259779c1908\u0026gt;] __lock_acquire+0x16c8/0x32f0\n   [\u0026lt;00000259779bffac\u0026gt;] lock_acquire+0x14c/0x350\n   [\u0026lt;00000259789643a6\u0026gt;] __mutex_lock_common+0xe6/0x1520\n   [\u0026lt;000002597896413c\u0026gt;] mutex_lock_nested+0x3c/0x50\n   [\u0026lt;00000259784a07e4\u0026gt;] sriov_disable+0x34/0x140\n   [\u0026lt;00000258f7d6dd80\u0026gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]\n   [\u0026lt;00000258f7d5745e\u0026gt;] remove_one+0x5e/0xf0 [mlx5_core]\n   [\u0026lt;00000259784857fc\u0026gt;] pci_device_remove+0x3c/0xa0\n   [\u0026lt;000002597851012e\u0026gt;] device_release_driver_internal+0x18e/0x280\n   [\u0026lt;000002597847ae22\u0026gt;] pci_stop_bus_device+0x82/0xa0\n   [\u0026lt;000002597847afce\u0026gt;] pci_stop_and_remove_bus_device_locked+0x5e/0x80\n   [\u0026lt;00000259784972c2\u0026gt;] remove_store+0x72/0x90\n   [\u0026lt;0000025977e6661a\u0026gt;] kernfs_fop_write_iter+0x15a/0x200\n   [\u0026lt;0000025977d7241c\u0026gt;] vfs_write+0x24c/0x300\n   [\u0026lt;0000025977d72696\u0026gt;] ksys_write+0x86/0x110\n   [\u0026lt;000002597895b61c\u0026gt;] __do_syscall+0x14c/0x400\n   [\u0026lt;000002597896e0ee\u0026gt;] system_call+0x6e/0x90\n\nThis alone is not a complete fix as it restores the issue the cited commit\ntried to solve. A new fix will be provided as a follow on.(CVE-2026-43147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narm64: Add support for TSV110 Spectre-BHB mitigation\n\nThe TSV110 processor is vulnerable to the Spectre-BHB (Branch History\nBuffer) attack, which can be exploited to leak information through\nbranch prediction side channels. This commit adds the MIDR of TSV110\nto the list for software mitigation.(CVE-2026-43261)\n\nIn the Linux kernel, the kexec_load_purgatory() function derives image-\u0026gt;start by locating e_entry inside an SHF_EXECINSTR section. If the purgatory object contains multiple executable sections with overlapping sh_addr, the entrypoint check can match more than once and trigger a WARN. Derive the entry section from the purgatory_start symbol when present and compute image-\u0026gt;start from its final placement. Keep the existing e_entry fallback for purgatories that do not expose the symbol.(CVE-2026-43289)\n\nIn the Linux kernel, there is a potential out-of-bounds access vulnerability in the ceph_handle_auth_reply() function of the libceph component. When processing messages of type CEPH_MSG_AUTH_REPLY, the value of the payload_len field is stored in a variable of type int. A value greater than INT_MAX leads to integer overflow and is interpreted as a negative value, which causes the pointer address to be decremented and subsequently accessed because ceph_decode_need() only checks that the memory access does not exceed the end address of the allocation. The vulnerability is fixed by changing the data type of payload_len to u32 and introducing additional sanity checks.(CVE-2026-43407)\n\nIn the Linux kernel, when an alias is found through d_splice_alias in the nfs3_proc_create function, if the alias happens to be a directory dentry, the system does not return any error but simply forgets about this alias, leaving the original dentry to be added as negative. This later causes a system crash in nfs_atomic_open_v23/finish_open since a negative dentry is supplied to do_dentry_open. This issue was observed running lustre-racer, where directories and files are created/removed concurrently with the same name and O_EXCL is not used to open files.(CVE-2026-43470)","status":"published","published":"2026-05-22T11:11:22Z","modified":"2026-08-18T01:20:02.121651445Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"UBUNTU-CVE-2025-39980","description":"In the Linux kernel, the following vulnerability has been resolved: nexthop: Forbid FDB status change while nexthop is in a group The kernel forbids the creation of non-FDB nexthop groups with FDB nexthops:  # ip nexthop add id 1 via 192.0.2.1 fdb  # ip nexthop add id 2 group 1  Error: Non FDB nexthop group cannot have fdb nexthops. And vice versa:  # ip nexthop add id 3 via 192.0.2.2 dev dummy1  # ip nexthop add id 4 group 3 fdb  Error: FDB nexthop group can only have fdb nexthops. However, as long as no routes are pointing to a non-FDB nexthop group, the kernel allows changing the type of a nexthop from FDB to non-FDB and vice versa:  # ip nexthop add id 5 via 192.0.2.2 dev dummy1  # ip nexthop add id 6 group 5  # ip nexthop replace id 5 via 192.0.2.2 fdb  # echo $?  0 This configuration is invalid and can result in a NPD [1] since FDB nexthops are not associated with a nexthop device:  # ip route add 198.51.100.1/32 nhid 6  # ping 198.51.100.1 Fix by preventing nexthop FDB status change while the nexthop is in a group:  # ip nexthop add id 7 via 192.0.2.2 dev dummy1  # ip nexthop add id 8 group 7  # ip nexthop replace id 7 via 192.0.2.2 fdb  Error: Cannot change nexthop FDB status while in a group. [1] BUG: kernel NULL pointer dereference, address: 00000000000003c0 [...] Oops: Oops: 0000 [#1] SMP CPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:fib_lookup_good_nhc+0x1e/0x80 [...] Call Trace:  \u003cTASK\u003e  fib_table_lookup+0x541/0x650  ip_route_output_key_hash_rcu+0x2ea/0x970  ip_route_output_key_hash+0x55/0x80  __ip4_datagram_connect+0x250/0x330  udp_connect+0x2b/0x60  __sys_connect+0x9c/0xd0  __x64_sys_connect+0x18/0x20  do_syscall_64+0xa4/0x2a0  entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T08:15:00Z","modified":"2026-11-11T09:39:09.105014899Z","cvss":[{"version":"4.0","score":6.8,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"}],"updated_at":"2026-11-11T10:01:01.00184Z"},{"id":"AZL-68507","title":"CVE-2025-39980 affecting package kernel for versions less than 6.6.112.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T08:15:35Z","modified":"2026-04-21T04:47:29.626222Z","updated_at":"2026-11-02T15:28:08.630357Z"},{"id":"BELL-CVE-2025-39980","status":"published","published":"2025-10-17T06:04:47.235682Z","modified":"2026-06-25T07:18:30.936950382Z","updated_at":"2026-11-02T15:28:22.246535Z"},{"id":"CLSA-2026-1791741836","title":"kernel: Fix of 127 CVEs","description":"- md/raid1,raid10: strip REQ_NOWAIT from member bios {CVE-2025-22125}\n- md/raid1: fix data lost for writemostly rdev {CVE-2025-22125}\n- md/raid1,raid10: don't handle IO error for REQ_RAHEAD and REQ_NOWAIT {CVE-2025-22125}\n- md/raid1,raid10: don't ignore IO flags {CVE-2025-22125}\n- net/sched: netem: fix queue limit check to include reordered packets {CVE-2026-52984}\n- netem: Update sch-\u003eq.qlen before qdisc_tree_reduce_backlog() {CVE-2025-21703}\n- net/sched: netem: account for backlog updates from child qdisc {CVE-2024-56770}\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check {CVE-2026-89818}\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check {CVE-2026-46199}\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg {CVE-2026-46199}\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check {CVE-2026-46230}\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg {CVE-2026-46230}\n- vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE {CVE-2022-48862}\n- vhost: handle error while adding split ranges to iotlb {CVE-2022-48862}\n- vhost: allow batching hint without size {CVE-2022-48862}\n- vhost: fix hung thread due to erroneous iotlb entries {CVE-2022-48862}\n- md raid: fix hang when stopping arrays with metadata through dm-raid {CVE-2026-43309}\n- dm raid: use proper md_ro_state enumerators {CVE-2026-43309}\n- i40e: When removing VF MAC filters, only check PF-set MAC {CVE-2024-26830}\n- i40e: Fix VF MAC filter removal {CVE-2024-26830}\n- i40e: Do not allow untrusted VF to remove administratively set MAC {CVE-2024-26830}\n- netlink: make sure we allow at least one dump skb {CVE-2025-38465}\n- netlink: avoid infinite retry looping in netlink_unicast() {CVE-2025-38465}\n- netlink: Fix rmem check in netlink_broadcast_deliver(). {CVE-2025-38465}\n- netlink: Fix wraparounds of sk-\u003esk_rmem_alloc. {CVE-2025-38465}\n- ipv6: fix possible infinite loop in rt6_fill_node() {CVE-2024-56703}\n- ipv6: prevent infinite loop in rt6_nlmsg_size() {CVE-2024-56703}\n- ipv6: Fix soft lockups in fib6_select_path under high next hop churn {CVE-2024-56703}\n- qede: fix out-of-bounds check for cqe-\u003elen_list[] {CVE-2025-40252}\n- net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() {CVE-2025-40252}\n- scsi: lpfc: apply the HBA_SETUP dev_loss check to SLI4 only {CVE-2024-49891}\n- scsi: lpfc: Validate hdwq pointers before dereferencing in reset/errata paths {CVE-2024-49891}\n- ext4: fix string copying in parse_apply_sb_mount_options() {CVE-2025-71123}\n- ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() {CVE-2025-40198}\n- openvswitch: vport: fix self-deadlock on release of tunnel ports {CVE-2026-31678}\n- openvswitch: defer tunnel netdev_put to RCU release {CVE-2026-31678}\n- blk-iolatency: Fix memory leak on add_disk() failures {CVE-2022-50550}\n- drm/vkms: Fix use after free and double free on init error {CVE-2025-22097}\n- iommu/amd: move wait_on_sem() out of spinlock {CVE-2026-43253}\n- fbdev: bitblit: bound-check glyph index in bit_cursor() {CVE-2026-74635}\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page {CVE-2026-80726}\n- wifi: nl80211: reject beacons with bad HE operation {CVE-2026-97517}\n- sctp: prevent peer transport count overflow {CVE-2026-74469}\n- IB/isert: reject login PDUs declaring more data than was received {CVE-2026-90413}\n- sctp: validate embedded address parameter length {CVE-2026-74287}\n- tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() {CVE-2026-98374}\n- ALSA: usb-audio: Fix a DMA to stack memory bug {CVE-2024-53197}\n- ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices {CVE-2024-53197}\n- USB: core: Limit the length of unkillable synchronous timeouts {CVE-2026-43428}\n- ext4: refresh inline data size before write operations {CVE-2025-68264}\n- net, bpf: check master for NULL in xdp_master_redirect() {CVE-2026-64545}\n- iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() {CVE-2026-31505}\n- dm cache: fix flushing uninitialized delayed_work on cache_ctr error {CVE-2024-50280}\n- net: hns3: add vlan list lock to protect vlan list {CVE-2022-49182}\n- spi: fix statistics allocation {CVE-2026-23475} https://git.kernel.org/linus/dee0774bbb2abb172e9069ce5ffef579b12b3ae9 https://nvd.nist.gov/vuln/detail/CVE-2026-23475 https://access.redhat.com/security/cve/CVE-2026-23475 https://ubuntu.com/security/CVE-2026-23475 almalinux9.2esu: Issue: ELSCVE-153557 (https://cloudlinux.atlassian.net/browse/ELSCVE-153557) CVSS: 5.5\n- net: openvswitch: remove never-working support for setting nsh fields {CVE-2025-40254}\n- mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr {CVE-2025-21938}\n- drm/hyperv: Fix address space leak when Hyper-V DRM device is removed {CVE-2025-21978}\n- KVM: x86: Don't (re)check L1 intercepts when completing userspace I/O {CVE-2025-40026}\n- vsock: fix lock inversion in vsock_assign_transport() {CVE-2025-40231}\n- ext4: fix use-after-free in update_super_work when racing with umount {CVE-2026-31446}\n- dm cache metadata: fix memory leak on metadata abort retry {CVE-2026-53060}\n- netfilter: ipset: fix refcount race between list:set GC and swap {CVE-2026-74748}\n- net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD {CVE-2026-68288}\n- openvswitch: fix GSO userspace truncation underflow {CVE-2026-68123}\n- drm/amd/display: use kvzalloc to allocate struct dc {CVE-2026-68436}\n- sctp: avoid auth_enable sysctl UAF during netns teardown {CVE-2026-68162}\n- wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin {CVE-2026-68362}\n- usb: roles: fix NULL pointer issue when put module's reference {CVE-2024-26747}\n- drm/vmwgfx: Validate vmw_surface_metadata::array_size {CVE-2026-68446}\n- smb: client: Fix refcount leak for cifs_sb_tlink {CVE-2025-40103}\n- bpf: Free reuseport cBPF prog after RCU grace period {CVE-2026-52910}\n- ceph: fix BUG_ON in __ceph_build_xattrs_blob() due to stale blob size {CVE-2026-52961}\n- bpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded {CVE-2026-23310}\n- block: stop the timeout timer when releasing a never added disk {CVE-2026-80589}\n- net/mlx5: fw_tracer, return NULL on create error {CVE-2026-74717}\n- ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops {CVE-2026-74657}\n- net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer {CVE-2026-64034}\n- nfsd: fix fcache_disposal UAF by inlining dispose state into nfsd_net {CVE-2026-89682}\n- nvmet-auth: validate reply message payload bounds against transfer length {CVE-2026-64319}\n- crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() {CVE-2026-64438}\n- perf/core: Fix group leader use-after-free after sibling detach {CVE-2026-74637}\n- smb: client: mask server-provided mode to 07777 in modefromsid {CVE-2026-64379}\n- dm-verity: fix buffer overflow in FEC calculation {CVE-2026-72098}\n- nvmet-auth: reject short AUTH_RECEIVE buffers {CVE-2026-72130}\n- drm/amdgpu: Fix context pstate override handling {CVE-2026-68273}\n- nvmet: fix NULL pointer dereference in nvmet_execute_identify_ns_zns() {CVE-2026-90228}\n- nvmet: fix error handling in nvmet_execute_identify_cns_cs_ns() {CVE-2026-90228}\n- svcrdma: Reject Write/Reply chunks with segcount 0 {CVE-2026-93228}\n- smb: client: fix heap overflow in DACL owner/group rewrite {CVE-2026-97555}\n- ima: Handle error code returned by ima_filter_rule_match() {CVE-2025-68740}\n- NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags {CVE-2025-68764}\n- dm: fix unlocked test for dm_suspended_md {CVE-2026-46327}\n- drm/amd/display: Validate GPIO pin LUT table size before iterating {CVE-2026-64097}\n- i40e: fix validation of VF state in get resources {CVE-2025-39969}\n- l2tp: prevent possible tunnel refcount underflow {CVE-2024-49940}\n- netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}\n- crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg {CVE-2025-39964}\n- bnx2x: fix potential memory leak in bnx2x_tpa_stop() {CVE-2022-3542}\n- scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read {CVE-2026-89846}\n- xfrm: ah6: validate routing header segments_left {CVE-2026-80844}\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() {CVE-2026-74680}\n- bonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor {CVE-2026-74726}\n- net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master {CVE-2026-53069}\n- net/sched: cls_bpf: reject dev-bound programs bound to a different device {CVE-2026-74736}\n- xfrm: input: hold netns during deferred transport reinjection {CVE-2026-63919}\n- ASoC: rt700-sdw: always drain jack work on remove {CVE-2026-93185}\n- ima: fix out-of-bounds read in xattr_verify() {CVE-2026-74671}\n- net/openvswitch: check Ethernet header length in key_extract() {CVE-2026-74701}\n- bpf: reject BPF_PSEUDO_FUNC reference to the main program {CVE-2026-98075}\n- selinux: check connect-related permissions on TCP Fast Open {CVE-2026-72243}\n- ppp_synctty: ensure a writeable skb header {CVE-2026-97964}\n- nvme-rdma: fix -EIO cleanup order in queue_rq {CVE-2026-98154}\n- audit: avoid dropping live tree ref on fsnotify rule autoremove {CVE-2026-89643}\n- macvlan: inherit needed_headroom and needed_tailroom from lowerdev {CVE-2026-74743}\n- drm/gud: NUL-terminate TV mode names read from the device {CVE-2026-89817}\n- NFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check {CVE-2026-89711}\n- nvdimm: pmem: keep PREFLUSH before data writes {CVE-2026-98161}\n- net/ip6_tunnel: Prevent perpetual tunnel growth {CVE-2025-40173}\n- ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control {CVE-2026-72261}\n- net: bridge: stop fast-leave after deleting a port group {CVE-2026-74480}\n- Bluetooth: ISO: fix UAF in iso_recv_frame {CVE-2026-63946}\n- netfilter: nf_conntrack: use get_unaligned_be32() in tcp_sack() {CVE-2026-97417}\n- net/mlx5e: Fix use-after-free race in sample_restore_put() {CVE-2026-98016}\n- RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters {CVE-2026-100075}\n- sctp: fix race between sctp_wait_for_connect and peeloff {CVE-2026-63971}\n- xfs: fix ilock leak on error in xfs_dq_get_next_id {CVE-2026-80534}\n- nexthop: Initialize extack in remove_nh_grp_entry() {CVE-2026-98031}\n- drm/amd/display: set new_stream to NULL after release {CVE-2026-68236}\n- ASoC: ops: Consistently treat platform_max as control value {CVE-2025-37889}\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet {CVE-2026-80574}\n- crypto: essiv - Check ssize for decryption and in-place encryption {CVE-2025-40019}\n- Squashfs: fix uninit-value in squashfs_get_parent {CVE-2025-40049}\n- scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() {CVE-2025-40115}\n- nexthop: Forbid FDB status change while nexthop is in a group {CVE-2025-39980}\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() {CVE-2026-31570}\n- libceph: Use u32 for non-negative values in ceph_monmap_decode() {CVE-2026-43405}\n- perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling {CVE-2022-49781}\n- ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe {CVE-2025-68241}\n- net: ipv6: flowlabel: defer exclusive option free until RCU teardown {CVE-2026-31680}\n- KVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight {CVE-2025-38455}\n- bpf: reject direct access to nullable PTR_TO_BUF pointers {CVE-2026-43333}\n- ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup() {CVE-2026-53221}\n- KVM: x86: Play nice with protected guests in complete_hypercall_exit() {CVE-2024-55881}\n- pid: Add a judgment for ns null in pid_nr_ns {CVE-2025-40178}\n- arm64/fpsimd: Discard stale CPU state when handling SME traps {CVE-2025-38170}\n- vdpa_sim_blk: reject out-of-range sector starts {CVE-2026-97991}\n- ALSA: timer: drain a slave's callback before its master detaches it {CVE-2026-68201}\n- nvmet-rdma: handle inline data with a nonzero offset {CVE-2026-72129}\n- libceph: validate banner payload length {CVE-2026-90067}\n- tls: fix handling of zero-length records on the rx_list {CVE-2025-39682}","status":"published","published":"2026-10-23T12:35:14Z","modified":"2026-10-26T09:43:28.160433661Z","updated_at":"2026-11-02T15:43:50.599064Z"},{"id":"CLSA-2026-1791800936","title":"kernel: Fix of 191 CVEs","description":"- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check {CVE-2026-89818}\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check {CVE-2026-46199}\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg {CVE-2026-46199}\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check {CVE-2026-46230}\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg {CVE-2026-46230}\n- openvswitch: vport: fix self-deadlock on release of tunnel ports {CVE-2026-46165}\n- openvswitch: defer tunnel netdev_put to RCU release {CVE-2026-31678}\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs {CVE-2026-74642}\n- ALSA: usb-audio: fix use-after-free in ump_to_endpoint() {CVE-2026-74501}\n- NFS: Decrement refcounts if allocating nfs_free_stateid_data fails {CVE-2026-74730}\n- NFS: Pin the 'struct nfs_server' during a FREE_STATEID call {CVE-2026-74730}\n- exec: do_close_on_exec() before taking exec_update_lock {CVE-2026-64371}\n- proc: Fix broken error paths for namespace links {CVE-2026-64371}\n- proc: protect ptrace_may_access() with exec_update_lock (part 1) {CVE-2026-64371}\n- ALSA: timer: Clear SNDRV_TIMER_IFLG_DEAD once the close completes {CVE-2026-74503}\n- ALSA: timer: Forcibly close timer instances at closing {CVE-2026-53193}\n- usb: typec: ucsi: Fix race condition and ordering in port unregistration {CVE-2026-74441}\n- arp: do not assume dev_hard_header() does not change skb-\u003ehead {CVE-2026-22988}\n- netfilter: nft_ct: fix use-after-free in timeout object destroy {CVE-2026-31665}\n- md/raid10: fix writes_pending and barrier reference leaks on discard failures {CVE-2026-72438}\n- md/raid10: fix deadlock with check operation and nowait requests {CVE-2026-46050}\n- mm: introduce and use {pgd,p4d}_populate_kernel() {CVE-2025-39844}\n- vsock/virtio: fix zerocopy completion for multi-skb sends {CVE-2026-53365}\n- vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting {CVE-2026-52994}\n- mm: do file ownership checks with the proper mount idmap {CVE-2026-64294}\n- udf: validate VAT header length against the VAT inode size {CVE-2026-64323}\n- SUNRPC: auth_gss: fix memory leaks in XDR decoding error paths {CVE-2026-45870}\n- Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig {CVE-2026-53208}\n- slip: bound decode() reads against the compressed packet length {CVE-2026-45843}\n- net: tls: fix strparser anchor skb leak on offload RX setup failure {CVE-2026-52974}\n- netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion {CVE-2026-23272}\n- rbd: Reset positive result codes to zero in object map update path {CVE-2026-68131}\n- netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() {CVE-2026-23458}\n- mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr {CVE-2025-21938}\n- bpf: Fix NULL deref in map_kptr_match_type for scalar regs {CVE-2026-53032}\n- bpf: Explicitly check accesses to bpf_sock_addr {CVE-2025-40078}\n- nexthop: Forbid FDB status change while nexthop is in a group {CVE-2025-39980}\n- bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN {CVE-2026-31525}\n- x86/amd_nb: Use rdmsr_safe() in amd_get_mmconfig_range() {CVE-2025-21913}\n- ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple() {CVE-2024-57994}\n- drm/i915/vrr: require valid min/max vfreq for VRR {CVE-2026-68254}\n- libceph: handle rbtree insertion error in decode_choose_args() {CVE-2026-52954}\n- gfs2: prevent NULL pointer dereference during unmount {CVE-2026-53048}\n- smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path {CVE-2026-31708}\n- ext4: reject mount if bigalloc with s_first_data_block != 0 {CVE-2026-31447}\n- NFSD: Fix crash in nfsd4_read_release() {CVE-2025-40324}\n- netfilter: x_tables: guard option walkers against 1-byte tail reads {CVE-2026-43452}\n- smb: client: Fix refcount leak for cifs_sb_tlink {CVE-2025-40103}\n- smb: client: harden POSIX SID length parsing {CVE-2026-64380}\n- crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() {CVE-2026-64438}\n- bpf: Allow LPM map access from sleepable BPF programs {CVE-2026-64352}\n- bpf: Consistently use bpf_rcu_lock_held() everywhere {CVE-2026-64352}\n- net/sched: act_ct: fix sk_buff leak when the header checks reject a packet {CVE-2026-74621}\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_akai_output() {CVE-2026-74499}\n- net/packet: reset the MAC header on the packet-socket transmit path {CVE-2026-74667}\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" {CVE-2026-74604}\n- ipv4: fix use-after-free in fib_nhc_update_mtu() {CVE-2026-74656}\n- ipv4: igmp: remove multicast group from hash table on device destruction {CVE-2026-64423}\n- usb: typec: tcpm: Validate SVID index in svdm_consume_modes() {CVE-2026-64330}\n- mpls: reload header after pskb_may_pull() {CVE-2026-89555}\n- scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer {CVE-2026-74556}\n- sctp: keep chunk-\u003etransport in step with the list it is queued on {CVE-2026-74588}\n- ipvs: clear IPv4 options after rebasing tunnel ICMP errors {CVE-2026-74669}\n- USB: ldusb: fix use-after-free on disconnect race {CVE-2026-64343}\n- USB: legousbtower: fix use-after-free on disconnect race {CVE-2026-64340}\n- spi: fsl-lpspi: terminate the RX channel on TX prepare failure path {CVE-2026-64303}\n- usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove {CVE-2026-64329}\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib {CVE-2026-31566}\n- ALSA: usb-audio: Add sanity check for OOB writes at silencing {CVE-2026-43279}\n- bpf, sockmap: Fix sk_redir use-after-free in send verdict {CVE-2026-74589}\n- net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer {CVE-2026-64034}\n- proc: protect ptrace_may_access() with exec_update_lock (FD links) {CVE-2026-64375}\n- ALSA: ump: Fix buffer overflow at UMP SysEx message conversion {CVE-2025-37891}\n- drm/amdkfd: Fix buffer overflow in SDMA queue checkpoint/restore on GFX11 {CVE-2026-53143}\n- crypto: qat - protect service table iterations with service_lock {CVE-2026-64305}\n- net: tun: bound receive headroom {CVE-2026-81000}\n- smb: client: reject overlapping data areas in SMB2 responses {CVE-2026-64257}\n- smb: client: restrict implied bcc[0] exemption to responses without data area {CVE-2026-64448}\n- xsk: require at least 16 bytes of TX metadata {CVE-2026-74710}\n- drm/amdgpu: reject oversized IBs with per-ring packet limits {CVE-2026-80576}\n- ipvlan: inherit needed_headroom and needed_tailroom from phy_dev {CVE-2026-74744}\n- smb: client: fix use-after-free of iface in cifs_try_adding_channels() {CVE-2026-74608}\n- smb: mark the new channel addition log as informational log with cifs_info {CVE-2026-74608}\n- smb: client: Fix use-after-free in cifs_try_adding_channels() {CVE-2026-74608}\n- udf: reject VAT indexes equal to the entry count {CVE-2026-89525}\n- drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 {CVE-2026-45878}\n- smb: client: fix double-free in SMB2_open() replay {CVE-2026-64382}\n- smb: client: fix change notify replay double-free {CVE-2026-64384}\n- smb: client: fix query_info() replay double-free {CVE-2026-64386}\n- smb: client: mask server-provided mode to 07777 in modefromsid {CVE-2026-64379}\n- net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete {CVE-2026-72072}\n- netfilter: nf_conntrack_sip: don't use simple_strtoul {CVE-2026-52986}\n- video: screen_info: Relocate framebuffers behind PCI bridges {CVE-2025-38427}\n- erofs: fix the out-of-bounds nameoff handling for trailing dirents {CVE-2026-46078}\n- ceph: fix memory leak in ceph_direct_read_write() {CVE-2024-56710}\n- KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 {CVE-2026-46071}\n- drm/amdgpu: Release VFCT ACPI table reference {CVE-2026-68238}\n- dm cache metadata: fix memory leak on metadata abort retry {CVE-2026-53060}\n- netfilter: nfnetlink_osf: fix out-of-bounds read on option matching {CVE-2026-52999}\n- netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() {CVE-2026-23457}\n- bpf: Preserve id of register in sync_linked_regs() {CVE-2026-45933}\n- bpf: Fix regsafe() for pointers to packet {CVE-2026-43030}\n- ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe {CVE-2025-68241}\n- perf/core: Order the PMU list to fix warning about unordered pmu_ctx_list {CVE-2025-21895}\n- net: openvswitch: remove never-working support for setting nsh fields {CVE-2025-40254}\n- tracing: Fix race condition in kprobe initialization causing NULL pointer dereference {CVE-2025-40042}\n- Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled {CVE-2026-68085}\n- media: pwc: Return queued buffers on start_streaming() failure {CVE-2026-68216}\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state {CVE-2026-31773}\n- Bluetooth: fix memory leak in error path of hci_alloc_dev() {CVE-2026-53252}\n- mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations {CVE-2026-31394}\n- ext4: refresh inline data size before write operations {CVE-2025-68264}\n- kernfs: Relax constraint in draining guard {CVE-2025-38282}\n- netfilter: x_tables: ensure names are nul-terminated {CVE-2026-43028}\n- nfsd: fix fcache_disposal UAF by inlining dispose state into nfsd_net {CVE-2026-89682}\n- smb: client: Fix next buffer leak in receive_encrypted_standard() {CVE-2026-64381}\n- can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER {CVE-2026-72125}\n- can: isotp: use unconditional synchronize_rcu() in isotp_release() {CVE-2026-72126}\n- netfilter: flowtable: publish GC-visible tuple last {CVE-2026-74746}\n- mm/debug_vm_pgtable: clear page table entries at destroy_args() {CVE-2025-39776}\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs {CVE-2026-74682}\n- ipv6: prevent in6_dev_get() from resurrecting inet6_dev {CVE-2026-74630}\n- ip6_tunnel: clear skb2-\u003ecb[] in ip6ip6_err() {CVE-2026-74597}\n- tipc: read le-\u003elink under the node lock in tipc_node_link_down() {CVE-2026-74609}\n- net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes {CVE-2026-64422}\n- rhashtable: clear stale iter-\u003ep on table restart {CVE-2026-64563}\n- bridge: stp: Fix a potential use-after-free when deleting a bridge {CVE-2026-72389}\n- sctp: validate cookie AUTH state before use {CVE-2026-74752}\n- sctp: fix use-after-free of cached ASCONF chunk {CVE-2026-74587}\n- USB: idmouse: fix use-after-free on disconnect race {CVE-2026-64344}\n- USB: iowarrior: fix use-after-free on disconnect race {CVE-2026-64341}\n- vhost: reset the vring metadata cache on vring reconfiguration {CVE-2026-74580}\n- usb: free iso schedules on failed submit {CVE-2026-64348}\n- udf: validate sparing table length as an entry count, not a byte count {CVE-2026-64322}\n- drm/i915: Fix potential UAF in TTM object purge {CVE-2026-63884}\n- packet: use consistent hard_header_len in non-ring send paths {CVE-2026-74582}\n- nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page {CVE-2026-64320}\n- crypto: qat - validate RSA CRT component lengths {CVE-2026-64304}\n- ALSA: usx2y: bound the hwdep mmap fault offset {CVE-2026-74641}\n- drm/xe: Use local fence in error path of xe_migrate_clear {CVE-2025-37869}\n- nvmet-auth: validate reply message payload bounds against transfer length {CVE-2026-64319}\n- ip6_tunnel: clear skb2-\u003ecb[] in ip4ip6_err() {CVE-2026-43037}\n- smb: client: fix query directory replay double-free {CVE-2026-64387}\n- tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() {CVE-2026-68289}\n- xfs: don't swallow dquot recovery verification errors {CVE-2026-80529}\n- enic: fix tx_hang_reset use-after-free on device removal {CVE-2026-74725}\n- net: mana: validate rx_req_idx to prevent out-of-bounds array access {CVE-2026-64018}\n- bpf: Simplify sanitize_err() signature {CVE-2026-74720}\n- bpf: Preserve pointer state for commuted arithmetic {CVE-2026-74720}\n- sctp: fix race between sctp_wait_for_connect and peeloff {CVE-2026-63971}\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests {CVE-2026-43493}\n- smb: client: fix double-free in SMB2_flush() replay {CVE-2026-64383}\n- smb: client: fix double-free in SMB2_ioctl() replay {CVE-2026-64385}\n- smb: client: fix double-free in SMB2_close() replay {CVE-2026-64597}\n- locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() {CVE-2026-72069}\n- dm-verity: fix buffer overflow in FEC calculation {CVE-2026-72098}\n- dm-verity-fec: replace {MAX,MIN}_RSN with {MIN,MAX}_ROOTS {CVE-2026-72098}\n- dm-verity-fec: fix the size of dm_verity_fec_io::erasures {CVE-2026-72098}\n- netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}\n- locking/spinlock/debug: Fix data-race in do_raw_write_lock {CVE-2025-68336}\n- hsr: Remove WARN_ONCE() in hsr_addr_is_self(). {CVE-2026-53353}\n- ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw(). {CVE-2025-22005}\n- x86/fpu: Ensure shadow stack is active before \"getting\" registers {CVE-2025-21632}\n- perf/core: Add RCU read lock protection to perf_iterate_ctx() {CVE-2025-21889}\n- KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU {CVE-2026-31593}\n- genetlink: fix genl_bind() invoking bind() after -EPERM {CVE-2025-39926}\n- fs: udf: fix OOB read in lengthAllocDescs handling {CVE-2025-40044}\n- rxrpc: Only put the call ref if one was acquired {CVE-2026-31638}\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() {CVE-2026-45835}\n- bpf: Fix OOB in pcpu_init_value {CVE-2026-53076}\n- pid: Add a judgment for ns null in pid_nr_ns {CVE-2025-40178}\n- arm64: ptrace: fix partial SETREGSET for NT_ARM_FPMR {CVE-2024-57878}\n- kunit: Fix potential null dereference in kunit_device_driver_test() {CVE-2024-56773}\n- arm64/fpsimd: Discard stale CPU state when handling SME traps {CVE-2025-38170}\n- mm: hugetlb: avoid soft lockup when mprotect to large memory area {CVE-2025-40153}\n- perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value. {CVE-2025-37936}\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls {CVE-2026-46131}\n- netfilter: nf_tables: always walk all pending catchall elements {CVE-2026-23278}\n- openvswitch: validate MPLS set/set_masked payload length {CVE-2026-31679}\n- tipc: Fix use-after-free in tipc_mon_reinit_self(). {CVE-2025-40280}\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing {CVE-2025-68185}\n- devlink: fix xa_alloc_cyclic() error handling {CVE-2025-22017}\n- net/sched: act_mirred: fix wrong device for mac_header_xmit check in tcf_blockcast_redir {CVE-2026-53014}\n- ethtool: cmis_cdb: use correct rpl size in ethtool_cmis_module_poll() {CVE-2025-37791}\n- xfrm: prevent policy_hthresh.work from racing with netns teardown {CVE-2026-31516}\n- blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() {CVE-2026-53126}\n- rxrpc: Fix key reference count leak from call-\u003ekey {CVE-2026-31639}\n- xsk: fix refcount underflow in error path {CVE-2023-53698}\n- net/sched: sch_cake: drop WARN_ON(1) for malformed packets in ACK filter {CVE-2026-74704}\n- octeontx2-af: Workaround SQM/PSE stalls by disabling sticky {CVE-2026-43296}\n- drm/xe/userptr: fix EFAULT handling {CVE-2025-21880}\n- bpf: fix mm lifecycle in open-coded task_vma iterator {CVE-2026-53085}\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() {CVE-2026-46201}\n- udp: fix potential use-after-free in tunnel segmentation {CVE-2026-74705}\n- netfilter: require Ethernet MAC header before using eth_hdr() {CVE-2026-53131}\n- netfilter: ipset: stop hash:* range iteration at end {CVE-2026-52921}\n- ipvs: clear the svc scheduler ptr early on edit {CVE-2026-53270}\n- tee: fix NULL pointer dereference in tee_shm_put {CVE-2025-39865}\n- KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU {CVE-2026-64287}\n- regulator: core: fix locking in regulator_resolve_supply() error path {CVE-2026-46252}\n- tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() {CVE-2026-46196}\n- exit: prevent preemption of oopsing TASK_DEAD task {CVE-2026-46173}\n- EFI/CPER: don't dump the entire memory region {CVE-2026-43171}\n- libceph: Avoid using invalid osd indices from primary_temp {CVE-2026-80558}\n- RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() {CVE-2026-46178}\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls {CVE-2026-53350}\n- svcrdma: Clear sc_cm_id when ADDR_CHANGE replacement fails {CVE-2026-89534}\n- mptcp: avoid deadlock on fallback while reinjecting\n- mptcp: plug races between subflow fail and subflow creation {CVE-2025-38552}\n- mptcp: make fallback action and fallback decision atomic","status":"published","published":"2026-10-21T10:25:55Z","modified":"2026-10-26T09:43:19.007549271Z","updated_at":"2026-11-02T15:43:50.599064Z"},{"id":"CVE-2025-39980","title":"nexthop: Forbid FDB status change while nexthop is in a group","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnexthop: Forbid FDB status change while nexthop is in a group\n\nThe kernel forbids the creation of non-FDB nexthop groups with FDB\nnexthops:\n\n # ip nexthop add id 1 via 192.0.2.1 fdb\n # ip nexthop add id 2 group 1\n Error: Non FDB nexthop group cannot have fdb nexthops.\n\nAnd vice versa:\n\n # ip nexthop add id 3 via 192.0.2.2 dev dummy1\n # ip nexthop add id 4 group 3 fdb\n Error: FDB nexthop group can only have fdb nexthops.\n\nHowever, as long as no routes are pointing to a non-FDB nexthop group,\nthe kernel allows changing the type of a nexthop from FDB to non-FDB and\nvice versa:\n\n # ip nexthop add id 5 via 192.0.2.2 dev dummy1\n # ip nexthop add id 6 group 5\n # ip nexthop replace id 5 via 192.0.2.2 fdb\n # echo $?\n 0\n\nThis configuration is invalid and can result in a NPD [1] since FDB\nnexthops are not associated with a nexthop device:\n\n # ip route add 198.51.100.1/32 nhid 6\n # ping 198.51.100.1\n\nFix by preventing nexthop FDB status change while the nexthop is in a\ngroup:\n\n # ip nexthop add id 7 via 192.0.2.2 dev dummy1\n # ip nexthop add id 8 group 7\n # ip nexthop replace id 7 via 192.0.2.2 fdb\n Error: Cannot change nexthop FDB status while in a group.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 00000000000003c0\n[...]\nOops: Oops: 0000 [#1] SMP\nCPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014\nRIP: 0010:fib_lookup_good_nhc+0x1e/0x80\n[...]\nCall Trace:\n \u003cTASK\u003e\n fib_table_lookup+0x541/0x650\n ip_route_output_key_hash_rcu+0x2ea/0x970\n ip_route_output_key_hash+0x55/0x80\n __ip4_datagram_connect+0x250/0x330\n udp_connect+0x2b/0x60\n __sys_connect+0x9c/0xd0\n __x64_sys_connect+0x18/0x20\n do_syscall_64+0xa4/0x2a0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T07:56:00.275Z","modified":"2026-11-11T02:31:14.444475357Z","updated_at":"2026-11-11T11:06:33.7068Z"},{"id":"DEBIAN-CVE-2025-39980","description":"In the Linux kernel, the following vulnerability has been resolved:  nexthop: Forbid FDB status change while nexthop is in a group  The kernel forbids the creation of non-FDB nexthop groups with FDB nexthops:   # ip nexthop add id 1 via 192.0.2.1 fdb  # ip nexthop add id 2 group 1  Error: Non FDB nexthop group cannot have fdb nexthops.  And vice versa:   # ip nexthop add id 3 via 192.0.2.2 dev dummy1  # ip nexthop add id 4 group 3 fdb  Error: FDB nexthop group can only have fdb nexthops.  However, as long as no routes are pointing to a non-FDB nexthop group, the kernel allows changing the type of a nexthop from FDB to non-FDB and vice versa:   # ip nexthop add id 5 via 192.0.2.2 dev dummy1  # ip nexthop add id 6 group 5  # ip nexthop replace id 5 via 192.0.2.2 fdb  # echo $?  0  This configuration is invalid and can result in a NPD [1] since FDB nexthops are not associated with a nexthop device:   # ip route add 198.51.100.1/32 nhid 6  # ping 198.51.100.1  Fix by preventing nexthop FDB status change while the nexthop is in a group:   # ip nexthop add id 7 via 192.0.2.2 dev dummy1  # ip nexthop add id 8 group 7  # ip nexthop replace id 7 via 192.0.2.2 fdb  Error: Cannot change nexthop FDB status while in a group.  [1] BUG: kernel NULL pointer dereference, address: 00000000000003c0 [...] Oops: Oops: 0000 [#1] SMP CPU: 6 UID: 0 PID: 367 Comm: ping Not tainted 6.17.0-rc6-virtme-gb65678cacc03 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:fib_lookup_good_nhc+0x1e/0x80 [...] Call Trace:  \u003cTASK\u003e  fib_table_lookup+0x541/0x650  ip_route_output_key_hash_rcu+0x2ea/0x970  ip_route_output_key_hash+0x55/0x80  __ip4_datagram_connect+0x250/0x330  udp_connect+0x2b/0x60  __sys_connect+0x9c/0xd0  __x64_sys_connect+0x18/0x20  do_syscall_64+0xa4/0x2a0  entry_SYSCALL_64_after_hwframe+0x4b/0x53","status":"published","published":"2025-10-15T08:15:35.887Z","modified":"2026-11-11T10:00:38.427778476Z","updated_at":"2026-11-11T10:35:16.464644Z"},{"id":"DLA-4379-1","title":"linux-6.1 - security update","status":"published","published":"2025-11-25T00:00:00Z","modified":"2025-11-25T18:32:49.207532Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DLA-4404-1","title":"linux - security update","status":"published","published":"2025-12-12T00:00:00Z","modified":"2025-12-12T14:30:10.212698Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DSA-6053-1","title":"linux - security update","status":"published","published":"2025-11-11T00:00:00Z","modified":"2025-11-11T20:17:48.223249Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"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: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":"ROOT-OS-DEBIAN-11-CVE-2025-39980","title":"CVE-2025-39980 in linux - Patched by Root","description":"Root has patched CVE-2025-39980 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:16:28.016434797Z","updated_at":"2026-11-02T15:53:29.631993Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2025-39980","title":"CVE-2025-39980 in linux - Patched by Root","description":"Root has patched CVE-2025-39980 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:16:00.199003613Z","updated_at":"2026-11-02T15:53:31.514195Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-39980","title":"CVE-2025-39980 in linux - Patched by Root","description":"Root has patched CVE-2025-39980 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:15:29.249918604Z","updated_at":"2026-11-06T16:28:43.316846Z"},{"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-8033-1","title":"linux, linux-aws, linux-gcp, linux-gke, linux-gkeop, linux-hwe-5.15, linux-ibm, linux-ibm-5.15, linux-lowlatency, linux-lowlatency-hwe-5.15 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-12T10:40:51Z","modified":"2026-11-03T21:18:42.391608877Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8033-2","title":"linux-intel-iot-realtime, 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-12T10:55:16Z","modified":"2026-11-03T21:17:44.370804235Z","updated_at":"2026-11-03T21:43:54.166508Z"},{"id":"USN-8033-3","title":"linux-aws-fips, linux-fips, linux-gcp-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-12T11:12:38Z","modified":"2026-11-03T21:18:28.453793988Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8033-4","title":"linux-aws-5.15 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-13T09:44:17Z","modified":"2026-11-03T21:18:29.716748087Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8033-5","title":"linux-gcp-5.15, linux-kvm, linux-oracle, linux-oracle-5.15 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-17T14:57:00Z","modified":"2026-11-03T21:18:05.350644816Z","updated_at":"2026-11-03T21:43:48.662011Z"},{"id":"USN-8033-6","title":"linux-nvidia 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-17T15:53:41Z","modified":"2026-11-03T21:17:11.424709754Z","updated_at":"2026-11-03T21:44:00.661154Z"},{"id":"USN-8033-7","title":"linux-intel-iotg-5.15, linux-xilinx-zynqmp 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-19T10:10:15Z","modified":"2026-11-03T21:18:27.869696239Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8033-8","title":"linux-intel-iotg 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249)\n","status":"published","published":"2026-02-19T14:23:05Z","modified":"2026-11-03T21:18:29.298999849Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8034-1","title":"linux-nvidia-tegra, linux-nvidia-tegra-5.15 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249, CVE-2025-71162)\n","status":"published","published":"2026-02-12T11:24:57Z","modified":"2026-11-03T21:18:30.701874957Z","updated_at":"2026-11-03T21:43:43.010304Z"},{"id":"USN-8034-2","title":"linux-nvidia-tegra-igx 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  - Nios II architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - GPU drivers;\n  - HW tracing;\n  - Input Device (Miscellaneous) drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - SCSI subsystem;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network sockets;\n  - XFRM subsystem;\n  - Control group (cgroup);\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Tracing infrastructure;\n  - Memory management;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - NFC subsystem;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Intel ASoC drivers;\n  - USB sound devices;\n(CVE-2024-53114, CVE-2024-56538, CVE-2024-58011, CVE-2025-21861,\nCVE-2025-22058, CVE-2025-23143, CVE-2025-38236, CVE-2025-38248,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40060, CVE-2025-40068, CVE-2025-40070, CVE-2025-40078,\nCVE-2025-40081, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40111, CVE-2025-40112, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40118, CVE-2025-40120, CVE-2025-40121,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40134, CVE-2025-40140, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40167, CVE-2025-40171, CVE-2025-40173, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40194, CVE-2025-40200, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-68249, CVE-2025-71162)\n","status":"published","published":"2026-02-17T15:06:47Z","modified":"2026-11-03T21:19:15.415859882Z","updated_at":"2026-11-03T21:43:32.336286Z"},{"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"}]},"sources_more":{"osv":6}}