{"id":"CVE-2025-38713","aliases":["BELL-CVE-2025-38713","CLSA-2026-1773832495","CLSA-2026-1773872435","CLSA-2026-1775224807","CLSA-2026-1775779453","DEBIAN-CVE-2025-38713","DLA-4327-1","DLA-4328-1","DSA-6009-1","EUVD-2025-26756","GHSA-f84m-84r4-h992","MGASA-2025-0234","MGASA-2025-0235","OESA-2026-1275","OESA-2026-1303","OESA-2026-1304","OESA-2026-1305","ROOT-OS-DEBIAN-11-CVE-2025-38713","ROOT-OS-DEBIAN-12-CVE-2025-38713","ROOT-OS-UBUNTU-2204-CVE-2025-38713","ROOT-OS-UBUNTU-2404-CVE-2025-38713","SUSE-SU-2025:03600-1","SUSE-SU-2025:03613-1","SUSE-SU-2025:03614-1","SUSE-SU-2025:03615-1","SUSE-SU-2025:03626-1","SUSE-SU-2025:03628-1","SUSE-SU-2025:03634-1","SUSE-SU-2025:20851-1","SUSE-SU-2025:20861-1","SUSE-SU-2025:20870-1","SUSE-SU-2025:20898-1","SUSE-SU-2025:3716-1","SUSE-SU-2025:3751-1","SUSE-SU-2025:3761-1","SUSE-SU-2025:4057-1","SUSE-SU-2025:4132-1","SUSE-SU-2025:4141-1","SUSE-SU-2025:4315-1","UBUNTU-CVE-2025-38713","USN-7909-1","USN-7909-2","USN-7909-3","USN-7909-4","USN-7909-5","USN-7910-1","USN-7910-2","USN-7933-1","USN-7938-1","USN-8028-1","USN-8028-2","USN-8028-3","USN-8028-4","USN-8028-5","USN-8028-6","USN-8028-7","USN-8028-8","USN-8031-1","USN-8031-2","USN-8031-3","USN-8052-1","USN-8052-2","USN-8074-1","USN-8074-2","USN-8126-1"],"status":"published","title":"hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00174,"percentile":0.06952,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-125"],"published":"2025-09-04T15:33:03Z","modified":"2026-11-11T09:39:07Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.151-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.44-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.4.297","5.10.241","5.15.190","6.1.149","6.6.103","6.12.43","6.15.11","6.16.2"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.153-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.43-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.16.3-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1097.104~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1102.111~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1097.106~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-163.173~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1091.94~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1092.98~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-163.173~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1049.49~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1094.100~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1092.96~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-163.173"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1097.104"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1046.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1101.110"],"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-1102.111.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1046.53~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1097.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1047.50~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1093.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1080.88"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-100.100~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1091.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1044.44~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1092.98"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1089.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-163.173"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-100.100.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1092.93"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1046.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1049.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1038.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1094.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1043.44~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1091.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-100.100~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1061.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1081.83"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1089.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1096.105"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1041.42~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1097.104+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1101.110+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-163.173+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1097.106+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-100.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1046.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1046.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1046.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1039.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1047.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1043.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1030.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1044.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-100.100.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1046.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1046.49.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1043.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1047.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1023.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1016.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2037.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1041.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1046.49+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1046.52+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-100.100+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1047.50+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.147-r0"},{"fixed":"6.1.151-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.41-r0"},{"fixed":"6.12.44-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:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-254-tuxcare.els42","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-254-tuxcare.els42","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-254-tuxcare.els42","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-254-tuxcare.els42-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-254-tuxcare.els42-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-254-tuxcare.els52","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-cloud-tools-4.15.0-254-tuxcare.els52","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-tools-4.15.0-254-tuxcare.els52","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-254-tuxcare.els52-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-254-tuxcare.els52-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-254.265~16.04.1"}]}],"bundled":114},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-226-tuxcare.els8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-226-tuxcare.els8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-extra-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-source-5.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-226-tuxcare.els8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-226-tuxcare.els8-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-226-tuxcare.els8-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-226.246"}]}],"bundled":95},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-281-tuxcare.els51","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-281-tuxcare.els51","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-281-tuxcare.els51","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-281-tuxcare.els51-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.4.0-281-tuxcare.els51-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-281.315"}]}],"bundled":68},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.12"},{"fixed":"5.4.297"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.241"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.190"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.149"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.103"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.43"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.15.11"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.16.0"},{"fixed":"6.16.2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.153-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.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.43-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.16.3-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.3-1~bpo13+1","6.16~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.244-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.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":331},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.153-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"],"bundled":465},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.153-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.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":138},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.105-1.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.105-1.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.10-10.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-86.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"Mageia:9","package":"mageia-repos","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9-4.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"Mageia:9","package":"meta-task","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9-4.mga9"}]}],"bundled":132},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-299.0.0.202.oe2203sp4"}]}],"bundled":35},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.119.oe2403"}]}],"bundled":99},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.132.oe2403sp1"}]}],"bundled":99},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-138.0.0.132.oe2403sp2"}]}],"bundled":94},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1.150600.12.32.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6_Update_16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.13.3.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"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.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1.150600.12.32.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.23.73.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.223.1"}]}],"bundled":79},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.223.1"}]}],"bundled":79},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.223.1"}]}],"bundled":79},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.223.1"}]}],"bundled":79},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_73","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.275.1"}]}],"bundled":183},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1.150500.6.59.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP5","package":"kernel-livepatch-SLE15-SP5_Update_31","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150500.11.3.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1.150500.6.59.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1.150500.6.59.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1.150500.6.59.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1.150500.6.59.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.55.124.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP3","package":"kernel-livepatch-SLE15-SP3_Update_62","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150300.7.3.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1.150300.18.132.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-preempt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.18-150300.59.221.1"}]}],"bundled":84},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP4","package":"kernel-livepatch-SLE15-SP4_Update_45","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150400.9.3.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Proxy LTS 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Proxy LTS 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Proxy LTS 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Proxy LTS 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Server LTS 4.3","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Server LTS 4.3","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1.150400.24.92.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Server LTS 4.3","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Server LTS 4.3","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"source":"osv","ecosystem":"SUSE:Manager Server LTS 4.3","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.24.179.1"}]}],"bundled":326},{"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.52.1"}]}],"bundled":445},{"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.52.1"}]}],"bundled":445},{"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.52.1"}]}],"bundled":445},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.52.1"}]}],"bundled":445},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.52.1"}]}],"bundled":445},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.8.52.1"}]}],"bundled":445},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1.21.12"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1.21.12"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-35.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-37.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-37.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-37.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-37.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.133.1"}]}],"bundled":324},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.3","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.133.1"}]}],"bundled":324},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.133.1"}]}],"bundled":324},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.4","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150400.15.133.1"}]}],"bundled":324},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP6","package":"kernel-livepatch-SLE15-SP6-RT_Update_16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150600.1.3.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.55.1"}]}],"bundled":346},{"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.55.1"}]}],"bundled":346},{"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.55.1"}]}],"bundled":346},{"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.55.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.55.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-rt_debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.55.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.55.1"}]}],"bundled":346},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150600.10.55.1"}]}],"bundled":346},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.109.1"}]}],"bundled":378},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.5","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.21-150500.13.109.1"}]}],"bundled":378},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1.150700.17.15.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.22.1"}]}],"bundled":462},{"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.18.1"}]}],"bundled":462},{"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.18.1"}]}],"bundled":462},{"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.18.1"}]}],"bundled":462},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.1"}]}],"bundled":461},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.22.1"}]}],"bundled":461},{"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.22.1"}]}],"bundled":461},{"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.22.1"}]}],"bundled":461},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-ec2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-trace","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE","package":"kernel-xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.101-108.192.1"}]}],"bundled":20},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206","3.13.0-157.207","3.13.0-158.208","3.13.0-160.210","3.13.0-161.211","3.13.0-162.212","3.13.0-163.213","3.13.0-164.214","3.13.0-165.215","3.13.0-166.216","3.13.0-167.217","3.13.0-168.218","3.13.0-169.219","3.13.0-170.220","3.13.0-171.222","3.13.0-172.223","3.13.0-173.224","3.13.0-174.225","3.13.0-175.226","3.13.0-176.227","3.13.0-180.231","3.13.0-181.232","3.13.0-182.233","3.13.0-183.234","3.13.0-184.235","3.13.0-185.236","3.13.0-186.237","3.13.0-187.238","3.13.0-188.239","3.13.0-189.240","3.13.0-190.241","3.13.0-191.242","3.13.0-192.243","3.13.0-193.244","3.13.0-194.245","3.13.0-195.246","3.13.0-196.247","3.13.0-197.248","3.13.0-198.249","3.13.0-199.250","3.13.0-200.251","3.13.0-201.252","3.13.0-202.253","3.13.0-203.254","3.13.0-204.255","3.13.0-205.256","3.13.0-206.257","3.13.0-207.258","3.13.0-208.259","3.13.0-209.260","3.13.0-210.261","3.13.0-211.262","3.13.0-212.263","3.13.0-214.265","3.13.0-215.266","3.13.0-217.268","3.13.0-218.269","3.13.0-219.270","3.13.0-220.271"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1017.17","4.4.0-1019.19","4.4.0-1022.22","4.4.0-1023.23","4.4.0-1024.25","4.4.0-1025.26","4.4.0-1027.30","4.4.0-1028.31","4.4.0-1029.32","4.4.0-1031.34","4.4.0-1032.35","4.4.0-1034.37","4.4.0-1036.39","4.4.0-1037.40","4.4.0-1038.41","4.4.0-1039.42","4.4.0-1040.43","4.4.0-1042.45","4.4.0-1044.47","4.4.0-1045.48","4.4.0-1046.50","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1052.56","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1056.60","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1060.64","4.4.0-1061.65","4.4.0-1062.66","4.4.0-1064.68","4.4.0-1065.69","4.4.0-1066.70","4.4.0-1067.71","4.4.0-1073.77","4.4.0-1074.78","4.4.0-1075.79","4.4.0-1076.80","4.4.0-1077.81","4.4.0-1078.82","4.4.0-1081.85","4.4.0-1082.86","4.4.0-1083.87","4.4.0-1085.89","4.4.0-1086.90","4.4.0-1087.91","4.4.0-1088.92","4.4.0-1090.94","4.4.0-1091.95","4.4.0-1092.96","4.4.0-1093.97","4.4.0-1094.99","4.4.0-1095.100","4.4.0-1096.101","4.4.0-1097.102","4.4.0-1098.103","4.4.0-1099.104","4.4.0-1101.106","4.4.0-1102.107","4.4.0-1103.108","4.4.0-1104.109","4.4.0-1107.113","4.4.0-1109.115","4.4.0-1110.116","4.4.0-1111.117","4.4.0-1112.118","4.4.0-1113.119","4.4.0-1114.120","4.4.0-1115.121","4.4.0-1116.122","4.4.0-1117.123","4.4.0-1118.124","4.4.0-1119.125","4.4.0-1120.126","4.4.0-1121.127","4.4.0-1122.128","4.4.0-1123.129","4.4.0-1124.130","4.4.0-1125.131","4.4.0-1127.133","4.4.0-1128.134","4.4.0-1129.135","4.4.0-1130.136","4.4.0-1131.137","4.4.0-1133.139","4.4.0-1134.140","4.4.0-1135.141","4.4.0-1136.142","4.4.0-1137.143","4.4.0-1138.144","4.4.0-1139.145","4.4.0-1140.146","4.4.0-1141.147","4.4.0-1142.148","4.4.0-1143.149","4.4.0-1144.150","4.4.0-1145.151","4.4.0-1146.152","4.4.0-1147.153","4.4.0-1148.154","4.4.0-1149.155","4.4.0-1150.156","4.4.0-1151.157","4.4.0-1152.158","4.4.0-1153.159","4.4.0-1154.160","4.4.0-1155.161","4.4.0-1156.162","4.4.0-1157.163","4.4.0-1158.164","4.4.0-1159.165","4.4.0-1160.166","4.4.0-1161.167","4.4.0-1162.168"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1","4.15.0-1184.199~14.04.1","4.15.0-1185.200~14.04.1","4.15.0-1186.201~14.04.1","4.15.0-1187.202~14.04.1","4.15.0-1188.203~14.04.1","4.15.0-1189.204~14.04.1","4.15.0-1190.205~14.04.1","4.15.0-1191.206~14.04.1","4.15.0-1192.207~14.04.1","4.15.0-1193.208~14.04.1","4.15.0-1194.209~14.04.1","4.15.0-1195.210~14.04.1","4.15.0-1196.211~14.04.1","4.15.0-1197.212~14.04.1","4.15.0-1199.214~14.04.1","4.15.0-1200.215~14.04.1","4.15.0-1201.216~14.04.1","4.15.0-1202.217~14.04.1","4.15.0-1205.220~14.04.1","4.15.0-1206.221~14.04.1","4.15.0-1207.222~14.04.1","4.15.0-1208.223~14.04.1","4.15.0-1209.224~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1","4.4.0-119.143~14.04.1","4.4.0-121.145~14.04.1","4.4.0-124.148~14.04.1","4.4.0-127.153~14.04.1","4.4.0-128.154~14.04.1","4.4.0-130.156~14.04.1","4.4.0-131.157~14.04.1","4.4.0-133.159~14.04.1","4.4.0-134.160~14.04.1","4.4.0-135.161~14.04.1","4.4.0-137.163~14.04.1","4.4.0-138.164~14.04.1","4.4.0-139.165~14.04.1","4.4.0-140.166~14.04.1","4.4.0-141.167~14.04.1","4.4.0-142.168~14.04.1","4.4.0-143.169~14.04.2","4.4.0-144.170~14.04.1","4.4.0-146.172~14.04.1","4.4.0-148.174~14.04.1","4.4.0-150.176~14.04.1","4.4.0-151.178~14.04.1","4.4.0-154.181~14.04.1","4.4.0-157.185~14.04.1","4.4.0-159.187~14.04.1","4.4.0-161.189~14.04.1","4.4.0-164.192~14.04.1","4.4.0-165.193~14.04.1","4.4.0-166.195~14.04.1","4.4.0-168.197~14.04.1","4.4.0-169.198~14.04.1","4.4.0-170.199~14.04.1","4.4.0-171.200~14.04.1","4.4.0-173.203~14.04.1","4.4.0-174.204~14.04.1","4.4.0-176.206~14.04.1","4.4.0-177.207~14.04.1","4.4.0-178.208~14.04.1","4.4.0-179.209~14.04.1","4.4.0-184.214~14.04.1","4.4.0-185.215~14.04.1","4.4.0-186.216~14.04.1","4.4.0-187.217~14.04.1","4.4.0-189.219~14.04.1","4.4.0-190.220~14.04.1","4.4.0-193.224~14.04.1","4.4.0-194.226~14.04.1","4.4.0-197.229~14.04.1","4.4.0-198.230~14.04.1","4.4.0-200.232~14.04.1","4.4.0-201.233~14.04.1","4.4.0-203.235~14.04.1","4.4.0-204.236~14.04.1","4.4.0-206.238~14.04.1","4.4.0-208.240~14.04.1","4.4.0-209.241~14.04.1","4.4.0-210.242~14.04.1","4.4.0-211.243~14.04.1","4.4.0-212.244~14.04.1","4.4.0-213.245~14.04.1","4.4.0-214.246~14.04.1","4.4.0-215.247~14.04.1","4.4.0-218.251~14.04.1","4.4.0-219.252~14.04.1","4.4.0-221.254~14.04.1","4.4.0-222.255~14.04.1","4.4.0-223.256~14.04.1","4.4.0-224.257~14.04.1","4.4.0-227.261~14.04.1","4.4.0-229.263~14.04.1","4.4.0-230.264~14.04.1","4.4.0-231.265~14.04.1","4.4.0-233.267~14.04.1","4.4.0-234.268~14.04.1","4.4.0-235.269~14.04.1","4.4.0-236.270~14.04.1","4.4.0-237.271~14.04.1","4.4.0-239.273~14.04.1","4.4.0-240.274~14.04.1","4.4.0-241.275~14.04.1","4.4.0-242.276~14.04.1","4.4.0-243.277~14.04.1","4.4.0-244.278~14.04.1","4.4.0-245.279~14.04.1","4.4.0-246.280~14.04.1","4.4.0-248.282~14.04.1","4.4.0-250.284~14.04.1","4.4.0-251.285~14.04.1","4.4.0-252.286~14.04.1","4.4.0-253.287~14.04.1","4.4.0-254.288~14.04.1","4.4.0-256.290~14.04.1","4.4.0-257.291~14.04.1","4.4.0-258.292~14.04.2","4.4.0-259.293~14.04.1","4.4.0-260.294~14.04.1","4.4.0-261.295~14.04.1","4.4.0-262.296~14.04.1","4.4.0-263.297~14.04.1","4.4.0-264.298~14.04.1","4.4.0-266.300~14.04.1","4.4.0-267.301~14.04.1","4.4.0-268.302~14.04.1","4.4.0-269.303~14.04.1","4.4.0-270.304~14.04.1","4.4.0-271.305~14.04.1","4.4.0-272.306~14.04.1","4.4.0-273.307~14.04.1","4.4.0-274.308~14.04.1","4.4.0-276.310~14.04.1","4.4.0-277.311~14.04.1","4.4.0-278.312~14.04.1","4.4.0-279.313~14.04.1","4.4.0-280.314~14.04.1","4.4.0-281.315~14.04.1","4.4.0-283.317~14.04.1","4.4.0-284.318~14.04.1","4.4.0-287.321~14.04.1","4.4.0-288.322~14.04.1","4.4.0-289.323~14.04.1","4.4.0-290.324~14.04.1","4.4.0-291.325~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140","4.4.0-119.143","4.4.0-121.145","4.4.0-122.146","4.4.0-124.148","4.4.0-127.153","4.4.0-128.154","4.4.0-130.156","4.4.0-131.157","4.4.0-133.159","4.4.0-134.160","4.4.0-135.161","4.4.0-137.163","4.4.0-138.164","4.4.0-139.165","4.4.0-140.166","4.4.0-141.167","4.4.0-142.168","4.4.0-143.169","4.4.0-145.171","4.4.0-146.172","4.4.0-148.174","4.4.0-150.176","4.4.0-151.178","4.4.0-154.181","4.4.0-157.185","4.4.0-159.187","4.4.0-161.189","4.4.0-164.192","4.4.0-165.193","4.4.0-166.195","4.4.0-168.197","4.4.0-169.198","4.4.0-170.199","4.4.0-171.200","4.4.0-173.203","4.4.0-174.204","4.4.0-176.206","4.4.0-177.207","4.4.0-178.208","4.4.0-179.209","4.4.0-184.214","4.4.0-185.215","4.4.0-186.216","4.4.0-187.217","4.4.0-189.219","4.4.0-190.220","4.4.0-193.224","4.4.0-194.226","4.4.0-197.229","4.4.0-198.230","4.4.0-200.232","4.4.0-201.233","4.4.0-203.235","4.4.0-204.236","4.4.0-206.238","4.4.0-208.240","4.4.0-209.241","4.4.0-210.242","4.4.0-211.243","4.4.0-212.244","4.4.0-213.245","4.4.0-214.246","4.4.0-216.249","4.4.0-217.250","4.4.0-218.251","4.4.0-219.252","4.4.0-221.254","4.4.0-222.255","4.4.0-223.256","4.4.0-224.257","4.4.0-227.261","4.4.0-229.263","4.4.0-230.264","4.4.0-231.265","4.4.0-233.267","4.4.0-234.268","4.4.0-235.269","4.4.0-236.270","4.4.0-237.271","4.4.0-239.273","4.4.0-240.274","4.4.0-241.275","4.4.0-242.276","4.4.0-243.277","4.4.0-244.278","4.4.0-245.279","4.4.0-246.280","4.4.0-248.282","4.4.0-250.284","4.4.0-251.285","4.4.0-252.286","4.4.0-253.287","4.4.0-254.288","4.4.0-256.290","4.4.0-257.291","4.4.0-258.292","4.4.0-259.293","4.4.0-260.294","4.4.0-261.295","4.4.0-262.296","4.4.0-263.297","4.4.0-264.298","4.4.0-266.300","4.4.0-267.301","4.4.0-268.302","4.4.0-269.303","4.4.0-270.304","4.4.0-271.305","4.4.0-272.306","4.4.0-273.307","4.4.0-274.308","4.4.0-276.310","4.4.0-277.311","4.4.0-278.312","4.4.0-279.313","4.4.0-280.314","4.4.0-281.315","4.4.0-283.317","4.4.0-284.318","4.4.0-287.321","4.4.0-288.322","4.4.0-289.323","4.4.0-290.324","4.4.0-291.325"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61","4.4.0-1054.63","4.4.0-1055.64","4.4.0-1057.66","4.4.0-1060.69","4.4.0-1061.70","4.4.0-1062.71","4.4.0-1063.72","4.4.0-1065.75","4.4.0-1066.76","4.4.0-1067.77","4.4.0-1069.79","4.4.0-1070.80","4.4.0-1072.82","4.4.0-1073.83","4.4.0-1074.84","4.4.0-1075.85","4.4.0-1077.87","4.4.0-1079.89","4.4.0-1081.91","4.4.0-1083.93","4.4.0-1084.94","4.4.0-1085.96","4.4.0-1087.98","4.4.0-1088.99","4.4.0-1090.101","4.4.0-1092.103","4.4.0-1094.105","4.4.0-1095.106","4.4.0-1096.107","4.4.0-1098.109","4.4.0-1099.110","4.4.0-1100.111","4.4.0-1101.112","4.4.0-1102.113","4.4.0-1104.115","4.4.0-1105.116","4.4.0-1106.117","4.4.0-1107.118","4.4.0-1109.120","4.4.0-1110.121","4.4.0-1111.123","4.4.0-1112.124","4.4.0-1113.126","4.4.0-1114.127","4.4.0-1117.131","4.4.0-1118.132","4.4.0-1119.133","4.4.0-1121.135","4.4.0-1122.136","4.4.0-1123.137","4.4.0-1124.138","4.4.0-1126.140","4.4.0-1127.141","4.4.0-1128.142","4.4.0-1129.143","4.4.0-1130.144","4.4.0-1131.145","4.4.0-1132.146","4.4.0-1133.147","4.4.0-1134.148","4.4.0-1135.149","4.4.0-1137.151","4.4.0-1138.152","4.4.0-1139.153","4.4.0-1140.154","4.4.0-1143.158","4.4.0-1145.160","4.4.0-1146.161","4.4.0-1147.162","4.4.0-1148.163","4.4.0-1150.165","4.4.0-1151.166","4.4.0-1152.167","4.4.0-1153.168","4.4.0-1154.169","4.4.0-1155.170","4.4.0-1156.171","4.4.0-1157.172","4.4.0-1158.173","4.4.0-1159.174","4.4.0-1160.175","4.4.0-1161.176","4.4.0-1162.177","4.4.0-1163.178","4.4.0-1164.179","4.4.0-1165.180","4.4.0-1166.181","4.4.0-1167.182","4.4.0-1168.183","4.4.0-1169.184","4.4.0-1171.186","4.4.0-1172.187","4.4.0-1173.188","4.4.0-1174.189","4.4.0-1175.190","4.4.0-1176.191","4.4.0-1177.192","4.4.0-1178.193","4.4.0-1179.194","4.4.0-1180.195","4.4.0-1181.196","4.4.0-1182.197","4.4.0-1183.198","4.4.0-1184.199","4.4.0-1185.200","4.4.0-1186.201","4.4.0-1187.202","4.4.0-1188.203","4.4.0-1189.204","4.4.0-1190.205","4.4.0-1191.206","4.4.0-1192.207","4.4.0-1193.208","4.4.0-1194.209","4.4.0-1195.210","4.4.0-1196.211","4.4.0-1197.212","4.4.0-1198.213","4.4.0-1199.214","4.4.0-1200.215"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1","4.15.0-1176.189~16.04.1","4.15.0-1177.190~16.04.1","4.15.0-1178.191~16.04.1","4.15.0-1179.192~16.04.1","4.15.0-1180.193~16.04.1","4.15.0-1181.194~16.04.1","4.15.0-1182.195~16.04.1","4.15.0-1183.196~16.04.1","4.15.0-1184.197~16.04.1","4.15.0-1185.198~16.04.1","4.15.0-1186.199~16.04.1","4.15.0-1187.200~16.04.1","4.15.0-1188.201~16.04.1","4.15.0-1189.202~16.04.1","4.15.0-1190.203~16.04.1","4.15.0-1191.204~16.04.1","4.15.0-1192.205~16.04.1","4.15.0-1194.207~16.04.1","4.15.0-1195.208~16.04.1","4.15.0-1196.209~16.04.1","4.15.0-1197.210~16.04.1","4.15.0-1198.211~16.04.1","4.15.0-1199.212~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1","4.15.0-1184.199~16.04.1","4.15.0-1185.200~16.04.1","4.15.0-1186.201~16.04.1","4.15.0-1187.202~16.04.1","4.15.0-1188.203~16.04.1","4.15.0-1189.204~16.04.1","4.15.0-1190.205~16.04.1","4.15.0-1191.206~16.04.1","4.15.0-1192.207~16.04.1","4.15.0-1193.208~16.04.1","4.15.0-1194.209~16.04.1","4.15.0-1195.210~16.04.1","4.15.0-1196.211~16.04.1","4.15.0-1197.212~16.04.1","4.15.0-1200.215~16.04.1","4.15.0-1204.219~16.04.1","4.15.0-1205.220~16.04.1","4.15.0-1206.221~16.04.1","4.15.0-1208.223~16.04.1","4.15.0-1209.224~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1","4.15.0-1169.186~16.04.1","4.15.0-1170.187~16.04.1","4.15.0-1171.188~16.04.1","4.15.0-1172.189~16.04.1","4.15.0-1173.190~16.04.1","4.15.0-1174.191~16.04.1","4.15.0-1175.192~16.04.1","4.15.0-1176.193~16.04.1","4.15.0-1177.194~16.04.1","4.15.0-1178.195~16.04.1","4.15.0-1179.196~16.04.1","4.15.0-1180.197~16.04.1","4.15.0-1181.198~16.04.1","4.15.0-1182.199~16.04.1","4.15.0-1183.200~16.04.2","4.15.0-1184.201~16.04.1","4.15.0-1185.202~16.04.1","4.15.0-1187.204~16.04.1","4.15.0-1188.205~16.04.1","4.15.0-1189.206~16.04.1","4.15.0-1190.207~16.04.1","4.15.0-1191.208~16.04.1","4.15.0-1192.209~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1","4.15.0-232.244~16.04.1","4.15.0-233.245~16.04.1","4.15.0-234.246~16.04.1","4.15.0-235.247~16.04.1","4.15.0-236.248~16.04.1","4.15.0-237.249~16.04.1","4.15.0-238.250~16.04.1","4.15.0-239.251~16.04.1","4.15.0-240.252~16.04.1","4.15.0-241.253~16.04.1","4.15.0-242.254~16.04.1","4.15.0-243.255~16.04.1","4.15.0-245.257~16.04.1","4.15.0-246.258~16.04.1","4.15.0-247.259~16.04.1","4.15.0-248.260~16.04.1","4.15.0-249.261~16.04.1","4.15.0-250.262~16.04.1","4.15.0-253.265~16.04.1","4.15.0-254.266~16.04.1","4.15.0-257.269~16.04.1","4.15.0-260.272~16.04.2","4.15.0-261.273~16.04.1","4.15.0-262.274~16.04.1"]},{"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:Pro:16.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1020.25","4.4.0-1021.26","4.4.0-1023.28","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1029.34","4.4.0-1031.37","4.4.0-1032.38","4.4.0-1033.39","4.4.0-1035.41","4.4.0-1036.42","4.4.0-1037.43","4.4.0-1038.44","4.4.0-1039.45","4.4.0-1040.46","4.4.0-1041.47","4.4.0-1043.49","4.4.0-1044.50","4.4.0-1046.52","4.4.0-1047.53","4.4.0-1048.55","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1056.63","4.4.0-1058.65","4.4.0-1059.66","4.4.0-1060.67","4.4.0-1062.69","4.4.0-1063.70","4.4.0-1064.71","4.4.0-1065.72","4.4.0-1066.73","4.4.0-1068.75","4.4.0-1069.76","4.4.0-1070.77","4.4.0-1071.78","4.4.0-1075.82","4.4.0-1076.83","4.4.0-1077.84","4.4.0-1078.85","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1082.91","4.4.0-1084.93","4.4.0-1085.94","4.4.0-1087.96","4.4.0-1088.97","4.4.0-1089.98","4.4.0-1090.99","4.4.0-1091.100","4.4.0-1092.101","4.4.0-1093.102","4.4.0-1094.103","4.4.0-1095.104","4.4.0-1096.105","4.4.0-1097.106","4.4.0-1098.107","4.4.0-1099.108","4.4.0-1100.109","4.4.0-1102.111","4.4.0-1103.112","4.4.0-1104.113","4.4.0-1105.114","4.4.0-1108.118","4.4.0-1110.120","4.4.0-1111.121","4.4.0-1112.122","4.4.0-1113.123","4.4.0-1114.124","4.4.0-1115.125","4.4.0-1116.126","4.4.0-1117.127","4.4.0-1118.128","4.4.0-1119.129","4.4.0-1120.130","4.4.0-1121.131","4.4.0-1122.132","4.4.0-1123.133","4.4.0-1124.134","4.4.0-1125.135","4.4.0-1126.136","4.4.0-1128.138","4.4.0-1129.139","4.4.0-1130.140","4.4.0-1131.141","4.4.0-1132.142","4.4.0-1134.144","4.4.0-1135.145","4.4.0-1136.146","4.4.0-1137.147","4.4.0-1138.148","4.4.0-1139.149","4.4.0-1140.151","4.4.0-1141.152","4.4.0-1142.153","4.4.0-1143.154","4.4.0-1144.155","4.4.0-1145.156","4.4.0-1146.157","4.4.0-1147.158","4.4.0-1148.159","4.4.0-1149.160","4.4.0-1150.161","4.4.0-1151.162","4.4.0-1152.163","4.4.0-1153.164","4.4.0-1154.165","4.4.0-1155.166","4.4.0-1156.167","4.4.0-1157.168","4.4.0-1158.169","4.4.0-1159.170","4.4.0-1160.171","4.4.0-1161.172","4.4.0-1162.173","4.4.0-1163.174"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1138.149~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.153~16.04.1","4.15.0-1143.154~16.04.1","4.15.0-1144.155~16.04.1","4.15.0-1145.156~16.04.1","4.15.0-1148.159~16.04.1","4.15.0-1149.160~16.04.1","4.15.0-1150.161~16.04.1","4.15.0-1151.162~16.04.1","4.15.0-1153.164~16.04.1","4.15.0-1154.165~16.04.1","4.15.0-1156.167~16.04.1","4.15.0-1158.169~16.04.1","4.15.0-1160.171~16.04.1","4.15.0-1161.172~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1008.10","4.4.0-1010.13","4.4.0-1011.14","4.4.0-1012.16","4.4.0-1013.17","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1021.26","4.4.0-1022.27","4.4.0-1023.28","4.4.0-1025.30","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1028.33","4.4.0-1029.34","4.4.0-1031.36","4.4.0-1032.37","4.4.0-1033.38","4.4.0-1034.39","4.4.0-1041.46","4.4.0-1042.47","4.4.0-1043.48","4.4.0-1044.49","4.4.0-1045.50","4.4.0-1046.51","4.4.0-1048.53","4.4.0-1049.55","4.4.0-1051.57","4.4.0-1052.58","4.4.0-1054.60","4.4.0-1055.61","4.4.0-1056.62","4.4.0-1057.63","4.4.0-1058.64","4.4.0-1060.66","4.4.0-1061.67","4.4.0-1062.68","4.4.0-1063.69","4.4.0-1064.70","4.4.0-1065.71","4.4.0-1066.72","4.4.0-1067.73","4.4.0-1068.74","4.4.0-1069.75","4.4.0-1071.77","4.4.0-1072.78","4.4.0-1073.79","4.4.0-1074.80","4.4.0-1077.84","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1081.88","4.4.0-1082.89","4.4.0-1083.90","4.4.0-1084.91","4.4.0-1085.92","4.4.0-1086.93","4.4.0-1088.95","4.4.0-1089.96","4.4.0-1090.97","4.4.0-1091.98","4.4.0-1092.99","4.4.0-1093.100","4.4.0-1094.101","4.4.0-1095.102","4.4.0-1097.104","4.4.0-1099.106","4.4.0-1100.107","4.4.0-1101.108","4.4.0-1102.109","4.4.0-1103.110","4.4.0-1104.111","4.4.0-1105.112","4.4.0-1106.113","4.4.0-1107.114","4.4.0-1108.115","4.4.0-1109.116","4.4.0-1110.117","4.4.0-1111.118","4.4.0-1112.119","4.4.0-1113.120","4.4.0-1114.121","4.4.0-1115.122","4.4.0-1116.123","4.4.0-1117.124","4.4.0-1119.126","4.4.0-1120.127","4.4.0-1121.128","4.4.0-1122.129","4.4.0-1123.130","4.4.0-1124.131","4.4.0-1125.132","4.4.0-1126.133","4.4.0-1127.134","4.4.0-1128.135","4.4.0-1129.136","4.4.0-1130.137","4.4.0-1131.138"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.1","4.4.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243","4.15.0-232.244","4.15.0-233.245","4.15.0-234.246","4.15.0-235.247","4.15.0-236.248","4.15.0-237.249","4.15.0-238.250","4.15.0-239.251","4.15.0-240.252","4.15.0-241.253","4.15.0-242.254","4.15.0-243.255","4.15.0-245.257","4.15.0-246.258","4.15.0-247.259","4.15.0-248.260","4.15.0-249.261","4.15.0-250.262","4.15.0-251.263","4.15.0-253.265","4.15.0-254.266","4.15.0-257.269","4.15.0-260.272","4.15.0-261.273","4.15.0-262.274"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","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-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188","4.15.0-1176.189","4.15.0-1177.190","4.15.0-1178.191","4.15.0-1179.192","4.15.0-1180.193","4.15.0-1181.194","4.15.0-1182.195","4.15.0-1183.196","4.15.0-1184.197","4.15.0-1185.198","4.15.0-1186.199","4.15.0-1187.200","4.15.0-1188.201","4.15.0-1189.202","4.15.0-1190.203","4.15.0-1191.204","4.15.0-1192.205","4.15.0-1194.207","4.15.0-1195.208","4.15.0-1196.209","4.15.0-1197.210","4.15.0-1198.211","4.15.0-1199.212"]},{"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:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~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-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1","5.4.0-1135.145~18.04.1","5.4.0-1136.146~18.04.1","5.4.0-1137.147~18.04.1","5.4.0-1139.149~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1147.157~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1153.163~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1156.166~18.04.1","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1160.170~18.04.1","5.4.0-1161.172~18.04.1","5.4.0-1162.173~18.04.1","5.4.0-1163.174~18.04.1","5.4.0-1165.176~18.04.1","5.4.0-1167.178~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198","4.15.0-1184.199","4.15.0-1185.200","4.15.0-1186.201","4.15.0-1187.202","4.15.0-1188.203","4.15.0-1189.204","4.15.0-1190.205","4.15.0-1191.206","4.15.0-1192.207","4.15.0-1193.208","4.15.0-1194.209","4.15.0-1195.210","4.15.0-1196.211","4.15.0-1197.212","4.15.0-1199.214","4.15.0-1200.215","4.15.0-1201.216","4.15.0-1202.217","4.15.0-1204.219","4.15.0-1205.220","4.15.0-1206.221","4.15.0-1207.222","4.15.0-1208.223","4.15.0-1209.224"]},{"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:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~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-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.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-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1","5.4.0-1140.147~18.04.1","5.4.0-1142.149~18.04.1","5.4.0-1143.150~18.04.1","5.4.0-1145.152~18.04.1","5.4.0-1147.154~18.04.1","5.4.0-1148.155~18.04.1","5.4.0-1149.156~18.04.1","5.4.0-1150.157~18.04.1","5.4.0-1151.158~18.04.1","5.4.0-1152.159~18.04.1","5.4.0-1153.160~18.04.1","5.4.0-1154.161~18.04.1","5.4.0-1156.163~18.04.1","5.4.0-1157.164~18.04.1","5.4.0-1161.167~18.04.1","5.4.0-1162.168~18.04.1","5.4.0-1163.169~18.04.1","5.4.0-1164.170~18.04.1","5.4.0-1166.172~18.04.1","5.4.0-1167.173~18.04.1","5.4.0-1168.174~18.04.1","5.4.0-1169.175~18.04.1","5.4.0-1170.176~18.04.1","5.4.0-1171.177~18.04.1","5.4.0-1172.178~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185","4.15.0-1169.186","4.15.0-1170.187","4.15.0-1171.188","4.15.0-1172.189","4.15.0-1173.190","4.15.0-1174.191","4.15.0-1175.192","4.15.0-1176.193","4.15.0-1177.194","4.15.0-1178.195","4.15.0-1179.196","4.15.0-1180.197","4.15.0-1181.198","4.15.0-1182.199","4.15.0-1183.200","4.15.0-1184.201","4.15.0-1185.202","4.15.0-1186.203","4.15.0-1187.204","4.15.0-1188.205","4.15.0-1189.206","4.15.0-1190.207","4.15.0-1191.208","4.15.0-1192.209"]},{"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:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~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-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1139.148~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.150~18.04.1","5.4.0-1142.151~18.04.1","5.4.0-1143.152~18.04.1","5.4.0-1145.154~18.04.1","5.4.0-1147.156~18.04.1","5.4.0-1148.157~18.04.1","5.4.0-1149.158~18.04.1","5.4.0-1150.159~18.04.1","5.4.0-1151.160~18.04.1","5.4.0-1152.161~18.04.1","5.4.0-1153.162~18.04.1","5.4.0-1154.163~18.04.1","5.4.0-1155.164~18.04.1","5.4.0-1156.165~18.04.1","5.4.0-1157.166~18.04.1","5.4.0-1159.168~18.04.1","5.4.0-1160.169~18.04.1","5.4.0-1161.170~18.04.1","5.4.0-1162.171~18.04.1","5.4.0-1163.172~18.04.1","5.4.0-1164.173~18.04.1","5.4.0-1165.174~18.04.1","5.4.0-1166.175~18.04.1","5.4.0-1167.176~18.04.1","5.4.0-1168.178~18.04.1","5.4.0-1169.179~18.04.1","5.4.0-1170.180~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:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1","5.4.0-200.220~18.04.1","5.4.0-202.222~18.04.1","5.4.0-204.224~18.04.1","5.4.0-205.225~18.04.1","5.4.0-208.228~18.04.1","5.4.0-211.231~18.04.1","5.4.0-212.232~18.04.1","5.4.0-214.234~18.04.1","5.4.0-215.235~18.04.1","5.4.0-216.236~18.04.1","5.4.0-218.238~18.04.1","5.4.0-219.239~18.04.1","5.4.0-220.240~18.04.1","5.4.0-221.241~18.04.1","5.4.0-222.242~18.04.1","5.4.0-223.243~18.04.1","5.4.0-224.244~18.04.1","5.4.0-225.245~18.04.1","5.4.0-227.247~18.04.1","5.4.0-228.248~18.04.1","5.4.0-229.249~18.04.1","5.4.0-231.251~18.04.1","5.4.0-233.253~18.04.1","5.4.0-234.254~18.04.1","5.4.0-238.258~18.04.1","5.4.0-241.261~18.04.1","5.4.0-242.262~18.04.1","5.4.0-244.264~18.04.1","5.4.0-245.265~18.04.1"]},{"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:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1","5.4.0-1082.87~18.04.1","5.4.0-1083.88~18.04.1","5.4.0-1084.89~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1092.97~18.04.1","5.4.0-1093.98~18.04.1","5.4.0-1094.99~18.04.1","5.4.0-1095.100~18.04.1","5.4.0-1096.101~18.04.1","5.4.0-1097.102~18.04.1","5.4.0-1098.103~18.04.1","5.4.0-1099.104~18.04.1","5.4.0-1100.105~18.04.1","5.4.0-1102.107~18.04.1","5.4.0-1103.108~18.04.1","5.4.0-1104.109~18.04.1","5.4.0-1105.110~18.04.1","5.4.0-1107.112~18.04.1","5.4.0-1108.113~18.04.1","5.4.0-1109.114~18.04.1","5.4.0-1111.116~18.04.1","5.4.0-1112.117~18.04.1","5.4.0-1113.118~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","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-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163","4.15.0-1159.164","4.15.0-1160.165","4.15.0-1161.166","4.15.0-1162.167","4.15.0-1163.168","4.15.0-1164.169","4.15.0-1165.170","4.15.0-1166.171","4.15.0-1167.172","4.15.0-1168.173","4.15.0-1169.174","4.15.0-1170.175","4.15.0-1171.176","4.15.0-1172.177","4.15.0-1173.178","4.15.0-1174.179","4.15.0-1175.180","4.15.0-1176.181","4.15.0-1177.182","4.15.0-1178.183","4.15.0-1179.184","4.15.0-1180.185","4.15.0-1181.186"]},{"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:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.153","4.15.0-1143.154","4.15.0-1144.155","4.15.0-1145.156","4.15.0-1146.157","4.15.0-1147.158","4.15.0-1148.159","4.15.0-1149.160","4.15.0-1150.161","4.15.0-1151.162","4.15.0-1152.163","4.15.0-1153.164","4.15.0-1154.165","4.15.0-1155.166","4.15.0-1156.167","4.15.0-1158.169","4.15.0-1160.171","4.15.0-1161.172"]},{"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:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.151~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1143.153~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1155.165~18.04.1","5.4.0-1156.166~18.04.2","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1159.169~18.04.1","5.4.0-1161.171~18.04.1","5.4.0-1162.172~18.04.1","5.4.0-1163.173~18.04.1","5.4.0-1164.174~18.04.1","5.4.0-1165.175~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1","5.4.0-1119.131~18.04.1","5.4.0-1120.132~18.04.1","5.4.0-1121.133~18.04.1","5.4.0-1122.134~18.04.1","5.4.0-1129.142~18.04.1","5.4.0-1130.143~18.04.1","5.4.0-1131.144~18.04.1","5.4.0-1132.145~18.04.1","5.4.0-1133.146~18.04.1","5.4.0-1134.147~18.04.1","5.4.0-1135.148~18.04.1","5.4.0-1136.149~18.04.1","5.4.0-1137.150~18.04.1","5.4.0-1139.152~18.04.1","5.4.0-1140.153~18.04.1","5.4.0-1143.156~18.04.1","5.4.0-1144.157~18.04.1","5.4.0-1145.158~18.04.1","5.4.0-1146.159~18.04.1","5.4.0-1147.160~18.04.1","5.4.0-1148.161~18.04.1","5.4.0-1149.162~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4","4.15.0-2018.18","4.15.0-2021.21","4.15.0-2022.22","4.15.0-2024.24","4.15.0-2025.25","4.15.0-2026.26","4.15.0-2027.27","4.15.0-2030.31","4.15.0-2031.32","4.15.0-2033.34","4.15.0-2034.35","4.15.0-2035.37","4.15.0-2036.38","4.15.0-2037.39","4.15.0-2038.40","4.15.0-2039.41","4.15.0-2040.42","4.15.0-2041.43","4.15.0-2042.44","4.15.0-2044.46","4.15.0-2045.47","4.15.0-2048.50","4.15.0-2051.53","4.15.0-2052.54","4.15.0-2053.55","4.15.0-2054.56","4.15.0-2055.57","4.15.0-2056.58","4.15.0-2057.59","4.15.0-2059.61","4.15.0-2060.62","4.15.0-2061.63","4.15.0-2063.66","4.15.0-2064.67","4.15.0-2065.68","4.15.0-2066.69","4.15.0-2067.70","4.15.0-2069.72","4.15.0-2072.76","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2078.83","4.15.0-2079.84","4.15.0-2080.85","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2085.91","4.15.0-2087.93","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2103.109","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2107.113","4.15.0-2108.114","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123","4.15.0-2118.124","4.15.0-2119.125","4.15.0-2120.126","4.15.0-2121.127","4.15.0-2122.128","4.15.0-2123.129","4.15.0-2124.130","4.15.0-2125.131","4.15.0-2126.132","4.15.0-2127.133","4.15.0-2128.134","4.15.0-2129.135","4.15.0-2130.136","4.15.0-2132.138","4.15.0-2133.139","4.15.0-2134.140","4.15.0-2135.141","4.15.0-2136.142","4.15.0-2137.143"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-2006.7","4.15.0-2007.8","4.15.0-2008.9","4.15.0-2009.10","4.15.0-2012.14","4.15.0-2013.15","4.15.0-2015.17","4.15.0-2016.18","4.15.0-2017.20","4.15.0-2018.21","4.15.0-2020.23","4.15.0-2021.24","4.15.0-2022.25","4.15.0-2023.26","4.15.0-2024.27","4.15.0-2025.28","4.15.0-2026.29","4.15.0-2027.30","4.15.0-2030.33","4.15.0-2033.37","4.15.0-2034.38","4.15.0-2035.39","4.15.0-2036.40","4.15.0-2037.41","4.15.0-2038.42","4.15.0-2039.43","4.15.0-2041.45","4.15.0-2042.46","4.15.0-2043.47","4.15.0-2045.49","4.15.0-2046.50","4.15.0-2047.51","4.15.0-2048.52","4.15.0-2049.53","4.15.0-2050.54","4.15.0-2053.58","4.15.0-2056.62","4.15.0-2057.63","4.15.0-2059.65","4.15.0-2060.66","4.15.0-2062.68","4.15.0-2066.72","4.15.0-2067.73","4.15.0-2068.74","4.15.0-2070.76","4.15.0-2071.77","4.15.0-2072.78","4.15.0-2073.79","4.15.0-2074.80","4.15.0-2075.81","4.15.0-2076.82","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1027.32","4.15.0-1029.34","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1037.42","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1040.45","4.15.0-1041.46","4.15.0-1044.50","4.15.0-1045.52","4.15.0-1046.53","4.15.0-1048.55","4.15.0-1049.56","4.15.0-1050.58","4.15.0-1051.59","4.15.0-1052.60","4.15.0-1053.61","4.15.0-1054.62","4.15.0-1055.63","4.15.0-1056.64","4.15.0-1057.65","4.15.0-1058.66","4.15.0-1059.67","4.15.0-1060.68","4.15.0-1063.71","4.15.0-1066.75","4.15.0-1067.76","4.15.0-1068.77","4.15.0-1069.78","4.15.0-1070.79","4.15.0-1071.80","4.15.0-1072.81","4.15.0-1073.82","4.15.0-1075.84","4.15.0-1076.85","4.15.0-1078.87","4.15.0-1080.89","4.15.0-1081.90","4.15.0-1083.92","4.15.0-1084.93","4.15.0-1085.94","4.15.0-1087.96","4.15.0-1090.100","4.15.0-1093.104","4.15.0-1094.105","4.15.0-1096.107","4.15.0-1097.108","4.15.0-1098.109","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1103.114","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1109.120","4.15.0-1110.121","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.153","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1145.157","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1149.161","4.15.0-1150.162","4.15.0-1151.163","4.15.0-1152.164","4.15.0-1153.165","4.15.0-1154.166"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2013.14","4.15.0-2016.18","4.15.0-2017.19","4.15.0-2018.20","4.15.0-2019.21","4.15.0-2020.22","4.15.0-2021.23","4.15.0-2022.24","4.15.0-2024.26","4.15.0-2025.27","4.15.0-2026.28","4.15.0-2028.31","4.15.0-2029.32","4.15.0-2030.33","4.15.0-2031.34","4.15.0-2032.35","4.15.0-2034.37","4.15.0-2037.41","4.15.0-2040.45","4.15.0-2041.46","4.15.0-2043.48","4.15.0-2044.49","4.15.0-2045.50","4.15.0-2047.52","4.15.0-2050.55","4.15.0-2052.57","4.15.0-2054.59","4.15.0-2055.60","4.15.0-2056.61","4.15.0-2057.62","4.15.0-2058.63","4.15.0-2059.64","4.15.0-2060.65","4.15.0-2061.66","4.15.0-2062.67","4.15.0-2063.68","4.15.0-2064.69","4.15.0-2065.70","4.15.0-2066.71","4.15.0-2067.72","4.15.0-2068.73","4.15.0-2069.74","4.15.0-2070.75","4.15.0-2071.76","4.15.0-2072.77","4.15.0-2073.78","4.15.0-2074.79","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218","5.4.0-200.220","5.4.0-202.222","5.4.0-204.224","5.4.0-205.225","5.4.0-208.228","5.4.0-211.231","5.4.0-212.232","5.4.0-214.234","5.4.0-215.235","5.4.0-216.236","5.4.0-218.238","5.4.0-219.239","5.4.0-220.240","5.4.0-221.241","5.4.0-222.242","5.4.0-223.243","5.4.0-224.244","5.4.0-225.245","5.4.0-227.247","5.4.0-228.248","5.4.0-229.249","5.4.0-230.250","5.4.0-231.251","5.4.0-233.253","5.4.0-234.254","5.4.0-238.258","5.4.0-241.261","5.4.0-242.262","5.4.0-244.264","5.4.0-245.265"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1142.152","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1148.158","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1153.163","5.4.0-1154.164","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.172","5.4.0-1162.173","5.4.0-1163.174","5.4.0-1164.175","5.4.0-1165.176","5.4.0-1166.177","5.4.0-1167.178"]},{"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-1097.104~20.04.1"}]}],"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"]},{"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:Pro:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146","5.4.0-1140.147","5.4.0-1142.149","5.4.0-1143.150","5.4.0-1145.152","5.4.0-1147.154","5.4.0-1148.155","5.4.0-1149.156","5.4.0-1150.157","5.4.0-1151.158","5.4.0-1152.159","5.4.0-1153.160","5.4.0-1154.161","5.4.0-1156.163","5.4.0-1157.164","5.4.0-1160.166","5.4.0-1161.167","5.4.0-1162.168","5.4.0-1163.169","5.4.0-1164.170","5.4.0-1166.172","5.4.0-1167.173","5.4.0-1168.174","5.4.0-1169.175","5.4.0-1170.176","5.4.0-1171.177","5.4.0-1172.178"]},{"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-1102.111~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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1123.130","5.4.0-1125.132","5.4.0-1126.133"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1142.151","5.4.0-1143.152","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163","5.4.0-1155.164","5.4.0-1156.165","5.4.0-1157.166","5.4.0-1159.168","5.4.0-1160.169","5.4.0-1161.170","5.4.0-1162.171","5.4.0-1163.172","5.4.0-1164.173","5.4.0-1165.174","5.4.0-1166.175","5.4.0-1167.177","5.4.0-1168.178","5.4.0-1169.179","5.4.0-1170.180"]},{"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-1097.106~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"]},{"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-163.173~20.04.1"}]}],"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"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86","5.4.0-1082.87","5.4.0-1083.88","5.4.0-1084.89","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1088.93","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1092.97","5.4.0-1093.98","5.4.0-1094.99","5.4.0-1095.100","5.4.0-1096.101","5.4.0-1097.102","5.4.0-1098.103","5.4.0-1099.104","5.4.0-1100.105","5.4.0-1102.107","5.4.0-1103.108","5.4.0-1104.109","5.4.0-1105.110","5.4.0-1107.112","5.4.0-1108.113","5.4.0-1109.114","5.4.0-1111.116","5.4.0-1112.117","5.4.0-1113.118"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94~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"]},{"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-1092.98~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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","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-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","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-1041.42","5.4.0-1042.43","5.4.0-1043.44","5.4.0-1044.45","5.4.0-1045.46","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-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1071.74"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","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-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","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-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130","5.4.0-1123.131","5.4.0-1124.132","5.4.0-1125.133","5.4.0-1126.134","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1143.152","5.4.0-1144.153","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173~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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1049.49~20.04.1"}]}],"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"]},{"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:Pro:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1140.150","5.4.0-1141.151","5.4.0-1142.152","5.4.0-1143.153","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1154.164","5.4.0-1155.165","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.171","5.4.0-1162.172","5.4.0-1163.173","5.4.0-1164.174","5.4.0-1165.175"]},{"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-1094.100~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"]},{"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:Pro:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130","5.4.0-1119.131","5.4.0-1120.132","5.4.0-1121.133","5.4.0-1122.134","5.4.0-1129.142","5.4.0-1130.143","5.4.0-1131.144","5.4.0-1132.145","5.4.0-1133.146","5.4.0-1134.147","5.4.0-1135.148","5.4.0-1136.149","5.4.0-1137.150","5.4.0-1139.152","5.4.0-1140.153","5.4.0-1143.156","5.4.0-1144.157","5.4.0-1145.158","5.4.0-1146.159","5.4.0-1147.160","5.4.0-1148.161","5.4.0-1149.162"]},{"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-1092.96~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"]},{"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:Pro:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1058.62","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-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-1082.86","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1","5.4.0-1124.134+fips1","5.4.0-1125.135+fips1","5.4.0-1126.136+fips2","5.4.0-1127.137+fips1","5.4.0-1128.138+fips1","5.4.0-1129.139+fips1","5.4.0-1130.140+fips1","5.4.0-1131.141+fips1","5.4.0-1132.142+fips1","5.4.0-1133.143+fips1","5.4.0-1134.144+fips1","5.4.0-1135.145+fips1","5.4.0-1136.146+fips1","5.4.0-1137.147+fips1","5.4.0-1139.149+fips1","5.4.0-1140.151+fips1","5.4.0-1142.153+fips1","5.4.0-1144.155+fips1","5.4.0-1145.156+fips1","5.4.0-1146.156+fips1","5.4.0-1147.157+fips1","5.4.0-1148.158+fips1","5.4.0-1149.159+fips1","5.4.0-1150.160+fips1","5.4.0-1151.161+fips1","5.4.0-1152.162+fips1","5.4.0-1153.163+fips1","5.4.0-1154.164+fips1","5.4.0-1155.165+fips1","5.4.0-1156.166+fips1","5.4.0-1157.167+fips1","5.4.0-1158.168+fips1","5.4.0-1159.169+fips1","5.4.0-1160.170+fips1","5.4.0-1161.172+fips1","5.4.0-1163.174+fips1","5.4.0-1165.176+fips1","5.4.0-1166.177+fips1","5.4.0-1167.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1","5.4.0-1129.136+fips1","5.4.0-1130.137+fips1","5.4.0-1131.138+fips1","5.4.0-1132.139+fips1","5.4.0-1133.140+fips1","5.4.0-1134.141+fips1","5.4.0-1135.142+fips1","5.4.0-1136.143+fips1","5.4.0-1137.144+fips1","5.4.0-1138.145+fips1","5.4.0-1139.146+fips1","5.4.0-1140.147+fips1","5.4.0-1142.149+fips1","5.4.0-1143.150+fips1","5.4.0-1145.152+fips1","5.4.0-1147.154+fips1","5.4.0-1148.156+fips1","5.4.0-1149.157+fips1","5.4.0-1151.158+fips1","5.4.0-1152.159+fips1","5.4.0-1153.160+fips1","5.4.0-1154.161+fips1","5.4.0-1155.162+fips1","5.4.0-1157.164+fips1","5.4.0-1158.165+fips1","5.4.0-1160.166+fips1","5.4.0-1161.167+fips1","5.4.0-1162.168+fips1","5.4.0-1163.169+fips1","5.4.0-1164.170+fips1","5.4.0-1166.172+fips1","5.4.0-1167.173+fips1","5.4.0-1168.174+fips1","5.4.0-1170.176+fips1","5.4.0-1171.177+fips1","5.4.0-1172.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118","5.4.0-1109.119","5.4.0-1110.120","5.4.0-1111.121","5.4.0-1112.122","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1138.148","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1141.151"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1","5.4.0-1128.137+fips1","5.4.0-1129.138+fips1","5.4.0-1130.139+fips1","5.4.0-1131.140+fips1","5.4.0-1132.141+fips1","5.4.0-1133.142+fips1","5.4.0-1134.143+fips1","5.4.0-1135.144+fips1","5.4.0-1136.145+fips1","5.4.0-1137.146+fips1","5.4.0-1138.147+fips1","5.4.0-1139.148+fips1","5.4.0-1140.149+fips1","5.4.0-1141.150+fips1","5.4.0-1142.151+fips1","5.4.0-1143.152+fips1","5.4.0-1145.154+fips1","5.4.0-1146.155+fips1","5.4.0-1147.156+fips1","5.4.0-1148.157+fips1","5.4.0-1149.158+fips1","5.4.0-1150.159+fips1","5.4.0-1151.160+fips1","5.4.0-1152.161+fips1","5.4.0-1153.162+fips1","5.4.0-1154.163+fips1","5.4.0-1155.164+fips1","5.4.0-1156.165+fips1","5.4.0-1157.166+fips1","5.4.0-1159.168+fips1","5.4.0-1160.169+fips1","5.4.0-1161.170+fips1","5.4.0-1162.171+fips1","5.4.0-1163.172+fips1","5.4.0-1164.173+fips1","5.4.0-1165.174+fips1","5.4.0-1166.175+fips1","5.4.0-1167.176+fips1","5.4.0-1168.178+fips1","5.4.0-1169.179+fips1","5.4.0-1170.180+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173"}]}],"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"]},{"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-1097.104"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.110"}]}],"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"]},{"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-1102.111.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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.53~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.106"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50~22.04.2"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1093.99"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1080.88"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.98"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1089.94"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.93"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1049.49"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1038.38"}]}],"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"]},{"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-1094.100"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.65"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.83"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1089.91"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1096.105"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.104+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.110+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.106+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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1046.52"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-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-1046.53"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51"]},{"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-1047.50"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1043.48"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.33"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-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-1044.44"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-intel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1005.12","6.8.0-1006.13","6.8.0-1007.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.20"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1043.44"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1047.51"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1023.24"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1016.20"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2037.38"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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-1046.49+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu: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-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.104~20.04.1"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.106~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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173~20.04.1"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94~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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.98~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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173~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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1049.49~20.04.1"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.100~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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.104"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.98"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1092.93"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1049.49"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1038.38"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.100"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1061.65"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1089.91"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1096.105"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.104+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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-163.173+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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.106+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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.106"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1093.99"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1080.88"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.94"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.110+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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.110"}]}],"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"],"bundled":178},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1089.94"}]}],"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"],"bundled":186},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.111~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"],"bundled":187},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.51"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2037.38"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1041.42"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.33"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.44"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.49.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1044.44"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50~22.04.2"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.50"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1043.48"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47"],"bundled":752},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-100.100.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1023.24"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.52+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1"],"bundled":753},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1"],"bundled":1179}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"simatic cn 4100"}],"references":[{"url":"https://git.kernel.org/stable/c/73f7da507d787b489761a0fa280716f84fa32b2f","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/76a4c6636a69d69409aa253b049b1be717a539c5","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/ccf0ad56a779e6704c0b27f555dec847f50c7557","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/13604b1d7e7b125fb428cddbec6b8d92baad25d5","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/291bb5d931c6f3cd7227b913302a17be21cf53b0","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/f7534cbfac0a9ffa4fa17cacc6e8b6446dae24ee","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/6f93694bcbc2c2ab3e01cd8fba2f296faf34e6b9","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/1ca69007e52a73bd8b84b988b61b319816ca8b01","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/94458781aee6045bd3d0ad4b80b02886b9e2219b","tags":["Patch","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html","tags":["Mailing List","Third Party Advisory","web"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html","tags":["Mailing List","Third Party Advisory","web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-032379.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38713","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-f84m-84r4-h992"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-38713","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu18.04els/CLSA-2026-1773832495.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-4439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49763","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53285","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53311","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53506","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53515","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53521","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53554","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53596","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53604","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53608","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21727","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21765","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37810","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38459","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38530","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38563","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38714","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39691","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39702","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39993","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu16.04els/CLSA-2026-1773872435.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21957","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1775224807.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu16.04els/CLSA-2026-1775779453.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49581","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49775","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50022","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50384","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38415","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38538","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38677","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38713.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-38713","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2025-0234.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34595","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.102","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.103","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.104","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.105","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2025-0235.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34594","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54263","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68229","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71125","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38489","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40284","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40311","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40314","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40319","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68184","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68218","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68219","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68295","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71151","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1304","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1305","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40058","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503600-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1213061","tags":["report"]},{"url":"https://bugzilla.suse.com/1213666","tags":["report"]},{"url":"https://bugzilla.suse.com/1214073","tags":["report"]},{"url":"https://bugzilla.suse.com/1214928","tags":["report"]},{"url":"https://bugzilla.suse.com/1214953","tags":["report"]},{"url":"https://bugzilla.suse.com/1215150","tags":["report"]},{"url":"https://bugzilla.suse.com/1215696","tags":["report"]},{"url":"https://bugzilla.suse.com/1216436","tags":["report"]},{"url":"https://bugzilla.suse.com/1216976","tags":["report"]},{"url":"https://bugzilla.suse.com/1218644","tags":["report"]},{"url":"https://bugzilla.suse.com/1220186","tags":["report"]},{"url":"https://bugzilla.suse.com/1220419","tags":["report"]},{"url":"https://bugzilla.suse.com/1229165","tags":["report"]},{"url":"https://bugzilla.suse.com/1230062","tags":["report"]},{"url":"https://bugzilla.suse.com/1236897","tags":["report"]},{"url":"https://bugzilla.suse.com/1237449","tags":["report"]},{"url":"https://bugzilla.suse.com/1237776","tags":["report"]},{"url":"https://bugzilla.suse.com/1240324","tags":["report"]},{"url":"https://bugzilla.suse.com/1241166","tags":["report"]},{"url":"https://bugzilla.suse.com/1241292","tags":["report"]},{"url":"https://bugzilla.suse.com/1241866","tags":["report"]},{"url":"https://bugzilla.suse.com/1243100","tags":["report"]},{"url":"https://bugzilla.suse.com/1243112","tags":["report"]},{"url":"https://bugzilla.suse.com/1245193","tags":["report"]},{"url":"https://bugzilla.suse.com/1245260","tags":["report"]},{"url":"https://bugzilla.suse.com/1245700","tags":["report"]},{"url":"https://bugzilla.suse.com/1246057","tags":["report"]},{"url":"https://bugzilla.suse.com/1246125","tags":["report"]},{"url":"https://bugzilla.suse.com/1246190","tags":["report"]},{"url":"https://bugzilla.suse.com/1246248","tags":["report"]},{"url":"https://bugzilla.suse.com/1246298","tags":["report"]},{"url":"https://bugzilla.suse.com/1246509","tags":["report"]},{"url":"https://bugzilla.suse.com/1246782","tags":["report"]},{"url":"https://bugzilla.suse.com/1247099","tags":["report"]},{"url":"https://bugzilla.suse.com/1247118","tags":["report"]},{"url":"https://bugzilla.suse.com/1247126","tags":["report"]},{"url":"https://bugzilla.suse.com/1247136","tags":["report"]},{"url":"https://bugzilla.suse.com/1247137","tags":["report"]},{"url":"https://bugzilla.suse.com/1247223","tags":["report"]},{"url":"https://bugzilla.suse.com/1247239","tags":["report"]},{"url":"https://bugzilla.suse.com/1247262","tags":["report"]},{"url":"https://bugzilla.suse.com/1247442","tags":["report"]},{"url":"https://bugzilla.suse.com/1247483","tags":["report"]},{"url":"https://bugzilla.suse.com/1247500","tags":["report"]},{"url":"https://bugzilla.suse.com/1247963","tags":["report"]},{"url":"https://bugzilla.suse.com/1248111","tags":["report"]},{"url":"https://bugzilla.suse.com/1248121","tags":["report"]},{"url":"https://bugzilla.suse.com/1248192","tags":["report"]},{"url":"https://bugzilla.suse.com/1248199","tags":["report"]},{"url":"https://bugzilla.suse.com/1248200","tags":["report"]},{"url":"https://bugzilla.suse.com/1248202","tags":["report"]},{"url":"https://bugzilla.suse.com/1248225","tags":["report"]},{"url":"https://bugzilla.suse.com/1248296","tags":["report"]},{"url":"https://bugzilla.suse.com/1248334","tags":["report"]},{"url":"https://bugzilla.suse.com/1248343","tags":["report"]},{"url":"https://bugzilla.suse.com/1248357","tags":["report"]},{"url":"https://bugzilla.suse.com/1248360","tags":["report"]},{"url":"https://bugzilla.suse.com/1248365","tags":["report"]},{"url":"https://bugzilla.suse.com/1248378","tags":["report"]},{"url":"https://bugzilla.suse.com/1248380","tags":["report"]},{"url":"https://bugzilla.suse.com/1248392","tags":["report"]},{"url":"https://bugzilla.suse.com/1248512","tags":["report"]},{"url":"https://bugzilla.suse.com/1248610","tags":["report"]},{"url":"https://bugzilla.suse.com/1248619","tags":["report"]},{"url":"https://bugzilla.suse.com/1248622","tags":["report"]},{"url":"https://bugzilla.suse.com/1248626","tags":["report"]},{"url":"https://bugzilla.suse.com/1248628","tags":["report"]},{"url":"https://bugzilla.suse.com/1248634","tags":["report"]},{"url":"https://bugzilla.suse.com/1248639","tags":["report"]},{"url":"https://bugzilla.suse.com/1248647","tags":["report"]},{"url":"https://bugzilla.suse.com/1248674","tags":["report"]},{"url":"https://bugzilla.suse.com/1248681","tags":["report"]},{"url":"https://bugzilla.suse.com/1248733","tags":["report"]},{"url":"https://bugzilla.suse.com/1248734","tags":["report"]},{"url":"https://bugzilla.suse.com/1248735","tags":["report"]},{"url":"https://bugzilla.suse.com/1248775","tags":["report"]},{"url":"https://bugzilla.suse.com/1248847","tags":["report"]},{"url":"https://bugzilla.suse.com/1249122","tags":["report"]},{"url":"https://bugzilla.suse.com/1249123","tags":["report"]},{"url":"https://bugzilla.suse.com/1249124","tags":["report"]},{"url":"https://bugzilla.suse.com/1249125","tags":["report"]},{"url":"https://bugzilla.suse.com/1249126","tags":["report"]},{"url":"https://bugzilla.suse.com/1249143","tags":["report"]},{"url":"https://bugzilla.suse.com/1249156","tags":["report"]},{"url":"https://bugzilla.suse.com/1249159","tags":["report"]},{"url":"https://bugzilla.suse.com/1249163","tags":["report"]},{"url":"https://bugzilla.suse.com/1249164","tags":["report"]},{"url":"https://bugzilla.suse.com/1249166","tags":["report"]},{"url":"https://bugzilla.suse.com/1249169","tags":["report"]},{"url":"https://bugzilla.suse.com/1249170","tags":["report"]},{"url":"https://bugzilla.suse.com/1249172","tags":["report"]},{"url":"https://bugzilla.suse.com/1249176","tags":["report"]},{"url":"https://bugzilla.suse.com/1249177","tags":["report"]},{"url":"https://bugzilla.suse.com/1249186","tags":["report"]},{"url":"https://bugzilla.suse.com/1249190","tags":["report"]},{"url":"https://bugzilla.suse.com/1249194","tags":["report"]},{"url":"https://bugzilla.suse.com/1249195","tags":["report"]},{"url":"https://bugzilla.suse.com/1249196","tags":["report"]},{"url":"https://bugzilla.suse.com/1249199","tags":["report"]},{"url":"https://bugzilla.suse.com/1249200","tags":["report"]},{"url":"https://bugzilla.suse.com/1249202","tags":["report"]},{"url":"https://bugzilla.suse.com/1249203","tags":["report"]},{"url":"https://bugzilla.suse.com/1249204","tags":["report"]},{"url":"https://bugzilla.suse.com/1249206","tags":["report"]},{"url":"https://bugzilla.suse.com/1249215","tags":["report"]},{"url":"https://bugzilla.suse.com/1249220","tags":["report"]},{"url":"https://bugzilla.suse.com/1249221","tags":["report"]},{"url":"https://bugzilla.suse.com/1249254","tags":["report"]},{"url":"https://bugzilla.suse.com/1249255","tags":["report"]},{"url":"https://bugzilla.suse.com/1249257","tags":["report"]},{"url":"https://bugzilla.suse.com/1249258","tags":["report"]},{"url":"https://bugzilla.suse.com/1249260","tags":["report"]},{"url":"https://bugzilla.suse.com/1249262","tags":["report"]},{"url":"https://bugzilla.suse.com/1249263","tags":["report"]},{"url":"https://bugzilla.suse.com/1249265","tags":["report"]},{"url":"https://bugzilla.suse.com/1249266","tags":["report"]},{"url":"https://bugzilla.suse.com/1249271","tags":["report"]},{"url":"https://bugzilla.suse.com/1249272","tags":["report"]},{"url":"https://bugzilla.suse.com/1249273","tags":["report"]},{"url":"https://bugzilla.suse.com/1249278","tags":["report"]},{"url":"https://bugzilla.suse.com/1249279","tags":["report"]},{"url":"https://bugzilla.suse.com/1249281","tags":["report"]},{"url":"https://bugzilla.suse.com/1249282","tags":["report"]},{"url":"https://bugzilla.suse.com/1249284","tags":["report"]},{"url":"https://bugzilla.suse.com/1249285","tags":["report"]},{"url":"https://bugzilla.suse.com/1249288","tags":["report"]},{"url":"https://bugzilla.suse.com/1249290","tags":["report"]},{"url":"https://bugzilla.suse.com/1249292","tags":["report"]},{"url":"https://bugzilla.suse.com/1249295","tags":["report"]},{"url":"https://bugzilla.suse.com/1249296","tags":["report"]},{"url":"https://bugzilla.suse.com/1249299","tags":["report"]},{"url":"https://bugzilla.suse.com/1249300","tags":["report"]},{"url":"https://bugzilla.suse.com/1249303","tags":["report"]},{"url":"https://bugzilla.suse.com/1249304","tags":["report"]},{"url":"https://bugzilla.suse.com/1249305","tags":["report"]},{"url":"https://bugzilla.suse.com/1249308","tags":["report"]},{"url":"https://bugzilla.suse.com/1249312","tags":["report"]},{"url":"https://bugzilla.suse.com/1249315","tags":["report"]},{"url":"https://bugzilla.suse.com/1249318","tags":["report"]},{"url":"https://bugzilla.suse.com/1249321","tags":["report"]},{"url":"https://bugzilla.suse.com/1249323","tags":["report"]},{"url":"https://bugzilla.suse.com/1249324","tags":["report"]},{"url":"https://bugzilla.suse.com/1249334","tags":["report"]},{"url":"https://bugzilla.suse.com/1249338","tags":["report"]},{"url":"https://bugzilla.suse.com/1249374","tags":["report"]},{"url":"https://bugzilla.suse.com/1249413","tags":["report"]},{"url":"https://bugzilla.suse.com/1249479","tags":["report"]},{"url":"https://bugzilla.suse.com/1249482","tags":["report"]},{"url":"https://bugzilla.suse.com/1249486","tags":["report"]},{"url":"https://bugzilla.suse.com/1249488","tags":["report"]},{"url":"https://bugzilla.suse.com/1249489","tags":["report"]},{"url":"https://bugzilla.suse.com/1249490","tags":["report"]},{"url":"https://bugzilla.suse.com/1249494","tags":["report"]},{"url":"https://bugzilla.suse.com/1249504","tags":["report"]},{"url":"https://bugzilla.suse.com/1249506","tags":["report"]},{"url":"https://bugzilla.suse.com/1249508","tags":["report"]},{"url":"https://bugzilla.suse.com/1249510","tags":["report"]},{"url":"https://bugzilla.suse.com/1249513","tags":["report"]},{"url":"https://bugzilla.suse.com/1249515","tags":["report"]},{"url":"https://bugzilla.suse.com/1249516","tags":["report"]},{"url":"https://bugzilla.suse.com/1249522","tags":["report"]},{"url":"https://bugzilla.suse.com/1249523","tags":["report"]},{"url":"https://bugzilla.suse.com/1249524","tags":["report"]},{"url":"https://bugzilla.suse.com/1249526","tags":["report"]},{"url":"https://bugzilla.suse.com/1249533","tags":["report"]},{"url":"https://bugzilla.suse.com/1249538","tags":["report"]},{"url":"https://bugzilla.suse.com/1249540","tags":["report"]},{"url":"https://bugzilla.suse.com/1249542","tags":["report"]},{"url":"https://bugzilla.suse.com/1249545","tags":["report"]},{"url":"https://bugzilla.suse.com/1249548","tags":["report"]},{"url":"https://bugzilla.suse.com/1249554","tags":["report"]},{"url":"https://bugzilla.suse.com/1249598","tags":["report"]},{"url":"https://bugzilla.suse.com/1249604","tags":["report"]},{"url":"https://bugzilla.suse.com/1249608","tags":["report"]},{"url":"https://bugzilla.suse.com/1249615","tags":["report"]},{"url":"https://bugzilla.suse.com/1249640","tags":["report"]},{"url":"https://bugzilla.suse.com/1249641","tags":["report"]},{"url":"https://bugzilla.suse.com/1249642","tags":["report"]},{"url":"https://bugzilla.suse.com/1249658","tags":["report"]},{"url":"https://bugzilla.suse.com/1249662","tags":["report"]},{"url":"https://bugzilla.suse.com/1249672","tags":["report"]},{"url":"https://bugzilla.suse.com/1249673","tags":["report"]},{"url":"https://bugzilla.suse.com/1249677","tags":["report"]},{"url":"https://bugzilla.suse.com/1249678","tags":["report"]},{"url":"https://bugzilla.suse.com/1249679","tags":["report"]},{"url":"https://bugzilla.suse.com/1249682","tags":["report"]},{"url":"https://bugzilla.suse.com/1249687","tags":["report"]},{"url":"https://bugzilla.suse.com/1249698","tags":["report"]},{"url":"https://bugzilla.suse.com/1249707","tags":["report"]},{"url":"https://bugzilla.suse.com/1249712","tags":["report"]},{"url":"https://bugzilla.suse.com/1249730","tags":["report"]},{"url":"https://bugzilla.suse.com/1249756","tags":["report"]},{"url":"https://bugzilla.suse.com/1249758","tags":["report"]},{"url":"https://bugzilla.suse.com/1249761","tags":["report"]},{"url":"https://bugzilla.suse.com/1249762","tags":["report"]},{"url":"https://bugzilla.suse.com/1249768","tags":["report"]},{"url":"https://bugzilla.suse.com/1249770","tags":["report"]},{"url":"https://bugzilla.suse.com/1249774","tags":["report"]},{"url":"https://bugzilla.suse.com/1249779","tags":["report"]},{"url":"https://bugzilla.suse.com/1249780","tags":["report"]},{"url":"https://bugzilla.suse.com/1249785","tags":["report"]},{"url":"https://bugzilla.suse.com/1249787","tags":["report"]},{"url":"https://bugzilla.suse.com/1249795","tags":["report"]},{"url":"https://bugzilla.suse.com/1249815","tags":["report"]},{"url":"https://bugzilla.suse.com/1249820","tags":["report"]},{"url":"https://bugzilla.suse.com/1249823","tags":["report"]},{"url":"https://bugzilla.suse.com/1249824","tags":["report"]},{"url":"https://bugzilla.suse.com/1249825","tags":["report"]},{"url":"https://bugzilla.suse.com/1249826","tags":["report"]},{"url":"https://bugzilla.suse.com/1249833","tags":["report"]},{"url":"https://bugzilla.suse.com/1249842","tags":["report"]},{"url":"https://bugzilla.suse.com/1249845","tags":["report"]},{"url":"https://bugzilla.suse.com/1249849","tags":["report"]},{"url":"https://bugzilla.suse.com/1249850","tags":["report"]},{"url":"https://bugzilla.suse.com/1249853","tags":["report"]},{"url":"https://bugzilla.suse.com/1249856","tags":["report"]},{"url":"https://bugzilla.suse.com/1249861","tags":["report"]},{"url":"https://bugzilla.suse.com/1249863","tags":["report"]},{"url":"https://bugzilla.suse.com/1249864","tags":["report"]},{"url":"https://bugzilla.suse.com/1249865","tags":["report"]},{"url":"https://bugzilla.suse.com/1249866","tags":["report"]},{"url":"https://bugzilla.suse.com/1249869","tags":["report"]},{"url":"https://bugzilla.suse.com/1249870","tags":["report"]},{"url":"https://bugzilla.suse.com/1249880","tags":["report"]},{"url":"https://bugzilla.suse.com/1249883","tags":["report"]},{"url":"https://bugzilla.suse.com/1249888","tags":["report"]},{"url":"https://bugzilla.suse.com/1249894","tags":["report"]},{"url":"https://bugzilla.suse.com/1249896","tags":["report"]},{"url":"https://bugzilla.suse.com/1249897","tags":["report"]},{"url":"https://bugzilla.suse.com/1249901","tags":["report"]},{"url":"https://bugzilla.suse.com/1249911","tags":["report"]},{"url":"https://bugzilla.suse.com/1249917","tags":["report"]},{"url":"https://bugzilla.suse.com/1249919","tags":["report"]},{"url":"https://bugzilla.suse.com/1249923","tags":["report"]},{"url":"https://bugzilla.suse.com/1249926","tags":["report"]},{"url":"https://bugzilla.suse.com/1249938","tags":["report"]},{"url":"https://bugzilla.suse.com/1249949","tags":["report"]},{"url":"https://bugzilla.suse.com/1249950","tags":["report"]},{"url":"https://bugzilla.suse.com/1249952","tags":["report"]},{"url":"https://bugzilla.suse.com/1249975","tags":["report"]},{"url":"https://bugzilla.suse.com/1249979","tags":["report"]},{"url":"https://bugzilla.suse.com/1249984","tags":["report"]},{"url":"https://bugzilla.suse.com/1249988","tags":["report"]},{"url":"https://bugzilla.suse.com/1249990","tags":["report"]},{"url":"https://bugzilla.suse.com/1249993","tags":["report"]},{"url":"https://bugzilla.suse.com/1249994","tags":["report"]},{"url":"https://bugzilla.suse.com/1249997","tags":["report"]},{"url":"https://bugzilla.suse.com/1250002","tags":["report"]},{"url":"https://bugzilla.suse.com/1250004","tags":["report"]},{"url":"https://bugzilla.suse.com/1250007","tags":["report"]},{"url":"https://bugzilla.suse.com/1250012","tags":["report"]},{"url":"https://bugzilla.suse.com/1250022","tags":["report"]},{"url":"https://bugzilla.suse.com/1250024","tags":["report"]},{"url":"https://bugzilla.suse.com/1250025","tags":["report"]},{"url":"https://bugzilla.suse.com/1250028","tags":["report"]},{"url":"https://bugzilla.suse.com/1250029","tags":["report"]},{"url":"https://bugzilla.suse.com/1250035","tags":["report"]},{"url":"https://bugzilla.suse.com/1250049","tags":["report"]},{"url":"https://bugzilla.suse.com/1250055","tags":["report"]},{"url":"https://bugzilla.suse.com/1250057","tags":["report"]},{"url":"https://bugzilla.suse.com/1250058","tags":["report"]},{"url":"https://bugzilla.suse.com/1250062","tags":["report"]},{"url":"https://bugzilla.suse.com/1250063","tags":["report"]},{"url":"https://bugzilla.suse.com/1250065","tags":["report"]},{"url":"https://bugzilla.suse.com/1250066","tags":["report"]},{"url":"https://bugzilla.suse.com/1250067","tags":["report"]},{"url":"https://bugzilla.suse.com/1250069","tags":["report"]},{"url":"https://bugzilla.suse.com/1250070","tags":["report"]},{"url":"https://bugzilla.suse.com/1250073","tags":["report"]},{"url":"https://bugzilla.suse.com/1250074","tags":["report"]},{"url":"https://bugzilla.suse.com/1250088","tags":["report"]},{"url":"https://bugzilla.suse.com/1250089","tags":["report"]},{"url":"https://bugzilla.suse.com/1250106","tags":["report"]},{"url":"https://bugzilla.suse.com/1250112","tags":["report"]},{"url":"https://bugzilla.suse.com/1250117","tags":["report"]},{"url":"https://bugzilla.suse.com/1250120","tags":["report"]},{"url":"https://bugzilla.suse.com/1250125","tags":["report"]},{"url":"https://bugzilla.suse.com/1250127","tags":["report"]},{"url":"https://bugzilla.suse.com/1250128","tags":["report"]},{"url":"https://bugzilla.suse.com/1250145","tags":["report"]},{"url":"https://bugzilla.suse.com/1250150","tags":["report"]},{"url":"https://bugzilla.suse.com/1250156","tags":["report"]},{"url":"https://bugzilla.suse.com/1250157","tags":["report"]},{"url":"https://bugzilla.suse.com/1250161","tags":["report"]},{"url":"https://bugzilla.suse.com/1250163","tags":["report"]},{"url":"https://bugzilla.suse.com/1250166","tags":["report"]},{"url":"https://bugzilla.suse.com/1250167","tags":["report"]},{"url":"https://bugzilla.suse.com/1250171","tags":["report"]},{"url":"https://bugzilla.suse.com/1250177","tags":["report"]},{"url":"https://bugzilla.suse.com/1250179","tags":["report"]},{"url":"https://bugzilla.suse.com/1250180","tags":["report"]},{"url":"https://bugzilla.suse.com/1250186","tags":["report"]},{"url":"https://bugzilla.suse.com/1250196","tags":["report"]},{"url":"https://bugzilla.suse.com/1250198","tags":["report"]},{"url":"https://bugzilla.suse.com/1250199","tags":["report"]},{"url":"https://bugzilla.suse.com/1250201","tags":["report"]},{"url":"https://bugzilla.suse.com/1250203","tags":["report"]},{"url":"https://bugzilla.suse.com/1250204","tags":["report"]},{"url":"https://bugzilla.suse.com/1250206","tags":["report"]},{"url":"https://bugzilla.suse.com/1250208","tags":["report"]},{"url":"https://bugzilla.suse.com/1250241","tags":["report"]},{"url":"https://bugzilla.suse.com/1250242","tags":["report"]},{"url":"https://bugzilla.suse.com/1250243","tags":["report"]},{"url":"https://bugzilla.suse.com/1250247","tags":["report"]},{"url":"https://bugzilla.suse.com/1250249","tags":["report"]},{"url":"https://bugzilla.suse.com/1250251","tags":["report"]},{"url":"https://bugzilla.suse.com/1250262","tags":["report"]},{"url":"https://bugzilla.suse.com/1250263","tags":["report"]},{"url":"https://bugzilla.suse.com/1250266","tags":["report"]},{"url":"https://bugzilla.suse.com/1250267","tags":["report"]},{"url":"https://bugzilla.suse.com/1250268","tags":["report"]},{"url":"https://bugzilla.suse.com/1250275","tags":["report"]},{"url":"https://bugzilla.suse.com/1250276","tags":["report"]},{"url":"https://bugzilla.suse.com/1250281","tags":["report"]},{"url":"https://bugzilla.suse.com/1250290","tags":["report"]},{"url":"https://bugzilla.suse.com/1250291","tags":["report"]},{"url":"https://bugzilla.suse.com/1250292","tags":["report"]},{"url":"https://bugzilla.suse.com/1250294","tags":["report"]},{"url":"https://bugzilla.suse.com/1250297","tags":["report"]},{"url":"https://bugzilla.suse.com/1250298","tags":["report"]},{"url":"https://bugzilla.suse.com/1250313","tags":["report"]},{"url":"https://bugzilla.suse.com/1250319","tags":["report"]},{"url":"https://bugzilla.suse.com/1250323","tags":["report"]},{"url":"https://bugzilla.suse.com/1250325","tags":["report"]},{"url":"https://bugzilla.suse.com/1250329","tags":["report"]},{"url":"https://bugzilla.suse.com/1250336","tags":["report"]},{"url":"https://bugzilla.suse.com/1250337","tags":["report"]},{"url":"https://bugzilla.suse.com/1250344","tags":["report"]},{"url":"https://bugzilla.suse.com/1250358","tags":["report"]},{"url":"https://bugzilla.suse.com/1250365","tags":["report"]},{"url":"https://bugzilla.suse.com/1250371","tags":["report"]},{"url":"https://bugzilla.suse.com/1250377","tags":["report"]},{"url":"https://bugzilla.suse.com/1250384","tags":["report"]},{"url":"https://bugzilla.suse.com/1250389","tags":["report"]},{"url":"https://bugzilla.suse.com/1250395","tags":["report"]},{"url":"https://bugzilla.suse.com/1250397","tags":["report"]},{"url":"https://bugzilla.suse.com/1250402","tags":["report"]},{"url":"https://bugzilla.suse.com/1250406","tags":["report"]},{"url":"https://bugzilla.suse.com/1250407","tags":["report"]},{"url":"https://bugzilla.suse.com/1250426","tags":["report"]},{"url":"https://bugzilla.suse.com/1250450","tags":["report"]},{"url":"https://bugzilla.suse.com/1250459","tags":["report"]},{"url":"https://bugzilla.suse.com/1250519","tags":["report"]},{"url":"https://bugzilla.suse.com/1250522","tags":["report"]},{"url":"https://bugzilla.suse.com/1250530","tags":["report"]},{"url":"https://bugzilla.suse.com/1250655","tags":["report"]},{"url":"https://bugzilla.suse.com/1250712","tags":["report"]},{"url":"https://bugzilla.suse.com/1250713","tags":["report"]},{"url":"https://bugzilla.suse.com/1250732","tags":["report"]},{"url":"https://bugzilla.suse.com/1250736","tags":["report"]},{"url":"https://bugzilla.suse.com/1250741","tags":["report"]},{"url":"https://bugzilla.suse.com/1250759","tags":["report"]},{"url":"https://bugzilla.suse.com/1250763","tags":["report"]},{"url":"https://bugzilla.suse.com/1250765","tags":["report"]},{"url":"https://bugzilla.suse.com/1250807","tags":["report"]},{"url":"https://bugzilla.suse.com/1250808","tags":["report"]},{"url":"https://bugzilla.suse.com/1250809","tags":["report"]},{"url":"https://bugzilla.suse.com/1250812","tags":["report"]},{"url":"https://bugzilla.suse.com/1250813","tags":["report"]},{"url":"https://bugzilla.suse.com/1250815","tags":["report"]},{"url":"https://bugzilla.suse.com/1250816","tags":["report"]},{"url":"https://bugzilla.suse.com/1250820","tags":["report"]},{"url":"https://bugzilla.suse.com/1250823","tags":["report"]},{"url":"https://bugzilla.suse.com/1250825","tags":["report"]},{"url":"https://bugzilla.suse.com/1250827","tags":["report"]},{"url":"https://bugzilla.suse.com/1250830","tags":["report"]},{"url":"https://bugzilla.suse.com/1250831","tags":["report"]},{"url":"https://bugzilla.suse.com/1250837","tags":["report"]},{"url":"https://bugzilla.suse.com/1250841","tags":["report"]},{"url":"https://bugzilla.suse.com/1250861","tags":["report"]},{"url":"https://bugzilla.suse.com/1250863","tags":["report"]},{"url":"https://bugzilla.suse.com/1250867","tags":["report"]},{"url":"https://bugzilla.suse.com/1250872","tags":["report"]},{"url":"https://bugzilla.suse.com/1250873","tags":["report"]},{"url":"https://bugzilla.suse.com/1250878","tags":["report"]},{"url":"https://bugzilla.suse.com/1250905","tags":["report"]},{"url":"https://bugzilla.suse.com/1250907","tags":["report"]},{"url":"https://bugzilla.suse.com/1250917","tags":["report"]},{"url":"https://bugzilla.suse.com/1250918","tags":["report"]},{"url":"https://bugzilla.suse.com/1250923","tags":["report"]},{"url":"https://bugzilla.suse.com/1250926","tags":["report"]},{"url":"https://bugzilla.suse.com/1250928","tags":["report"]},{"url":"https://bugzilla.suse.com/1250929","tags":["report"]},{"url":"https://bugzilla.suse.com/1250930","tags":["report"]},{"url":"https://bugzilla.suse.com/1250931","tags":["report"]},{"url":"https://bugzilla.suse.com/1250941","tags":["report"]},{"url":"https://bugzilla.suse.com/1250942","tags":["report"]},{"url":"https://bugzilla.suse.com/1250949","tags":["report"]},{"url":"https://bugzilla.suse.com/1250952","tags":["report"]},{"url":"https://bugzilla.suse.com/1250957","tags":["report"]},{"url":"https://bugzilla.suse.com/1250964","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-39197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53520","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40300","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503613-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1202700","tags":["report"]},{"url":"https://bugzilla.suse.com/1203063","tags":["report"]},{"url":"https://bugzilla.suse.com/1203332","tags":["report"]},{"url":"https://bugzilla.suse.com/1204228","tags":["report"]},{"url":"https://bugzilla.suse.com/1205128","tags":["report"]},{"url":"https://bugzilla.suse.com/1206883","tags":["report"]},{"url":"https://bugzilla.suse.com/1206884","tags":["report"]},{"url":"https://bugzilla.suse.com/1209287","tags":["report"]},{"url":"https://bugzilla.suse.com/1209291","tags":["report"]},{"url":"https://bugzilla.suse.com/1210124","tags":["report"]},{"url":"https://bugzilla.suse.com/1210584","tags":["report"]},{"url":"https://bugzilla.suse.com/1220185","tags":["report"]},{"url":"https://bugzilla.suse.com/1240784","tags":["report"]},{"url":"https://bugzilla.suse.com/1241353","tags":["report"]},{"url":"https://bugzilla.suse.com/1243278","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1245110","tags":["report"]},{"url":"https://bugzilla.suse.com/1245956","tags":["report"]},{"url":"https://bugzilla.suse.com/1246879","tags":["report"]},{"url":"https://bugzilla.suse.com/1246968","tags":["report"]},{"url":"https://bugzilla.suse.com/1247172","tags":["report"]},{"url":"https://bugzilla.suse.com/1248108","tags":["report"]},{"url":"https://bugzilla.suse.com/1248255","tags":["report"]},{"url":"https://bugzilla.suse.com/1248399","tags":["report"]},{"url":"https://bugzilla.suse.com/1249346","tags":["report"]},{"url":"https://bugzilla.suse.com/1249664","tags":["report"]},{"url":"https://bugzilla.suse.com/1249667","tags":["report"]},{"url":"https://bugzilla.suse.com/1249700","tags":["report"]},{"url":"https://bugzilla.suse.com/1249713","tags":["report"]},{"url":"https://bugzilla.suse.com/1249716","tags":["report"]},{"url":"https://bugzilla.suse.com/1249718","tags":["report"]},{"url":"https://bugzilla.suse.com/1249734","tags":["report"]},{"url":"https://bugzilla.suse.com/1249740","tags":["report"]},{"url":"https://bugzilla.suse.com/1249743","tags":["report"]},{"url":"https://bugzilla.suse.com/1249747","tags":["report"]},{"url":"https://bugzilla.suse.com/1249808","tags":["report"]},{"url":"https://bugzilla.suse.com/1249827","tags":["report"]},{"url":"https://bugzilla.suse.com/1249840","tags":["report"]},{"url":"https://bugzilla.suse.com/1249846","tags":["report"]},{"url":"https://bugzilla.suse.com/1249885","tags":["report"]},{"url":"https://bugzilla.suse.com/1249908","tags":["report"]},{"url":"https://bugzilla.suse.com/1249918","tags":["report"]},{"url":"https://bugzilla.suse.com/1249930","tags":["report"]},{"url":"https://bugzilla.suse.com/1249947","tags":["report"]},{"url":"https://bugzilla.suse.com/1250009","tags":["report"]},{"url":"https://bugzilla.suse.com/1250014","tags":["report"]},{"url":"https://bugzilla.suse.com/1250041","tags":["report"]},{"url":"https://bugzilla.suse.com/1250131","tags":["report"]},{"url":"https://bugzilla.suse.com/1250132","tags":["report"]},{"url":"https://bugzilla.suse.com/1250140","tags":["report"]},{"url":"https://bugzilla.suse.com/1250183","tags":["report"]},{"url":"https://bugzilla.suse.com/1250187","tags":["report"]},{"url":"https://bugzilla.suse.com/1250257","tags":["report"]},{"url":"https://bugzilla.suse.com/1250269","tags":["report"]},{"url":"https://bugzilla.suse.com/1250277","tags":["report"]},{"url":"https://bugzilla.suse.com/1250301","tags":["report"]},{"url":"https://bugzilla.suse.com/1250391","tags":["report"]},{"url":"https://bugzilla.suse.com/1250392","tags":["report"]},{"url":"https://bugzilla.suse.com/1250394","tags":["report"]},{"url":"https://bugzilla.suse.com/1250764","tags":["report"]},{"url":"https://bugzilla.suse.com/1250767","tags":["report"]},{"url":"https://bugzilla.suse.com/1250774","tags":["report"]},{"url":"https://bugzilla.suse.com/1250787","tags":["report"]},{"url":"https://bugzilla.suse.com/1250790","tags":["report"]},{"url":"https://bugzilla.suse.com/1250797","tags":["report"]},{"url":"https://bugzilla.suse.com/1250799","tags":["report"]},{"url":"https://bugzilla.suse.com/1250847","tags":["report"]},{"url":"https://bugzilla.suse.com/1250850","tags":["report"]},{"url":"https://bugzilla.suse.com/1250853","tags":["report"]},{"url":"https://bugzilla.suse.com/1250868","tags":["report"]},{"url":"https://bugzilla.suse.com/1250890","tags":["report"]},{"url":"https://bugzilla.suse.com/1250891","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-4460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-36280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-43945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50431","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-28328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38572","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503614-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1082555","tags":["report"]},{"url":"https://bugzilla.suse.com/1164051","tags":["report"]},{"url":"https://bugzilla.suse.com/1190317","tags":["report"]},{"url":"https://bugzilla.suse.com/1207629","tags":["report"]},{"url":"https://bugzilla.suse.com/1211960","tags":["report"]},{"url":"https://bugzilla.suse.com/1213015","tags":["report"]},{"url":"https://bugzilla.suse.com/1213016","tags":["report"]},{"url":"https://bugzilla.suse.com/1213040","tags":["report"]},{"url":"https://bugzilla.suse.com/1213041","tags":["report"]},{"url":"https://bugzilla.suse.com/1213133","tags":["report"]},{"url":"https://bugzilla.suse.com/1213747","tags":["report"]},{"url":"https://bugzilla.suse.com/1214967","tags":["report"]},{"url":"https://bugzilla.suse.com/1235459","tags":["report"]},{"url":"https://bugzilla.suse.com/1238467","tags":["report"]},{"url":"https://bugzilla.suse.com/1245196","tags":["report"]},{"url":"https://bugzilla.suse.com/1248333","tags":["report"]},{"url":"https://bugzilla.suse.com/1248341","tags":["report"]},{"url":"https://bugzilla.suse.com/1248617","tags":["report"]},{"url":"https://bugzilla.suse.com/1248648","tags":["report"]},{"url":"https://bugzilla.suse.com/1248669","tags":["report"]},{"url":"https://bugzilla.suse.com/1249037","tags":["report"]},{"url":"https://bugzilla.suse.com/1249647","tags":["report"]},{"url":"https://bugzilla.suse.com/1249683","tags":["report"]},{"url":"https://bugzilla.suse.com/1249696","tags":["report"]},{"url":"https://bugzilla.suse.com/1249706","tags":["report"]},{"url":"https://bugzilla.suse.com/1249715","tags":["report"]},{"url":"https://bugzilla.suse.com/1249720","tags":["report"]},{"url":"https://bugzilla.suse.com/1249725","tags":["report"]},{"url":"https://bugzilla.suse.com/1249727","tags":["report"]},{"url":"https://bugzilla.suse.com/1249739","tags":["report"]},{"url":"https://bugzilla.suse.com/1249744","tags":["report"]},{"url":"https://bugzilla.suse.com/1249798","tags":["report"]},{"url":"https://bugzilla.suse.com/1249799","tags":["report"]},{"url":"https://bugzilla.suse.com/1249802","tags":["report"]},{"url":"https://bugzilla.suse.com/1249803","tags":["report"]},{"url":"https://bugzilla.suse.com/1249810","tags":["report"]},{"url":"https://bugzilla.suse.com/1249867","tags":["report"]},{"url":"https://bugzilla.suse.com/1249871","tags":["report"]},{"url":"https://bugzilla.suse.com/1249872","tags":["report"]},{"url":"https://bugzilla.suse.com/1249877","tags":["report"]},{"url":"https://bugzilla.suse.com/1249882","tags":["report"]},{"url":"https://bugzilla.suse.com/1249912","tags":["report"]},{"url":"https://bugzilla.suse.com/1249920","tags":["report"]},{"url":"https://bugzilla.suse.com/1249922","tags":["report"]},{"url":"https://bugzilla.suse.com/1249925","tags":["report"]},{"url":"https://bugzilla.suse.com/1249927","tags":["report"]},{"url":"https://bugzilla.suse.com/1249936","tags":["report"]},{"url":"https://bugzilla.suse.com/1249944","tags":["report"]},{"url":"https://bugzilla.suse.com/1249951","tags":["report"]},{"url":"https://bugzilla.suse.com/1249958","tags":["report"]},{"url":"https://bugzilla.suse.com/1249981","tags":["report"]},{"url":"https://bugzilla.suse.com/1249991","tags":["report"]},{"url":"https://bugzilla.suse.com/1250018","tags":["report"]},{"url":"https://bugzilla.suse.com/1250023","tags":["report"]},{"url":"https://bugzilla.suse.com/1250043","tags":["report"]},{"url":"https://bugzilla.suse.com/1250044","tags":["report"]},{"url":"https://bugzilla.suse.com/1250045","tags":["report"]},{"url":"https://bugzilla.suse.com/1250052","tags":["report"]},{"url":"https://bugzilla.suse.com/1250071","tags":["report"]},{"url":"https://bugzilla.suse.com/1250072","tags":["report"]},{"url":"https://bugzilla.suse.com/1250081","tags":["report"]},{"url":"https://bugzilla.suse.com/1250084","tags":["report"]},{"url":"https://bugzilla.suse.com/1250104","tags":["report"]},{"url":"https://bugzilla.suse.com/1250114","tags":["report"]},{"url":"https://bugzilla.suse.com/1250121","tags":["report"]},{"url":"https://bugzilla.suse.com/1250155","tags":["report"]},{"url":"https://bugzilla.suse.com/1250165","tags":["report"]},{"url":"https://bugzilla.suse.com/1250168","tags":["report"]},{"url":"https://bugzilla.suse.com/1250250","tags":["report"]},{"url":"https://bugzilla.suse.com/1250324","tags":["report"]},{"url":"https://bugzilla.suse.com/1250328","tags":["report"]},{"url":"https://bugzilla.suse.com/1250363","tags":["report"]},{"url":"https://bugzilla.suse.com/1250393","tags":["report"]},{"url":"https://bugzilla.suse.com/1250792","tags":["report"]},{"url":"https://bugzilla.suse.com/1250818","tags":["report"]},{"url":"https://bugzilla.suse.com/1250851","tags":["report"]},{"url":"https://bugzilla.suse.com/1250856","tags":["report"]},{"url":"https://bugzilla.suse.com/1250879","tags":["report"]},{"url":"https://bugzilla.suse.com/1250915","tags":["report"]},{"url":"https://bugzilla.suse.com/1250963","tags":["report"]},{"url":"https://bugzilla.suse.com/1250965","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49975","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38665","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503615-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1193629","tags":["report"]},{"url":"https://bugzilla.suse.com/1205205","tags":["report"]},{"url":"https://bugzilla.suse.com/1206451","tags":["report"]},{"url":"https://bugzilla.suse.com/1206456","tags":["report"]},{"url":"https://bugzilla.suse.com/1206468","tags":["report"]},{"url":"https://bugzilla.suse.com/1206843","tags":["report"]},{"url":"https://bugzilla.suse.com/1207158","tags":["report"]},{"url":"https://bugzilla.suse.com/1207361","tags":["report"]},{"url":"https://bugzilla.suse.com/1207621","tags":["report"]},{"url":"https://bugzilla.suse.com/1207624","tags":["report"]},{"url":"https://bugzilla.suse.com/1207625","tags":["report"]},{"url":"https://bugzilla.suse.com/1207628","tags":["report"]},{"url":"https://bugzilla.suse.com/1207631","tags":["report"]},{"url":"https://bugzilla.suse.com/1207645","tags":["report"]},{"url":"https://bugzilla.suse.com/1207651","tags":["report"]},{"url":"https://bugzilla.suse.com/1208607","tags":["report"]},{"url":"https://bugzilla.suse.com/1209980","tags":["report"]},{"url":"https://bugzilla.suse.com/1212603","tags":["report"]},{"url":"https://bugzilla.suse.com/1213099","tags":["report"]},{"url":"https://bugzilla.suse.com/1213104","tags":["report"]},{"url":"https://bugzilla.suse.com/1213533","tags":["report"]},{"url":"https://bugzilla.suse.com/1215911","tags":["report"]},{"url":"https://bugzilla.suse.com/1217790","tags":["report"]},{"url":"https://bugzilla.suse.com/1223959","tags":["report"]},{"url":"https://bugzilla.suse.com/1234639","tags":["report"]},{"url":"https://bugzilla.suse.com/1236104","tags":["report"]},{"url":"https://bugzilla.suse.com/1238160","tags":["report"]},{"url":"https://bugzilla.suse.com/1242846","tags":["report"]},{"url":"https://bugzilla.suse.com/1243539","tags":["report"]},{"url":"https://bugzilla.suse.com/1244732","tags":["report"]},{"url":"https://bugzilla.suse.com/1245666","tags":["report"]},{"url":"https://bugzilla.suse.com/1247028","tags":["report"]},{"url":"https://bugzilla.suse.com/1249158","tags":["report"]},{"url":"https://bugzilla.suse.com/1249638","tags":["report"]},{"url":"https://bugzilla.suse.com/1249639","tags":["report"]},{"url":"https://bugzilla.suse.com/1249648","tags":["report"]},{"url":"https://bugzilla.suse.com/1249650","tags":["report"]},{"url":"https://bugzilla.suse.com/1249651","tags":["report"]},{"url":"https://bugzilla.suse.com/1249661","tags":["report"]},{"url":"https://bugzilla.suse.com/1249669","tags":["report"]},{"url":"https://bugzilla.suse.com/1249681","tags":["report"]},{"url":"https://bugzilla.suse.com/1249685","tags":["report"]},{"url":"https://bugzilla.suse.com/1249695","tags":["report"]},{"url":"https://bugzilla.suse.com/1249699","tags":["report"]},{"url":"https://bugzilla.suse.com/1249701","tags":["report"]},{"url":"https://bugzilla.suse.com/1249704","tags":["report"]},{"url":"https://bugzilla.suse.com/1249705","tags":["report"]},{"url":"https://bugzilla.suse.com/1249708","tags":["report"]},{"url":"https://bugzilla.suse.com/1249709","tags":["report"]},{"url":"https://bugzilla.suse.com/1249722","tags":["report"]},{"url":"https://bugzilla.suse.com/1249733","tags":["report"]},{"url":"https://bugzilla.suse.com/1249741","tags":["report"]},{"url":"https://bugzilla.suse.com/1249742","tags":["report"]},{"url":"https://bugzilla.suse.com/1249745","tags":["report"]},{"url":"https://bugzilla.suse.com/1249746","tags":["report"]},{"url":"https://bugzilla.suse.com/1249749","tags":["report"]},{"url":"https://bugzilla.suse.com/1249750","tags":["report"]},{"url":"https://bugzilla.suse.com/1249751","tags":["report"]},{"url":"https://bugzilla.suse.com/1249753","tags":["report"]},{"url":"https://bugzilla.suse.com/1249757","tags":["report"]},{"url":"https://bugzilla.suse.com/1249767","tags":["report"]},{"url":"https://bugzilla.suse.com/1249777","tags":["report"]},{"url":"https://bugzilla.suse.com/1249781","tags":["report"]},{"url":"https://bugzilla.suse.com/1249782","tags":["report"]},{"url":"https://bugzilla.suse.com/1249784","tags":["report"]},{"url":"https://bugzilla.suse.com/1249791","tags":["report"]},{"url":"https://bugzilla.suse.com/1249800","tags":["report"]},{"url":"https://bugzilla.suse.com/1249816","tags":["report"]},{"url":"https://bugzilla.suse.com/1249836","tags":["report"]},{"url":"https://bugzilla.suse.com/1249844","tags":["report"]},{"url":"https://bugzilla.suse.com/1249858","tags":["report"]},{"url":"https://bugzilla.suse.com/1249860","tags":["report"]},{"url":"https://bugzilla.suse.com/1249868","tags":["report"]},{"url":"https://bugzilla.suse.com/1249874","tags":["report"]},{"url":"https://bugzilla.suse.com/1249884","tags":["report"]},{"url":"https://bugzilla.suse.com/1249890","tags":["report"]},{"url":"https://bugzilla.suse.com/1249892","tags":["report"]},{"url":"https://bugzilla.suse.com/1249910","tags":["report"]},{"url":"https://bugzilla.suse.com/1249913","tags":["report"]},{"url":"https://bugzilla.suse.com/1249914","tags":["report"]},{"url":"https://bugzilla.suse.com/1249924","tags":["report"]},{"url":"https://bugzilla.suse.com/1249928","tags":["report"]},{"url":"https://bugzilla.suse.com/1249933","tags":["report"]},{"url":"https://bugzilla.suse.com/1249934","tags":["report"]},{"url":"https://bugzilla.suse.com/1249939","tags":["report"]},{"url":"https://bugzilla.suse.com/1249940","tags":["report"]},{"url":"https://bugzilla.suse.com/1249954","tags":["report"]},{"url":"https://bugzilla.suse.com/1250006","tags":["report"]},{"url":"https://bugzilla.suse.com/1250010","tags":["report"]},{"url":"https://bugzilla.suse.com/1250011","tags":["report"]},{"url":"https://bugzilla.suse.com/1250015","tags":["report"]},{"url":"https://bugzilla.suse.com/1250017","tags":["report"]},{"url":"https://bugzilla.suse.com/1250026","tags":["report"]},{"url":"https://bugzilla.suse.com/1250037","tags":["report"]},{"url":"https://bugzilla.suse.com/1250039","tags":["report"]},{"url":"https://bugzilla.suse.com/1250040","tags":["report"]},{"url":"https://bugzilla.suse.com/1250042","tags":["report"]},{"url":"https://bugzilla.suse.com/1250047","tags":["report"]},{"url":"https://bugzilla.suse.com/1250060","tags":["report"]},{"url":"https://bugzilla.suse.com/1250068","tags":["report"]},{"url":"https://bugzilla.suse.com/1250075","tags":["report"]},{"url":"https://bugzilla.suse.com/1250077","tags":["report"]},{"url":"https://bugzilla.suse.com/1250080","tags":["report"]},{"url":"https://bugzilla.suse.com/1250083","tags":["report"]},{"url":"https://bugzilla.suse.com/1250103","tags":["report"]},{"url":"https://bugzilla.suse.com/1250105","tags":["report"]},{"url":"https://bugzilla.suse.com/1250107","tags":["report"]},{"url":"https://bugzilla.suse.com/1250108","tags":["report"]},{"url":"https://bugzilla.suse.com/1250118","tags":["report"]},{"url":"https://bugzilla.suse.com/1250130","tags":["report"]},{"url":"https://bugzilla.suse.com/1250134","tags":["report"]},{"url":"https://bugzilla.suse.com/1250137","tags":["report"]},{"url":"https://bugzilla.suse.com/1250138","tags":["report"]},{"url":"https://bugzilla.suse.com/1250144","tags":["report"]},{"url":"https://bugzilla.suse.com/1250151","tags":["report"]},{"url":"https://bugzilla.suse.com/1250153","tags":["report"]},{"url":"https://bugzilla.suse.com/1250159","tags":["report"]},{"url":"https://bugzilla.suse.com/1250178","tags":["report"]},{"url":"https://bugzilla.suse.com/1250181","tags":["report"]},{"url":"https://bugzilla.suse.com/1250182","tags":["report"]},{"url":"https://bugzilla.suse.com/1250184","tags":["report"]},{"url":"https://bugzilla.suse.com/1250189","tags":["report"]},{"url":"https://bugzilla.suse.com/1250191","tags":["report"]},{"url":"https://bugzilla.suse.com/1250197","tags":["report"]},{"url":"https://bugzilla.suse.com/1250200","tags":["report"]},{"url":"https://bugzilla.suse.com/1250209","tags":["report"]},{"url":"https://bugzilla.suse.com/1250211","tags":["report"]},{"url":"https://bugzilla.suse.com/1250215","tags":["report"]},{"url":"https://bugzilla.suse.com/1250245","tags":["report"]},{"url":"https://bugzilla.suse.com/1250264","tags":["report"]},{"url":"https://bugzilla.suse.com/1250278","tags":["report"]},{"url":"https://bugzilla.suse.com/1250285","tags":["report"]},{"url":"https://bugzilla.suse.com/1250287","tags":["report"]},{"url":"https://bugzilla.suse.com/1250293","tags":["report"]},{"url":"https://bugzilla.suse.com/1250303","tags":["report"]},{"url":"https://bugzilla.suse.com/1250306","tags":["report"]},{"url":"https://bugzilla.suse.com/1250309","tags":["report"]},{"url":"https://bugzilla.suse.com/1250311","tags":["report"]},{"url":"https://bugzilla.suse.com/1250315","tags":["report"]},{"url":"https://bugzilla.suse.com/1250316","tags":["report"]},{"url":"https://bugzilla.suse.com/1250322","tags":["report"]},{"url":"https://bugzilla.suse.com/1250327","tags":["report"]},{"url":"https://bugzilla.suse.com/1250331","tags":["report"]},{"url":"https://bugzilla.suse.com/1250362","tags":["report"]},{"url":"https://bugzilla.suse.com/1250370","tags":["report"]},{"url":"https://bugzilla.suse.com/1250374","tags":["report"]},{"url":"https://bugzilla.suse.com/1250412","tags":["report"]},{"url":"https://bugzilla.suse.com/1250418","tags":["report"]},{"url":"https://bugzilla.suse.com/1250425","tags":["report"]},{"url":"https://bugzilla.suse.com/1250428","tags":["report"]},{"url":"https://bugzilla.suse.com/1250453","tags":["report"]},{"url":"https://bugzilla.suse.com/1250454","tags":["report"]},{"url":"https://bugzilla.suse.com/1250457","tags":["report"]},{"url":"https://bugzilla.suse.com/1250761","tags":["report"]},{"url":"https://bugzilla.suse.com/1250762","tags":["report"]},{"url":"https://bugzilla.suse.com/1250768","tags":["report"]},{"url":"https://bugzilla.suse.com/1250771","tags":["report"]},{"url":"https://bugzilla.suse.com/1250781","tags":["report"]},{"url":"https://bugzilla.suse.com/1250784","tags":["report"]},{"url":"https://bugzilla.suse.com/1250786","tags":["report"]},{"url":"https://bugzilla.suse.com/1250791","tags":["report"]},{"url":"https://bugzilla.suse.com/1250793","tags":["report"]},{"url":"https://bugzilla.suse.com/1250810","tags":["report"]},{"url":"https://bugzilla.suse.com/1250811","tags":["report"]},{"url":"https://bugzilla.suse.com/1250814","tags":["report"]},{"url":"https://bugzilla.suse.com/1250819","tags":["report"]},{"url":"https://bugzilla.suse.com/1250822","tags":["report"]},{"url":"https://bugzilla.suse.com/1250824","tags":["report"]},{"url":"https://bugzilla.suse.com/1250829","tags":["report"]},{"url":"https://bugzilla.suse.com/1250832","tags":["report"]},{"url":"https://bugzilla.suse.com/1250839","tags":["report"]},{"url":"https://bugzilla.suse.com/1250842","tags":["report"]},{"url":"https://bugzilla.suse.com/1250843","tags":["report"]},{"url":"https://bugzilla.suse.com/1250846","tags":["report"]},{"url":"https://bugzilla.suse.com/1250848","tags":["report"]},{"url":"https://bugzilla.suse.com/1250849","tags":["report"]},{"url":"https://bugzilla.suse.com/1250862","tags":["report"]},{"url":"https://bugzilla.suse.com/1250864","tags":["report"]},{"url":"https://bugzilla.suse.com/1250866","tags":["report"]},{"url":"https://bugzilla.suse.com/1250874","tags":["report"]},{"url":"https://bugzilla.suse.com/1250875","tags":["report"]},{"url":"https://bugzilla.suse.com/1250877","tags":["report"]},{"url":"https://bugzilla.suse.com/1250881","tags":["report"]},{"url":"https://bugzilla.suse.com/1250883","tags":["report"]},{"url":"https://bugzilla.suse.com/1250887","tags":["report"]},{"url":"https://bugzilla.suse.com/1250888","tags":["report"]},{"url":"https://bugzilla.suse.com/1250889","tags":["report"]},{"url":"https://bugzilla.suse.com/1250913","tags":["report"]},{"url":"https://bugzilla.suse.com/1250927","tags":["report"]},{"url":"https://bugzilla.suse.com/1250932","tags":["report"]},{"url":"https://bugzilla.suse.com/1250948","tags":["report"]},{"url":"https://bugzilla.suse.com/1250953","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53431","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38380","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503626-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1233640","tags":["report"]},{"url":"https://bugzilla.suse.com/1244729","tags":["report"]},{"url":"https://bugzilla.suse.com/1245963","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38216","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503628-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1242573","tags":["report"]},{"url":"https://bugzilla.suse.com/1242960","tags":["report"]},{"url":"https://bugzilla.suse.com/1245498","tags":["report"]},{"url":"https://bugzilla.suse.com/1245499","tags":["report"]},{"url":"https://bugzilla.suse.com/1247288","tags":["report"]},{"url":"https://bugzilla.suse.com/1247317","tags":["report"]},{"url":"https://bugzilla.suse.com/1249691","tags":["report"]},{"url":"https://bugzilla.suse.com/1250237","tags":["report"]},{"url":"https://bugzilla.suse.com/1250955","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-23155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38476","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202503634-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1213545","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1221858","tags":["report"]},{"url":"https://bugzilla.suse.com/1222323","tags":["report"]},{"url":"https://bugzilla.suse.com/1230557","tags":["report"]},{"url":"https://bugzilla.suse.com/1230708","tags":["report"]},{"url":"https://bugzilla.suse.com/1233120","tags":["report"]},{"url":"https://bugzilla.suse.com/1234156","tags":["report"]},{"url":"https://bugzilla.suse.com/1240708","tags":["report"]},{"url":"https://bugzilla.suse.com/1240890","tags":["report"]},{"url":"https://bugzilla.suse.com/1242034","tags":["report"]},{"url":"https://bugzilla.suse.com/1242754","tags":["report"]},{"url":"https://bugzilla.suse.com/1244734","tags":["report"]},{"url":"https://bugzilla.suse.com/1244930","tags":["report"]},{"url":"https://bugzilla.suse.com/1245663","tags":["report"]},{"url":"https://bugzilla.suse.com/1245710","tags":["report"]},{"url":"https://bugzilla.suse.com/1245767","tags":["report"]},{"url":"https://bugzilla.suse.com/1245780","tags":["report"]},{"url":"https://bugzilla.suse.com/1245815","tags":["report"]},{"url":"https://bugzilla.suse.com/1245973","tags":["report"]},{"url":"https://bugzilla.suse.com/1245977","tags":["report"]},{"url":"https://bugzilla.suse.com/1246005","tags":["report"]},{"url":"https://bugzilla.suse.com/1246012","tags":["report"]},{"url":"https://bugzilla.suse.com/1246181","tags":["report"]},{"url":"https://bugzilla.suse.com/1246193","tags":["report"]},{"url":"https://bugzilla.suse.com/1247057","tags":["report"]},{"url":"https://bugzilla.suse.com/1247078","tags":["report"]},{"url":"https://bugzilla.suse.com/1247112","tags":["report"]},{"url":"https://bugzilla.suse.com/1247116","tags":["report"]},{"url":"https://bugzilla.suse.com/1247119","tags":["report"]},{"url":"https://bugzilla.suse.com/1247155","tags":["report"]},{"url":"https://bugzilla.suse.com/1247162","tags":["report"]},{"url":"https://bugzilla.suse.com/1247167","tags":["report"]},{"url":"https://bugzilla.suse.com/1247229","tags":["report"]},{"url":"https://bugzilla.suse.com/1247243","tags":["report"]},{"url":"https://bugzilla.suse.com/1247280","tags":["report"]},{"url":"https://bugzilla.suse.com/1247313","tags":["report"]},{"url":"https://bugzilla.suse.com/1247712","tags":["report"]},{"url":"https://bugzilla.suse.com/1247976","tags":["report"]},{"url":"https://bugzilla.suse.com/1248088","tags":["report"]},{"url":"https://bugzilla.suse.com/1248164","tags":["report"]},{"url":"https://bugzilla.suse.com/1248166","tags":["report"]},{"url":"https://bugzilla.suse.com/1248178","tags":["report"]},{"url":"https://bugzilla.suse.com/1248179","tags":["report"]},{"url":"https://bugzilla.suse.com/1248180","tags":["report"]},{"url":"https://bugzilla.suse.com/1248183","tags":["report"]},{"url":"https://bugzilla.suse.com/1248186","tags":["report"]},{"url":"https://bugzilla.suse.com/1248194","tags":["report"]},{"url":"https://bugzilla.suse.com/1248196","tags":["report"]},{"url":"https://bugzilla.suse.com/1248198","tags":["report"]},{"url":"https://bugzilla.suse.com/1248205","tags":["report"]},{"url":"https://bugzilla.suse.com/1248206","tags":["report"]},{"url":"https://bugzilla.suse.com/1248208","tags":["report"]},{"url":"https://bugzilla.suse.com/1248209","tags":["report"]},{"url":"https://bugzilla.suse.com/1248212","tags":["report"]},{"url":"https://bugzilla.suse.com/1248213","tags":["report"]},{"url":"https://bugzilla.suse.com/1248214","tags":["report"]},{"url":"https://bugzilla.suse.com/1248216","tags":["report"]},{"url":"https://bugzilla.suse.com/1248217","tags":["report"]},{"url":"https://bugzilla.suse.com/1248223","tags":["report"]},{"url":"https://bugzilla.suse.com/1248227","tags":["report"]},{"url":"https://bugzilla.suse.com/1248228","tags":["report"]},{"url":"https://bugzilla.suse.com/1248229","tags":["report"]},{"url":"https://bugzilla.suse.com/1248297","tags":["report"]},{"url":"https://bugzilla.suse.com/1248306","tags":["report"]},{"url":"https://bugzilla.suse.com/1248312","tags":["report"]},{"url":"https://bugzilla.suse.com/1248337","tags":["report"]},{"url":"https://bugzilla.suse.com/1248338","tags":["report"]},{"url":"https://bugzilla.suse.com/1248340","tags":["report"]},{"url":"https://bugzilla.suse.com/1248345","tags":["report"]},{"url":"https://bugzilla.suse.com/1248349","tags":["report"]},{"url":"https://bugzilla.suse.com/1248350","tags":["report"]},{"url":"https://bugzilla.suse.com/1248354","tags":["report"]},{"url":"https://bugzilla.suse.com/1248355","tags":["report"]},{"url":"https://bugzilla.suse.com/1248361","tags":["report"]},{"url":"https://bugzilla.suse.com/1248363","tags":["report"]},{"url":"https://bugzilla.suse.com/1248368","tags":["report"]},{"url":"https://bugzilla.suse.com/1248374","tags":["report"]},{"url":"https://bugzilla.suse.com/1248377","tags":["report"]},{"url":"https://bugzilla.suse.com/1248386","tags":["report"]},{"url":"https://bugzilla.suse.com/1248390","tags":["report"]},{"url":"https://bugzilla.suse.com/1248395","tags":["report"]},{"url":"https://bugzilla.suse.com/1248401","tags":["report"]},{"url":"https://bugzilla.suse.com/1248511","tags":["report"]},{"url":"https://bugzilla.suse.com/1248573","tags":["report"]},{"url":"https://bugzilla.suse.com/1248575","tags":["report"]},{"url":"https://bugzilla.suse.com/1248577","tags":["report"]},{"url":"https://bugzilla.suse.com/1248609","tags":["report"]},{"url":"https://bugzilla.suse.com/1248614","tags":["report"]},{"url":"https://bugzilla.suse.com/1248621","tags":["report"]},{"url":"https://bugzilla.suse.com/1248636","tags":["report"]},{"url":"https://bugzilla.suse.com/1248643","tags":["report"]},{"url":"https://bugzilla.suse.com/1248652","tags":["report"]},{"url":"https://bugzilla.suse.com/1248655","tags":["report"]},{"url":"https://bugzilla.suse.com/1248666","tags":["report"]},{"url":"https://bugzilla.suse.com/1248746","tags":["report"]},{"url":"https://bugzilla.suse.com/1248748","tags":["report"]},{"url":"https://bugzilla.suse.com/1249022","tags":["report"]},{"url":"https://bugzilla.suse.com/1249481","tags":["report"]},{"url":"https://bugzilla.suse.com/1250169","tags":["report"]},{"url":"https://bugzilla.suse.com/1250205","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-46733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38520","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38634","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39828","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520851-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520861-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520870-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202520898-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20253716-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20253751-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20253761-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1249353","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254057-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1214954","tags":["report"]},{"url":"https://bugzilla.suse.com/1215143","tags":["report"]},{"url":"https://bugzilla.suse.com/1216396","tags":["report"]},{"url":"https://bugzilla.suse.com/1239206","tags":["report"]},{"url":"https://bugzilla.suse.com/1244939","tags":["report"]},{"url":"https://bugzilla.suse.com/1247222","tags":["report"]},{"url":"https://bugzilla.suse.com/1247683","tags":["report"]},{"url":"https://bugzilla.suse.com/1248211","tags":["report"]},{"url":"https://bugzilla.suse.com/1248230","tags":["report"]},{"url":"https://bugzilla.suse.com/1248517","tags":["report"]},{"url":"https://bugzilla.suse.com/1248630","tags":["report"]},{"url":"https://bugzilla.suse.com/1248754","tags":["report"]},{"url":"https://bugzilla.suse.com/1248886","tags":["report"]},{"url":"https://bugzilla.suse.com/1249161","tags":["report"]},{"url":"https://bugzilla.suse.com/1249182","tags":["report"]},{"url":"https://bugzilla.suse.com/1249224","tags":["report"]},{"url":"https://bugzilla.suse.com/1249286","tags":["report"]},{"url":"https://bugzilla.suse.com/1249302","tags":["report"]},{"url":"https://bugzilla.suse.com/1249317","tags":["report"]},{"url":"https://bugzilla.suse.com/1249319","tags":["report"]},{"url":"https://bugzilla.suse.com/1249320","tags":["report"]},{"url":"https://bugzilla.suse.com/1249397","tags":["report"]},{"url":"https://bugzilla.suse.com/1249512","tags":["report"]},{"url":"https://bugzilla.suse.com/1249595","tags":["report"]},{"url":"https://bugzilla.suse.com/1249735","tags":["report"]},{"url":"https://bugzilla.suse.com/1250032","tags":["report"]},{"url":"https://bugzilla.suse.com/1250119","tags":["report"]},{"url":"https://bugzilla.suse.com/1250202","tags":["report"]},{"url":"https://bugzilla.suse.com/1250274","tags":["report"]},{"url":"https://bugzilla.suse.com/1250296","tags":["report"]},{"url":"https://bugzilla.suse.com/1250379","tags":["report"]},{"url":"https://bugzilla.suse.com/1250400","tags":["report"]},{"url":"https://bugzilla.suse.com/1250455","tags":["report"]},{"url":"https://bugzilla.suse.com/1250491","tags":["report"]},{"url":"https://bugzilla.suse.com/1250650","tags":["report"]},{"url":"https://bugzilla.suse.com/1250702","tags":["report"]},{"url":"https://bugzilla.suse.com/1250704","tags":["report"]},{"url":"https://bugzilla.suse.com/1250721","tags":["report"]},{"url":"https://bugzilla.suse.com/1250742","tags":["report"]},{"url":"https://bugzilla.suse.com/1250758","tags":["report"]},{"url":"https://bugzilla.suse.com/1250946","tags":["report"]},{"url":"https://bugzilla.suse.com/1251024","tags":["report"]},{"url":"https://bugzilla.suse.com/1251027","tags":["report"]},{"url":"https://bugzilla.suse.com/1251028","tags":["report"]},{"url":"https://bugzilla.suse.com/1251031","tags":["report"]},{"url":"https://bugzilla.suse.com/1251035","tags":["report"]},{"url":"https://bugzilla.suse.com/1251038","tags":["report"]},{"url":"https://bugzilla.suse.com/1251043","tags":["report"]},{"url":"https://bugzilla.suse.com/1251045","tags":["report"]},{"url":"https://bugzilla.suse.com/1251052","tags":["report"]},{"url":"https://bugzilla.suse.com/1251053","tags":["report"]},{"url":"https://bugzilla.suse.com/1251054","tags":["report"]},{"url":"https://bugzilla.suse.com/1251056","tags":["report"]},{"url":"https://bugzilla.suse.com/1251057","tags":["report"]},{"url":"https://bugzilla.suse.com/1251059","tags":["report"]},{"url":"https://bugzilla.suse.com/1251060","tags":["report"]},{"url":"https://bugzilla.suse.com/1251065","tags":["report"]},{"url":"https://bugzilla.suse.com/1251066","tags":["report"]},{"url":"https://bugzilla.suse.com/1251067","tags":["report"]},{"url":"https://bugzilla.suse.com/1251068","tags":["report"]},{"url":"https://bugzilla.suse.com/1251071","tags":["report"]},{"url":"https://bugzilla.suse.com/1251076","tags":["report"]},{"url":"https://bugzilla.suse.com/1251079","tags":["report"]},{"url":"https://bugzilla.suse.com/1251081","tags":["report"]},{"url":"https://bugzilla.suse.com/1251083","tags":["report"]},{"url":"https://bugzilla.suse.com/1251084","tags":["report"]},{"url":"https://bugzilla.suse.com/1251100","tags":["report"]},{"url":"https://bugzilla.suse.com/1251105","tags":["report"]},{"url":"https://bugzilla.suse.com/1251106","tags":["report"]},{"url":"https://bugzilla.suse.com/1251108","tags":["report"]},{"url":"https://bugzilla.suse.com/1251113","tags":["report"]},{"url":"https://bugzilla.suse.com/1251114","tags":["report"]},{"url":"https://bugzilla.suse.com/1251119","tags":["report"]},{"url":"https://bugzilla.suse.com/1251123","tags":["report"]},{"url":"https://bugzilla.suse.com/1251126","tags":["report"]},{"url":"https://bugzilla.suse.com/1251132","tags":["report"]},{"url":"https://bugzilla.suse.com/1251134","tags":["report"]},{"url":"https://bugzilla.suse.com/1251143","tags":["report"]},{"url":"https://bugzilla.suse.com/1251146","tags":["report"]},{"url":"https://bugzilla.suse.com/1251150","tags":["report"]},{"url":"https://bugzilla.suse.com/1251152","tags":["report"]},{"url":"https://bugzilla.suse.com/1251153","tags":["report"]},{"url":"https://bugzilla.suse.com/1251159","tags":["report"]},{"url":"https://bugzilla.suse.com/1251161","tags":["report"]},{"url":"https://bugzilla.suse.com/1251170","tags":["report"]},{"url":"https://bugzilla.suse.com/1251177","tags":["report"]},{"url":"https://bugzilla.suse.com/1251180","tags":["report"]},{"url":"https://bugzilla.suse.com/1251206","tags":["report"]},{"url":"https://bugzilla.suse.com/1251215","tags":["report"]},{"url":"https://bugzilla.suse.com/1251216","tags":["report"]},{"url":"https://bugzilla.suse.com/1251222","tags":["report"]},{"url":"https://bugzilla.suse.com/1251230","tags":["report"]},{"url":"https://bugzilla.suse.com/1251232","tags":["report"]},{"url":"https://bugzilla.suse.com/1251233","tags":["report"]},{"url":"https://bugzilla.suse.com/1251247","tags":["report"]},{"url":"https://bugzilla.suse.com/1251268","tags":["report"]},{"url":"https://bugzilla.suse.com/1251269","tags":["report"]},{"url":"https://bugzilla.suse.com/1251270","tags":["report"]},{"url":"https://bugzilla.suse.com/1251282","tags":["report"]},{"url":"https://bugzilla.suse.com/1251283","tags":["report"]},{"url":"https://bugzilla.suse.com/1251286","tags":["report"]},{"url":"https://bugzilla.suse.com/1251290","tags":["report"]},{"url":"https://bugzilla.suse.com/1251319","tags":["report"]},{"url":"https://bugzilla.suse.com/1251321","tags":["report"]},{"url":"https://bugzilla.suse.com/1251323","tags":["report"]},{"url":"https://bugzilla.suse.com/1251328","tags":["report"]},{"url":"https://bugzilla.suse.com/1251529","tags":["report"]},{"url":"https://bugzilla.suse.com/1251721","tags":["report"]},{"url":"https://bugzilla.suse.com/1251732","tags":["report"]},{"url":"https://bugzilla.suse.com/1251742","tags":["report"]},{"url":"https://bugzilla.suse.com/1251743","tags":["report"]},{"url":"https://bugzilla.suse.com/1251746","tags":["report"]},{"url":"https://bugzilla.suse.com/1251748","tags":["report"]},{"url":"https://bugzilla.suse.com/1251749","tags":["report"]},{"url":"https://bugzilla.suse.com/1251750","tags":["report"]},{"url":"https://bugzilla.suse.com/1251754","tags":["report"]},{"url":"https://bugzilla.suse.com/1251755","tags":["report"]},{"url":"https://bugzilla.suse.com/1251756","tags":["report"]},{"url":"https://bugzilla.suse.com/1251758","tags":["report"]},{"url":"https://bugzilla.suse.com/1251759","tags":["report"]},{"url":"https://bugzilla.suse.com/1251760","tags":["report"]},{"url":"https://bugzilla.suse.com/1251762","tags":["report"]},{"url":"https://bugzilla.suse.com/1251763","tags":["report"]},{"url":"https://bugzilla.suse.com/1251764","tags":["report"]},{"url":"https://bugzilla.suse.com/1251769","tags":["report"]},{"url":"https://bugzilla.suse.com/1251771","tags":["report"]},{"url":"https://bugzilla.suse.com/1251772","tags":["report"]},{"url":"https://bugzilla.suse.com/1251777","tags":["report"]},{"url":"https://bugzilla.suse.com/1251780","tags":["report"]},{"url":"https://bugzilla.suse.com/1251804","tags":["report"]},{"url":"https://bugzilla.suse.com/1251810","tags":["report"]},{"url":"https://bugzilla.suse.com/1251930","tags":["report"]},{"url":"https://bugzilla.suse.com/1251967","tags":["report"]},{"url":"https://bugzilla.suse.com/1252033","tags":["report"]},{"url":"https://bugzilla.suse.com/1252035","tags":["report"]},{"url":"https://bugzilla.suse.com/1252039","tags":["report"]},{"url":"https://bugzilla.suse.com/1252044","tags":["report"]},{"url":"https://bugzilla.suse.com/1252047","tags":["report"]},{"url":"https://bugzilla.suse.com/1252051","tags":["report"]},{"url":"https://bugzilla.suse.com/1252052","tags":["report"]},{"url":"https://bugzilla.suse.com/1252056","tags":["report"]},{"url":"https://bugzilla.suse.com/1252060","tags":["report"]},{"url":"https://bugzilla.suse.com/1252062","tags":["report"]},{"url":"https://bugzilla.suse.com/1252064","tags":["report"]},{"url":"https://bugzilla.suse.com/1252065","tags":["report"]},{"url":"https://bugzilla.suse.com/1252069","tags":["report"]},{"url":"https://bugzilla.suse.com/1252070","tags":["report"]},{"url":"https://bugzilla.suse.com/1252072","tags":["report"]},{"url":"https://bugzilla.suse.com/1252074","tags":["report"]},{"url":"https://bugzilla.suse.com/1252075","tags":["report"]},{"url":"https://bugzilla.suse.com/1252078","tags":["report"]},{"url":"https://bugzilla.suse.com/1252079","tags":["report"]},{"url":"https://bugzilla.suse.com/1252081","tags":["report"]},{"url":"https://bugzilla.suse.com/1252082","tags":["report"]},{"url":"https://bugzilla.suse.com/1252083","tags":["report"]},{"url":"https://bugzilla.suse.com/1252236","tags":["report"]},{"url":"https://bugzilla.suse.com/1252253","tags":["report"]},{"url":"https://bugzilla.suse.com/1252265","tags":["report"]},{"url":"https://bugzilla.suse.com/1252330","tags":["report"]},{"url":"https://bugzilla.suse.com/1252332","tags":["report"]},{"url":"https://bugzilla.suse.com/1252336","tags":["report"]},{"url":"https://bugzilla.suse.com/1252346","tags":["report"]},{"url":"https://bugzilla.suse.com/1252348","tags":["report"]},{"url":"https://bugzilla.suse.com/1252349","tags":["report"]},{"url":"https://bugzilla.suse.com/1252364","tags":["report"]},{"url":"https://bugzilla.suse.com/1252469","tags":["report"]},{"url":"https://bugzilla.suse.com/1252479","tags":["report"]},{"url":"https://bugzilla.suse.com/1252481","tags":["report"]},{"url":"https://bugzilla.suse.com/1252489","tags":["report"]},{"url":"https://bugzilla.suse.com/1252490","tags":["report"]},{"url":"https://bugzilla.suse.com/1252492","tags":["report"]},{"url":"https://bugzilla.suse.com/1252495","tags":["report"]},{"url":"https://bugzilla.suse.com/1252496","tags":["report"]},{"url":"https://bugzilla.suse.com/1252499","tags":["report"]},{"url":"https://bugzilla.suse.com/1252534","tags":["report"]},{"url":"https://bugzilla.suse.com/1252536","tags":["report"]},{"url":"https://bugzilla.suse.com/1252537","tags":["report"]},{"url":"https://bugzilla.suse.com/1252550","tags":["report"]},{"url":"https://bugzilla.suse.com/1252553","tags":["report"]},{"url":"https://bugzilla.suse.com/1252559","tags":["report"]},{"url":"https://bugzilla.suse.com/1252561","tags":["report"]},{"url":"https://bugzilla.suse.com/1252564","tags":["report"]},{"url":"https://bugzilla.suse.com/1252565","tags":["report"]},{"url":"https://bugzilla.suse.com/1252566","tags":["report"]},{"url":"https://bugzilla.suse.com/1252632","tags":["report"]},{"url":"https://bugzilla.suse.com/1252668","tags":["report"]},{"url":"https://bugzilla.suse.com/1252678","tags":["report"]},{"url":"https://bugzilla.suse.com/1252679","tags":["report"]},{"url":"https://bugzilla.suse.com/1252685","tags":["report"]},{"url":"https://bugzilla.suse.com/1252688","tags":["report"]},{"url":"https://bugzilla.suse.com/1252734","tags":["report"]},{"url":"https://bugzilla.suse.com/1252735","tags":["report"]},{"url":"https://bugzilla.suse.com/1252772","tags":["report"]},{"url":"https://bugzilla.suse.com/1252775","tags":["report"]},{"url":"https://bugzilla.suse.com/1252785","tags":["report"]},{"url":"https://bugzilla.suse.com/1252787","tags":["report"]},{"url":"https://bugzilla.suse.com/1252789","tags":["report"]},{"url":"https://bugzilla.suse.com/1252797","tags":["report"]},{"url":"https://bugzilla.suse.com/1252819","tags":["report"]},{"url":"https://bugzilla.suse.com/1252822","tags":["report"]},{"url":"https://bugzilla.suse.com/1252826","tags":["report"]},{"url":"https://bugzilla.suse.com/1252841","tags":["report"]},{"url":"https://bugzilla.suse.com/1252848","tags":["report"]},{"url":"https://bugzilla.suse.com/1252849","tags":["report"]},{"url":"https://bugzilla.suse.com/1252850","tags":["report"]},{"url":"https://bugzilla.suse.com/1252851","tags":["report"]},{"url":"https://bugzilla.suse.com/1252854","tags":["report"]},{"url":"https://bugzilla.suse.com/1252858","tags":["report"]},{"url":"https://bugzilla.suse.com/1252865","tags":["report"]},{"url":"https://bugzilla.suse.com/1252866","tags":["report"]},{"url":"https://bugzilla.suse.com/1252873","tags":["report"]},{"url":"https://bugzilla.suse.com/1252902","tags":["report"]},{"url":"https://bugzilla.suse.com/1252904","tags":["report"]},{"url":"https://bugzilla.suse.com/1252909","tags":["report"]},{"url":"https://bugzilla.suse.com/1252915","tags":["report"]},{"url":"https://bugzilla.suse.com/1252918","tags":["report"]},{"url":"https://bugzilla.suse.com/1252921","tags":["report"]},{"url":"https://bugzilla.suse.com/1252939","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53611","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53617","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53633","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39947","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39957","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40104","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254132-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1252774","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40080","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254141-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-20254315-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1078788","tags":["report"]},{"url":"https://bugzilla.suse.com/1244824","tags":["report"]},{"url":"https://bugzilla.suse.com/1246911","tags":["report"]},{"url":"https://bugzilla.suse.com/1247374","tags":["report"]},{"url":"https://bugzilla.suse.com/1252554","tags":["report"]},{"url":"https://bugzilla.suse.com/963449","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38498","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2025-38713","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-38713","tags":["report"]},{"url":"https://git.kernel.org/linus/94458781aee6045bd3d0ad4b80b02886b9e2219b","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7909-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7909-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7909-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7910-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7909-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7910-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7933-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7909-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7938-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8031-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8052-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-7","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8028-8","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8052-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8074-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8074-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8126-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-50070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-50327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38470","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-38487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38488","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-38497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38502","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-38535","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-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38550","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-38563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38569","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-38583","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-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38614","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-38630","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-38645","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-38663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38666","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-38676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38691","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-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-38711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38712","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-38718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38721","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-38729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38732","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-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-39693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39697","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-39709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39710","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-39724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39730","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-39742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39752","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-39760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39766","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-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-39798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39808","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-39817","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-39828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39835","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-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-39853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39860","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-39891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-52593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-26896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40018","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-37927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-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-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-38166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-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-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-38469","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-38485","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-38496","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-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-38537","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-38549","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-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38610","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-38625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38632","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-38646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38648","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-38665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38692","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-38710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38730","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-39679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-39711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39712","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-39726","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-39739","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-39750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39753","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-39761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39770","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-39797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39800","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-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38105","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-39805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39807","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-39815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39819","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-39829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39832","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-39842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39843","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-39854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39857","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-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-38713","title":"hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","status":"published","published":"2025-09-04T15:33:03.464Z","modified":"2026-08-05T12:04:11.569Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:32:47.447481Z"}],"euvd":[{"id":"EUVD-2025-26756","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","status":"published","published":"2025-09-04T15:33:03Z","modified":"2026-08-05T12:04:11Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T18:02:13.097582Z"}],"ghsa":[{"id":"GHSA-f84m-84r4-h992","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","status":"published","published":"2025-09-05T18:31:17Z","modified":"2026-05-12T15:32:08Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:08:04.468489Z"}],"nvd":[{"id":"CVE-2025-38713","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","status":"published","published":"2025-09-04T16:15:40.657Z","modified":"2026-10-19T21:10:00.16Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:11:27.145738Z"}],"osv":[{"id":"BELL-CVE-2025-38713","status":"published","published":"2025-09-05T06:01:28.455247Z","modified":"2026-06-25T07:18:26.827929294Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:22.246535Z"},{"id":"CVE-2025-38713","title":"hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u003cTASK\u003e\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u003c/TASK\u003e\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---","status":"published","published":"2025-09-04T15:33:03.464Z","modified":"2026-10-28T02:30:48.157408997Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:49.052395Z"},{"id":"DEBIAN-CVE-2025-38713","description":"In the Linux kernel, the following vulnerability has been resolved:  hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()  The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc():  [  667.121659][ T9805] ================================================================== [  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10 [  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805 [  667.124578][ T9805] [  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full) [  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [  667.124890][ T9805] Call Trace: [  667.124893][ T9805]  \u003cTASK\u003e [  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0 [  667.124911][ T9805]  print_report+0xd0/0x660 [  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610 [  667.124928][ T9805]  ? __phys_addr+0xe8/0x180 [  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10 [  667.124942][ T9805]  kasan_report+0xc6/0x100 [  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10 [  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10 [  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360 [  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0 [  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10 [  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0 [  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20 [  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0 [  667.125022][ T9805]  ? lock_acquire+0x30/0x80 [  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20 [  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0 [  667.125044][ T9805]  ? putname+0x154/0x1a0 [  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10 [  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0 [  667.125069][ T9805]  iterate_dir+0x296/0xb20 [  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0 [  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10 [  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200 [  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10 [  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0 [  667.125143][ T9805]  do_syscall_64+0xc9/0x480 [  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f [  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9 [  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48 [  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9 [  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9 [  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004 [  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110 [  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260 [  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [  667.125207][ T9805]  \u003c/TASK\u003e [  667.125210][ T9805] [  667.145632][ T9805] Allocated by task 9805: [  667.145991][ T9805]  kasan_save_stack+0x20/0x40 [  667.146352][ T9805]  kasan_save_track+0x14/0x30 [  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0 [  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550 [  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0 [  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0 [  667.148174][ T9805]  iterate_dir+0x296/0xb20 [  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0 [  667.148937][ T9805]  do_syscall_64+0xc9/0x480 [  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f [  667.149809][ T9805] [  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000 [  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048 [  667.151282][ T9805] The buggy address is located 0 bytes to the right of [  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c) [  667.1 ---truncated---","status":"published","published":"2025-09-04T16:15:40.657Z","modified":"2026-10-23T18:04:34.450573606Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:46.626332Z"},{"id":"OESA-2026-1275","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix premature hw access after PCI error\n\nAfter a recoverable PCI error has been detected and recovered, qla driver\nneeds to check to see if the error condition still persist and/or wait\nfor the OS to give the resume signal.\n\nSep  8 22:26:03 localhost kernel: WARNING: CPU: 9 PID: 124606 at qla_tmpl.c:440\nqla27xx_fwdt_entry_t266+0x55/0x60 [qla2xxx]\nSep  8 22:26:03 localhost kernel: RIP: 0010:qla27xx_fwdt_entry_t266+0x55/0x60\n[qla2xxx]\nSep  8 22:26:03 localhost kernel: Call Trace:\nSep  8 22:26:03 localhost kernel: ? qla27xx_walk_template+0xb1/0x1b0 [qla2xxx]\nSep  8 22:26:03 localhost kernel: ? qla27xx_execute_fwdt_template+0x12a/0x160\n[qla2xxx]\nSep  8 22:26:03 localhost kernel: ? qla27xx_fwdump+0xa0/0x1c0 [qla2xxx]\nSep  8 22:26:03 localhost kernel: ? qla2xxx_pci_mmio_enabled+0xfb/0x120\n[qla2xxx]\nSep  8 22:26:03 localhost kernel: ? report_mmio_enabled+0x44/0x80\nSep  8 22:26:03 localhost kernel: ? report_slot_reset+0x80/0x80\nSep  8 22:26:03 localhost kernel: ? pci_walk_bus+0x70/0x90\nSep  8 22:26:03 localhost kernel: ? aer_dev_correctable_show+0xc0/0xc0\nSep  8 22:26:03 localhost kernel: ? pcie_do_recovery+0x1bb/0x240\nSep  8 22:26:03 localhost kernel: ? aer_recover_work_func+0xaa/0xd0\nSep  8 22:26:03 localhost kernel: ? process_one_work+0x1a7/0x360\n..\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-8041:22: detected PCI\ndisconnect.\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-107ff:22:\nqla27xx_fwdt_entry_t262: dump ram MB failed. Area 5h start 198013h end 198013h\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-107ff:22: Unable to\ncapture FW dump\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-1015:22: cmd=0x0,\nwaited 5221 msecs\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-680d:22: mmio\nenabled returning.\nSep  8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-d04c:22: MBX\nCommand timeout for cmd 0, iocontrol=ffffffff jiffies=10140f2e5\nmb[0-3]=[0xffff 0xffff 0xffff 0xffff](CVE-2022-49157)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid0, raid10: Don\u0026apos;t set discard sectors for request queue\n\nIt should use disk_stack_limits to get a proper max_discard_sectors\nrather than setting a value by stack drivers.\n\nAnd there is a bug. If all member disks are rotational devices,\nraid0/raid10 set max_discard_sectors. So the member devices are\nnot ssd/nvme, but raid0/raid10 export the wrong value. It reports\nwarning messages in function __blkdev_issue_discard when mkfs.xfs\nlike this:\n\n[ 4616.022599] ------------[ cut here ]------------\n[ 4616.027779] WARNING: CPU: 4 PID: 99634 at block/blk-lib.c:50 __blkdev_issue_discard+0x16a/0x1a0\n[ 4616.140663] RIP: 0010:__blkdev_issue_discard+0x16a/0x1a0\n[ 4616.146601] Code: 24 4c 89 20 31 c0 e9 fe fe ff ff c1 e8 09 8d 48 ff 4c 89 f0 4c 09 e8 48 85 c1 0f 84 55 ff ff ff b8 ea ff ff ff e9 df fe ff ff \u0026lt;0f\u0026gt; 0b 48 8d 74 24 08 e8 ea d6 00 00 48 c7 c6 20 1e 89 ab 48 c7 c7\n[ 4616.167567] RSP: 0018:ffffaab88cbffca8 EFLAGS: 00010246\n[ 4616.173406] RAX: ffff9ba1f9e44678 RBX: 0000000000000000 RCX: ffff9ba1c9792080\n[ 4616.181376] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9ba1c9792080\n[ 4616.189345] RBP: 0000000000000cc0 R08: ffffaab88cbffd10 R09: 0000000000000000\n[ 4616.197317] R10: 0000000000000012 R11: 0000000000000000 R12: 0000000000000000\n[ 4616.205288] R13: 0000000000400000 R14: 0000000000000cc0 R15: ffff9ba1c9792080\n[ 4616.213259] FS:  00007f9a5534e980(0000) GS:ffff9ba1b7c80000(0000) knlGS:0000000000000000\n[ 4616.222298] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 4616.228719] CR2: 000055a390a4c518 CR3: 0000000123e40006 CR4: 00000000001706e0\n[ 4616.236689] Call Trace:\n[ 4616.239428]  blkdev_issue_discard+0x52/0xb0\n[ 4616.244108]  blkdev_common_ioctl+0x43c/0xa00\n[ 4616.248883]  blkdev_ioctl+0x116/0x280\n[ 4616.252977]  __x64_sys_ioctl+0x8a/0xc0\n[ 4616.257163]  do_syscall_64+0x5c/0x90\n[ 4616.261164]  ? handle_mm_fault+0xc5/0x2a0\n[ 4616.265652]  ? do_user_addr_fault+0x1d8/0x690\n[ 4616.270527]  ? do_syscall_64+0x69/0x90\n[ 4616.274717]  ? exc_page_fault+0x62/0x150\n[ 4616.279097]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[ 4616.284748] RIP: 0033:0x7f9a55398c6b(CVE-2022-50583)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Validate index root when initialize NTFS security\n\nThis enhances the sanity check for $SDH and $SII while initializing NTFS\nsecurity, guarantees these index root are legit.\n\n[  162.459513] BUG: KASAN: use-after-free in hdr_find_e.isra.0+0x10c/0x320\n[  162.460176] Read of size 2 at addr ffff8880037bca99 by task mount/243\n[  162.460851]\n[  162.461252] CPU: 0 PID: 243 Comm: mount Not tainted 6.0.0-rc7 #42\n[  162.461744] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n[  162.462609] Call Trace:\n[  162.462954]  \u0026lt;TASK\u0026gt;\n[  162.463276]  dump_stack_lvl+0x49/0x63\n[  162.463822]  print_report.cold+0xf5/0x689\n[  162.464608]  ? unwind_get_return_address+0x3a/0x60\n[  162.465766]  ? hdr_find_e.isra.0+0x10c/0x320\n[  162.466975]  kasan_report+0xa7/0x130\n[  162.467506]  ? _raw_spin_lock_irq+0xc0/0xf0\n[  162.467998]  ? hdr_find_e.isra.0+0x10c/0x320\n[  162.468536]  __asan_load2+0x68/0x90\n[  162.468923]  hdr_find_e.isra.0+0x10c/0x320\n[  162.469282]  ? cmp_uints+0xe0/0xe0\n[  162.469557]  ? cmp_sdh+0x90/0x90\n[  162.469864]  ? ni_find_attr+0x214/0x300\n[  162.470217]  ? ni_load_mi+0x80/0x80\n[  162.470479]  ? entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[  162.470931]  ? ntfs_bread_run+0x190/0x190\n[  162.471307]  ? indx_get_root+0xe4/0x190\n[  162.471556]  ? indx_get_root+0x140/0x190\n[  162.471833]  ? indx_init+0x1e0/0x1e0\n[  162.472069]  ? fnd_clear+0x115/0x140\n[  162.472363]  ? _raw_spin_lock_irqsave+0x100/0x100\n[  162.472731]  indx_find+0x184/0x470\n[  162.473461]  ? sysvec_apic_timer_interrupt+0x57/0xc0\n[  162.474429]  ? indx_find_buffer+0x2d0/0x2d0\n[  162.474704]  ? do_syscall_64+0x3b/0x90\n[  162.474962]  dir_search_u+0x196/0x2f0\n[  162.475381]  ? ntfs_nls_to_utf16+0x450/0x450\n[  162.475661]  ? ntfs_security_init+0x3d6/0x440\n[  162.475906]  ? is_sd_valid+0x180/0x180\n[  162.476191]  ntfs_extend_init+0x13f/0x2c0\n[  162.476496]  ? ntfs_fix_post_read+0x130/0x130\n[  162.476861]  ? iput.part.0+0x286/0x320\n[  162.477325]  ntfs_fill_super+0x11e0/0x1b50\n[  162.477709]  ? put_ntfs+0x1d0/0x1d0\n[  162.477970]  ? vsprintf+0x20/0x20\n[  162.478258]  ? set_blocksize+0x95/0x150\n[  162.478538]  get_tree_bdev+0x232/0x370\n[  162.478789]  ? put_ntfs+0x1d0/0x1d0\n[  162.479038]  ntfs_fs_get_tree+0x15/0x20\n[  162.479374]  vfs_get_tree+0x4c/0x130\n[  162.479729]  path_mount+0x654/0xfe0\n[  162.480124]  ? putname+0x80/0xa0\n[  162.480484]  ? finish_automount+0x2e0/0x2e0\n[  162.480894]  ? putname+0x80/0xa0\n[  162.481467]  ? kmem_cache_free+0x1c4/0x440\n[  162.482280]  ? putname+0x80/0xa0\n[  162.482714]  do_mount+0xd6/0xf0\n[  162.483264]  ? path_mount+0xfe0/0xfe0\n[  162.484782]  ? __kasan_check_write+0x14/0x20\n[  162.485593]  __x64_sys_mount+0xca/0x110\n[  162.486024]  do_syscall_64+0x3b/0x90\n[  162.486543]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[  162.487141] RIP: 0033:0x7f9d374e948a\n[  162.488324] Code: 48 8b 0d 11 fa 2a 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 008\n[  162.489728] RSP: 002b:00007ffe30e73d18 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5\n[  162.490971] RAX: ffffffffffffffda RBX: 0000561cdb43a060 RCX: 00007f9d374e948a\n[  162.491669] RDX: 0000561cdb43a260 RSI: 0000561cdb43a2e0 RDI: 0000561cdb442af0\n[  162.492050] RBP: 0000000000000000 R08: 0000561cdb43a280 R09: 0000000000000020\n[  162.492459] R10: 00000000c0ed0000 R11: 0000000000000206 R12: 0000561cdb442af0\n[  162.493183] R13: 0000561cdb43a260 R14: 0000000000000000 R15: 00000000ffffffff\n[  162.493644]  \u0026lt;/TASK\u0026gt;\n[  162.493908]\n[  162.494214] The buggy address belongs to the physical page:\n[  162.494761] page:000000003e38a3d5 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x37bc\n[  162.496064] flags: 0xfffffc0000000(node=0|zone=1|lastcpupid=0x1fffff)\n[  162.497278] raw: 000fffffc0000000 ffffea00000df1c8 ffffea00000df008 0000000000000000\n[  162.498928] raw: 0000000000000000 0000000000240000 0\n---truncated---(CVE-2022-50737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Avoid calling OPDESC() with ops-\u0026gt;opnum == OP_ILLEGAL\n\nOPDESC() simply indexes into nfsd4_ops[] by the op\u0026apos;s operation\nnumber, without range checking that value. It assumes callers are\ncareful to avoid calling it with an out-of-bounds opnum value.\n\nnfsd4_decode_compound() is not so careful, and can invoke OPDESC()\nwith opnum set to OP_ILLEGAL, which is 10044 -- well beyond the end\nof nfsd4_ops[].(CVE-2023-53680)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix session state check in reconnect to avoid use-after-free issue\n\nDon\u0026apos;t collect exiting session in smb2_reconnect_server(), because it\nwill be released soon.\n\nNote that the exiting session will stay in server-\u0026gt;smb_ses_list until\nit complete the cifs_free_ipc() and logoff() and then delete itself\nfrom the list.(CVE-2023-53794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau/kms/nv50-: init hpd_irq_lock for PIOR DP\n\nFixes OOPS on boards with ANX9805 DP encoders.(CVE-2023-54263)\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\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\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\nVMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify\n\nDuring our test, it is found that a warning can be trigger in try_grab_folio\nas follow:\n\n  ------------[ cut here ]------------\n  WARNING: CPU: 0 PID: 1678 at mm/gup.c:147 try_grab_folio+0x106/0x130\n  Modules linked in:\n  CPU: 0 UID: 0 PID: 1678 Comm: syz.3.31 Not tainted 6.15.0-rc5 #163 PREEMPT(undef)\n  RIP: 0010:try_grab_folio+0x106/0x130\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   follow_huge_pmd+0x240/0x8e0\n   follow_pmd_mask.constprop.0.isra.0+0x40b/0x5c0\n   follow_pud_mask.constprop.0.isra.0+0x14a/0x170\n   follow_page_mask+0x1c2/0x1f0\n   __get_user_pages+0x176/0x950\n   __gup_longterm_locked+0x15b/0x1060\n   ? gup_fast+0x120/0x1f0\n   gup_fast_fallback+0x17e/0x230\n   get_user_pages_fast+0x5f/0x80\n   vmci_host_unlocked_ioctl+0x21c/0xf80\n  RIP: 0033:0x54d2cd\n  ---[ end trace 0000000000000000 ]---\n\nDigging into the source, context-\u0026gt;notify_page may init by get_user_pages_fast\nand can be seen in vmci_ctx_unset_notify which will try to put_page. However\nget_user_pages_fast is not finished here and lead to following\ntry_grab_folio warning. The race condition is shown as follow:\n\ncpu0\t\t\tcpu1\nvmci_host_do_set_notify\nvmci_host_setup_notify\nget_user_pages_fast(uva, 1, FOLL_WRITE, \u0026amp;context-\u0026gt;notify_page);\nlockless_pages_from_mm\ngup_pgd_range\ngup_huge_pmd  // update \u0026amp;context-\u0026gt;notify_page\n\t\t\tvmci_host_do_set_notify\n\t\t\tvmci_ctx_unset_notify\n\t\t\tnotify_page = context-\u0026gt;notify_page;\n\t\t\tif (notify_page)\n\t\t\tput_page(notify_page);\t// page is freed\n__gup_longterm_locked\n__get_user_pages\nfollow_trans_huge_pmd\ntry_grab_folio // warn here\n\nTo slove this, use local variable page to make notify_page can be seen\nafter finish get_user_pages_fast.(CVE-2025-38102)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()\n\nUpdate struct hid_descriptor to better reflect the mandatory and\noptional parts of the HID Descriptor as per USB HID 1.11 specification.\nNote: the kernel currently does not parse any optional HID class\ndescriptors, only the mandatory report descriptor.\n\nUpdate all references to member element desc[0] to rpt_desc.\n\nAdd test to verify bLength and bNumDescriptors values are valid.\n\nReplace the for loop with direct access to the mandatory HID class\ndescriptor member for the report descriptor. This eliminates the\npossibility of getting an out-of-bounds fault.\n\nAdd a warning message if the HID descriptor contains any unsupported\noptional HID class descriptors.(CVE-2025-38103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/pm: fix null pointer access\n\nWriting a string without delimiters (\u0026apos; \u0026apos;, \u0026apos;\\n\u0026apos;, \u0026apos;\\0\u0026apos;) to the under\ngpu_od/fan_ctrl sysfs or pp_power_profile_mode for the CUSTOM profile\nwill result in a null pointer dereference.(CVE-2025-38705)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/buffer: fix use-after-free when call bh_read() helper\n\nThere\u0026apos;s issue as follows:\nBUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0xe3/0x110\nRead of size 8 at addr ffffc9000168f7f8 by task swapper/3/0\nCPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted 6.16.0-862.14.0.6.x86_64\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996)\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x55/0x70\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb4/0x270\n kasan_report+0xb8/0xf0\n end_buffer_read_sync+0xe3/0x110\n end_bio_bh_io_sync+0x56/0x80\n blk_update_request+0x30a/0x720\n scsi_end_request+0x51/0x2b0\n scsi_io_completion+0xe3/0x480\n ? scsi_device_unbusy+0x11e/0x160\n blk_complete_reqs+0x7b/0x90\n handle_softirqs+0xef/0x370\n irq_exit_rcu+0xa5/0xd0\n sysvec_apic_timer_interrupt+0x6e/0x90\n \u0026lt;/IRQ\u0026gt;\n\n Above issue happens when do ntfs3 filesystem mount, issue may happens\n as follows:\n           mount                            IRQ\nntfs_fill_super\n  read_cache_page\n    do_read_cache_folio\n      filemap_read_folio\n        mpage_read_folio\n\t do_mpage_readpage\n\t  ntfs_get_block_vbo\n\t   bh_read\n\t     submit_bh\n\t     wait_on_buffer(bh);\n\t                            blk_complete_reqs\n\t\t\t\t     scsi_io_completion\n\t\t\t\t      scsi_end_request\n\t\t\t\t       blk_update_request\n\t\t\t\t        end_bio_bh_io_sync\n\t\t\t\t\t end_buffer_read_sync\n\t\t\t\t\t  __end_buffer_read_notouch\n\t\t\t\t\t   unlock_buffer\n\n            wait_on_buffer(bh);--\u0026gt; return will return to caller\n\n\t\t\t\t\t  put_bh\n\t\t\t\t\t    --\u0026gt; trigger stack-out-of-bounds\nIn the mpage_read_folio() function, the stack variable \u0026apos;map_bh\u0026apos; is\npassed to ntfs_get_block_vbo(). Once unlock_buffer() unlocks and\nwait_on_buffer() returns to continue processing, the stack variable\nis likely to be reclaimed. Consequently, during the end_buffer_read_sync()\nprocess, calling put_bh() may result in stack overrun.\n\nIf the bh is not allocated on the stack, it belongs to a folio.  Freeing\na buffer head which belongs to a folio is done by drop_buffers() which\nwill fail to free buffers which are still locked.  So it is safe to call\nput_bh() before __end_buffer_read_notouch().(CVE-2025-39691)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: add max boundary check for VF filters\n\nThere is no check for max filters that VF can request. Add it.(CVE-2025-39968)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npid: Add a judgment for ns null in pid_nr_ns\n\n__task_pid_nr_ns\n        ns = task_active_pid_ns(current);\n        pid_nr_ns(rcu_dereference(*task_pid_ptr(task, type)), ns);\n                if (pid \u0026amp;\u0026amp; ns-\u0026gt;level \u0026lt;= pid-\u0026gt;level) {\n\nSometimes null is returned for task_active_pid_ns. Then it will trigger kernel panic in pid_nr_ns.\n\nFor example:\n\tUnable to handle kernel NULL pointer dereference at virtual address 0000000000000058\n\tMem abort info:\n\tESR = 0x0000000096000007\n\tEC = 0x25: DABT (current EL), IL = 32 bits\n\tSET = 0, FnV = 0\n\tEA = 0, S1PTW = 0\n\tFSC = 0x07: level 3 translation fault\n\tData abort info:\n\tISV = 0, ISS = 0x00000007, ISS2 = 0x00000000\n\tCM = 0, WnR = 0, TnD = 0, TagAccess = 0\n\tGCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n\tuser pgtable: 4k pages, 39-bit VAs, pgdp=00000002175aa000\n\t[0000000000000058] pgd=08000002175ab003, p4d=08000002175ab003, pud=08000002175ab003, pmd=08000002175be003, pte=0000000000000000\n\tpstate: 834000c5 (Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--)\n\tpc : __task_pid_nr_ns+0x74/0xd0\n\tlr : __task_pid_nr_ns+0x24/0xd0\n\tsp : ffffffc08001bd10\n\tx29: ffffffc08001bd10 x28: ffffffd4422b2000 x27: 0000000000000001\n\tx26: ffffffd442821168 x25: ffffffd442821000 x24: 00000f89492eab31\n\tx23: 00000000000000c0 x22: ffffff806f5693c0 x21: ffffff806f5693c0\n\tx20: 0000000000000001 x19: 0000000000000000 x18: 0000000000000000\n\tx17: 00000000529c6ef0 x16: 00000000529c6ef0 x15: 00000000023a1adc\n\tx14: 0000000000000003 x13: 00000000007ef6d8 x12: 001167c391c78800\n\tx11: 00ffffffffffffff x10: 0000000000000000 x9 : 0000000000000001\n\tx8 : ffffff80816fa3c0 x7 : 0000000000000000 x6 : 49534d702d535449\n\tx5 : ffffffc080c4c2c0 x4 : ffffffd43ee128c8 x3 : ffffffd43ee124dc\n\tx2 : 0000000000000000 x1 : 0000000000000001 x0 : ffffff806f5693c0\n\tCall trace:\n\t__task_pid_nr_ns+0x74/0xd0\n\t...\n\t__handle_irq_event_percpu+0xd4/0x284\n\thandle_irq_event+0x48/0xb0\n\thandle_fasteoi_irq+0x160/0x2d8\n\tgeneric_handle_domain_irq+0x44/0x60\n\tgic_handle_irq+0x4c/0x114\n\tcall_on_irq_stack+0x3c/0x74\n\tdo_interrupt_handler+0x4c/0x84\n\tel1_interrupt+0x34/0x58\n\tel1h_64_irq_handler+0x18/0x24\n\tel1h_64_irq+0x68/0x6c\n\taccount_kernel_stack+0x60/0x144\n\texit_task_stack_account+0x1c/0x80\n\tdo_exit+0x7e4/0xaf8\n\t...\n\tget_signal+0x7bc/0x8d8\n\tdo_notify_resume+0x128/0x828\n\tel0_svc+0x6c/0x70\n\tel0t_64_sync_handler+0x68/0xbc\n\tel0t_64_sync+0x1a8/0x1ac\n\tCode: 35fffe54 911a02a8 f9400108 b4000128 (b9405a69)\n\t---[ end trace 0000000000000000 ]---\n\tKernel panic - not syncing: Oops: Fatal exception in interrupt(CVE-2025-40178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nA use-after-free vulnerability exists in the mlxsw spectrum multicast route component of Linux Kernel. The vulnerability occurs when updating multicast route statistics, where an instance of list entry deletion during route replace was missed from mutex protection, potentially leading to use-after-free.(CVE-2025-68800)\n\nA reference counting management vulnerability exists in the mlxsw: spectrum_router driver component of the Linux kernel. The driver stores a pointer to a neighbour object without properly holding a reference to it. A reference is only taken when the neighbour is used by a nexthop. This inconsistent reference counting scheme can lead to a situation where, under specific conditions (e.g., during network device event handling), the driver attempts to access a neighbour object that has already been freed, triggering a use-after-free error. An attacker could potentially exploit this vulnerability to cause a kernel crash, thereby affecting system availability.(CVE-2025-68801)\n\nAn off-by-one vulnerability exists in the Intel Ethernet Virtual Function (iavf) driver of the Linux kernel. The flaw resides in the `iavf_config_rss_reg()` function. When configuring the Receive Side Scaling (RSS) hash key and lookup table, incorrect loop boundary conditions (using `\u0026lt;=` instead of `\u0026lt;`) lead to out-of-bounds reads from allocated memory and potential out-of-bounds writes to device registers. An attacker could potentially exploit this vulnerability to cause kernel information disclosure, system instability, or crashes.(CVE-2025-71087)\n\nIn the Linux kernel, a buffer overflow vulnerability exists in the e1000 network driver\u0026apos;s e1000_tbi_should_accept() function. The function reads the last byte of the frame via \u0026apos;data[length - 1]\u0026apos; to evaluate the TBI (Tunnel Bypass Identifier) workaround. If the descriptor-reported length is zero or larger than the actual RX buffer size, this read goes out of bounds and can hit unrelated slab objects. The issue is observed from the NAPI receive path (e1000_clean_rx_irq). The root cause is that the TBI check unconditionally dereferences the last byte without validating the reported length first. The fix rejects the frame early if the length is zero or exceeds adapter-\u0026gt;rx_buffer_len, preserving the TBI workaround semantics for valid frames and preventing touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)","status":"published","published":"2026-01-30T11:10:18Z","modified":"2026-08-18T01:19:31.509394002Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1303","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: eir: Fix possible crashes on eir_create_adv_data\n\neir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER\nwithout checking if that would fit.(CVE-2025-38303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024\n  RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again\n\nCommit 7ded842b356d (\u0026quot;s390/bpf: Fix bpf_plt pointer arithmetic\u0026quot;) has\naccidentally removed the critical piece of commit c730fce7c70c\n(\u0026quot;s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL\u0026quot;), causing\nintermittent kernel panics in e.g. perf\u0026apos;s on_switch() prog to reappear.\n\nRestore the fix and add a comment.(CVE-2025-38489)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Avoid stack buffer overflow from kernel cmdline\n\nWhile the kernel command line is considered trusted in most environments,\navoid writing 1 byte past the end of \u0026quot;acpiid\u0026quot; if the \u0026quot;str\u0026quot; argument is\nmaximum length.(CVE-2025-38676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - flush misc workqueue during device shutdown\n\nRepeated loading and unloading of a device specific QAT driver, for\nexample qat_4xxx, in a tight loop can lead to a crash due to a\nuse-after-free scenario. This occurs when a power management (PM)\ninterrupt triggers just before the device-specific driver (e.g.,\nqat_4xxx.ko) is unloaded, while the core driver (intel_qat.ko) remains\nloaded.\n\nSince the driver uses a shared workqueue (`qat_misc_wq`) across all\ndevices and owned by intel_qat.ko, a deferred routine from the\ndevice-specific driver may still be pending in the queue. If this\nroutine executes after the driver is unloaded, it can dereference freed\nmemory, resulting in a page fault and kernel crash like the following:\n\n    BUG: unable to handle page fault for address: ffa000002e50a01c\n    #PF: supervisor read access in kernel mode\n    RIP: 0010:pm_bh_handler+0x1d2/0x250 [intel_qat]\n    Call Trace:\n      pm_bh_handler+0x1d2/0x250 [intel_qat]\n      process_one_work+0x171/0x340\n      worker_thread+0x277/0x3a0\n      kthread+0xf0/0x120\n      ret_from_fork+0x2d/0x50\n\nTo prevent this, flush the misc workqueue during device shutdown to\nensure that all pending work items are completed before the driver is\nunloaded.\n\nNote: This approach may slightly increase shutdown latency if the\nworkqueue contains jobs from other devices, but it ensures correctness\nand stability.(CVE-2025-39721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect -\u0026gt;defer_qs_iw_pending from data race\n\nOn kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is\ninvoked within an interrupts-disabled region of code [1], it will invoke\nrcu_read_unlock_special(), which uses an irq-work handler to force the\nsystem to notice when the RCU read-side critical section actually ends.\nThat end won\u0026apos;t happen until interrupts are enabled at the soonest.\n\nIn some kernels, such as those booted with rcutree.use_softirq=y, the\nirq-work handler is used unconditionally.\n\nThe per-CPU rcu_data structure\u0026apos;s -\u0026gt;defer_qs_iw_pending field is\nupdated by the irq-work handler and is both read and updated by\nrcu_read_unlock_special().  This resulted in the following KCSAN splat:\n\n------------------------------------------------------------------------\n\nBUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special\n\nread to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8:\n rcu_read_unlock_special+0x175/0x260\n __rcu_read_unlock+0x92/0xa0\n rt_spin_unlock+0x9b/0xc0\n __local_bh_enable+0x10d/0x170\n __local_bh_enable_ip+0xfb/0x150\n rcu_do_batch+0x595/0xc40\n rcu_cpu_kthread+0x4e9/0x830\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nwrite to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8:\n rcu_preempt_deferred_qs_handler+0x1e/0x30\n irq_work_single+0xaf/0x160\n run_irq_workd+0x91/0xc0\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nno locks held by irq_work/8/88.\nirq event stamp: 200272\nhardirqs last  enabled at (200272): [\u0026lt;ffffffffb0f56121\u0026gt;] finish_task_switch+0x131/0x320\nhardirqs last disabled at (200271): [\u0026lt;ffffffffb25c7859\u0026gt;] __schedule+0x129/0xd70\nsoftirqs last  enabled at (0): [\u0026lt;ffffffffb0ee093f\u0026gt;] copy_process+0x4df/0x1cc0\nsoftirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n\n------------------------------------------------------------------------\n\nThe problem is that irq-work handlers run with interrupts enabled, which\nmeans that rcu_preempt_deferred_qs_handler() could be interrupted,\nand that interrupt handler might contain an RCU read-side critical\nsection, which might invoke rcu_read_unlock_special().  In the strict\nKCSAN mode of operation used by RCU, this constitutes a data race on\nthe -\u0026gt;defer_qs_iw_pending field.\n\nThis commit therefore disables interrupts across the portion of the\nrcu_preempt_deferred_qs_handler() that updates the -\u0026gt;defer_qs_iw_pending\nfield.  This suffices because this handler is not a fast path.(CVE-2025-39749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: prevent NULL pointer dereference in UTF16 conversion\n\nThere can be a NULL pointer dereference bug here. NULL is passed to\n__cifs_sfu_make_node without checks, which passes it unchecked to\ncifs_strndup_to_utf16, which in turn passes it to\ncifs_local_to_utf16_bytes where \u0026apos;*from\u0026apos; is dereferenced, causing a crash.\n\nThis patch adds a check for NULL \u0026apos;src\u0026apos; in cifs_strndup_to_utf16 and\nreturns NULL early to prevent dereferencing NULL pointer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE(CVE-2025-39838)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix null-deref in agg_dequeue\n\nTo prevent a potential crash in agg_dequeue (net/sched/sch_qfq.c)\nwhen cl-\u0026gt;qdisc-\u0026gt;ops-\u0026gt;peek(cl-\u0026gt;qdisc) returns NULL, we check the return\nvalue before using it, similar to the existing approach in sch_hfsc.c.\n\nTo avoid code duplication, the following changes are made:\n\n1. Changed qdisc_warn_nonwc(include/net/pkt_sched.h) into a static\ninline function.\n\n2. Moved qdisc_peek_len from net/sched/sch_hfsc.c to\ninclude/net/pkt_sched.h so that sch_qfq can reuse it.\n\n3. Applied qdisc_peek_len in agg_dequeue to avoid crashing.(CVE-2025-40083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfs: Don\u0026apos;t leak disconnected dentries on umount\n\nWhen user calls open_by_handle_at() on some inode that is not cached, we\nwill create disconnected dentry for it. If such dentry is a directory,\nexportfs_decode_fh_raw() will then try to connect this dentry to the\ndentry tree through reconnect_path(). It may happen for various reasons\n(such as corrupted fs or race with rename) that the call to\nlookup_one_unlocked() in reconnect_one() will fail to find the dentry we\nare trying to reconnect and instead create a new dentry under the\nparent. Now this dentry will not be marked as disconnected although the\nparent still may well be disconnected (at least in case this\ninconsistency happened because the fs is corrupted and .. doesn\u0026apos;t point\nto the real parent directory). This creates inconsistency in\ndisconnected flags but AFAICS it was mostly harmless. At least until\ncommit f1ee616214cb (\u0026quot;VFS: don\u0026apos;t keep disconnected dentries on d_anon\u0026quot;)\nwhich removed adding of most disconnected dentries to sb-\u0026gt;s_anon list.\nThus after this commit cleanup of disconnected dentries implicitely\nrelies on the fact that dput() will immediately reclaim such dentries.\nHowever when some leaf dentry isn\u0026apos;t marked as disconnected, as in the\nscenario described above, the reclaim doesn\u0026apos;t happen and the dentries\nare \u0026quot;leaked\u0026quot;. Memory reclaim can eventually reclaim them but otherwise\nthey stay in memory and if umount comes first, we hit infamous \u0026quot;Busy\ninodes after unmount\u0026quot; bug. Make sure all dentries created under a\ndisconnected parent are marked as disconnected as well.(CVE-2025-40105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.496570777Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1304","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: eir: Fix possible crashes on eir_create_adv_data\n\neir_create_adv_data may attempt to add EIR_FLAGS and EIR_TX_POWER\nwithout checking if that would fit.(CVE-2025-38303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024\n  RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL again\n\nCommit 7ded842b356d (\u0026quot;s390/bpf: Fix bpf_plt pointer arithmetic\u0026quot;) has\naccidentally removed the critical piece of commit c730fce7c70c\n(\u0026quot;s390/bpf: Fix bpf_arch_text_poke() with new_addr == NULL\u0026quot;), causing\nintermittent kernel panics in e.g. perf\u0026apos;s on_switch() prog to reappear.\n\nRestore the fix and add a comment.(CVE-2025-38489)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Avoid stack buffer overflow from kernel cmdline\n\nWhile the kernel command line is considered trusted in most environments,\navoid writing 1 byte past the end of \u0026quot;acpiid\u0026quot; if the \u0026quot;str\u0026quot; argument is\nmaximum length.(CVE-2025-38676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - flush misc workqueue during device shutdown\n\nRepeated loading and unloading of a device specific QAT driver, for\nexample qat_4xxx, in a tight loop can lead to a crash due to a\nuse-after-free scenario. This occurs when a power management (PM)\ninterrupt triggers just before the device-specific driver (e.g.,\nqat_4xxx.ko) is unloaded, while the core driver (intel_qat.ko) remains\nloaded.\n\nSince the driver uses a shared workqueue (`qat_misc_wq`) across all\ndevices and owned by intel_qat.ko, a deferred routine from the\ndevice-specific driver may still be pending in the queue. If this\nroutine executes after the driver is unloaded, it can dereference freed\nmemory, resulting in a page fault and kernel crash like the following:\n\n    BUG: unable to handle page fault for address: ffa000002e50a01c\n    #PF: supervisor read access in kernel mode\n    RIP: 0010:pm_bh_handler+0x1d2/0x250 [intel_qat]\n    Call Trace:\n      pm_bh_handler+0x1d2/0x250 [intel_qat]\n      process_one_work+0x171/0x340\n      worker_thread+0x277/0x3a0\n      kthread+0xf0/0x120\n      ret_from_fork+0x2d/0x50\n\nTo prevent this, flush the misc workqueue during device shutdown to\nensure that all pending work items are completed before the driver is\nunloaded.\n\nNote: This approach may slightly increase shutdown latency if the\nworkqueue contains jobs from other devices, but it ensures correctness\nand stability.(CVE-2025-39721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect -\u0026gt;defer_qs_iw_pending from data race\n\nOn kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is\ninvoked within an interrupts-disabled region of code [1], it will invoke\nrcu_read_unlock_special(), which uses an irq-work handler to force the\nsystem to notice when the RCU read-side critical section actually ends.\nThat end won\u0026apos;t happen until interrupts are enabled at the soonest.\n\nIn some kernels, such as those booted with rcutree.use_softirq=y, the\nirq-work handler is used unconditionally.\n\nThe per-CPU rcu_data structure\u0026apos;s -\u0026gt;defer_qs_iw_pending field is\nupdated by the irq-work handler and is both read and updated by\nrcu_read_unlock_special().  This resulted in the following KCSAN splat:\n\n------------------------------------------------------------------------\n\nBUG: KCSAN: data-race in rcu_preempt_deferred_qs_handler / rcu_read_unlock_special\n\nread to 0xffff96b95f42d8d8 of 1 bytes by task 90 on cpu 8:\n rcu_read_unlock_special+0x175/0x260\n __rcu_read_unlock+0x92/0xa0\n rt_spin_unlock+0x9b/0xc0\n __local_bh_enable+0x10d/0x170\n __local_bh_enable_ip+0xfb/0x150\n rcu_do_batch+0x595/0xc40\n rcu_cpu_kthread+0x4e9/0x830\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nwrite to 0xffff96b95f42d8d8 of 1 bytes by task 88 on cpu 8:\n rcu_preempt_deferred_qs_handler+0x1e/0x30\n irq_work_single+0xaf/0x160\n run_irq_workd+0x91/0xc0\n smpboot_thread_fn+0x24d/0x3b0\n kthread+0x3bd/0x410\n ret_from_fork+0x35/0x40\n ret_from_fork_asm+0x1a/0x30\n\nno locks held by irq_work/8/88.\nirq event stamp: 200272\nhardirqs last  enabled at (200272): [\u0026lt;ffffffffb0f56121\u0026gt;] finish_task_switch+0x131/0x320\nhardirqs last disabled at (200271): [\u0026lt;ffffffffb25c7859\u0026gt;] __schedule+0x129/0xd70\nsoftirqs last  enabled at (0): [\u0026lt;ffffffffb0ee093f\u0026gt;] copy_process+0x4df/0x1cc0\nsoftirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n\n------------------------------------------------------------------------\n\nThe problem is that irq-work handlers run with interrupts enabled, which\nmeans that rcu_preempt_deferred_qs_handler() could be interrupted,\nand that interrupt handler might contain an RCU read-side critical\nsection, which might invoke rcu_read_unlock_special().  In the strict\nKCSAN mode of operation used by RCU, this constitutes a data race on\nthe -\u0026gt;defer_qs_iw_pending field.\n\nThis commit therefore disables interrupts across the portion of the\nrcu_preempt_deferred_qs_handler() that updates the -\u0026gt;defer_qs_iw_pending\nfield.  This suffices because this handler is not a fast path.(CVE-2025-39749)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: prevent NULL pointer dereference in UTF16 conversion\n\nThere can be a NULL pointer dereference bug here. NULL is passed to\n__cifs_sfu_make_node without checks, which passes it unchecked to\ncifs_strndup_to_utf16, which in turn passes it to\ncifs_local_to_utf16_bytes where \u0026apos;*from\u0026apos; is dereferenced, causing a crash.\n\nThis patch adds a check for NULL \u0026apos;src\u0026apos; in cifs_strndup_to_utf16 and\nreturns NULL early to prevent dereferencing NULL pointer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE(CVE-2025-39838)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix null-deref in agg_dequeue\n\nTo prevent a potential crash in agg_dequeue (net/sched/sch_qfq.c)\nwhen cl-\u0026gt;qdisc-\u0026gt;ops-\u0026gt;peek(cl-\u0026gt;qdisc) returns NULL, we check the return\nvalue before using it, similar to the existing approach in sch_hfsc.c.\n\nTo avoid code duplication, the following changes are made:\n\n1. Changed qdisc_warn_nonwc(include/net/pkt_sched.h) into a static\ninline function.\n\n2. Moved qdisc_peek_len from net/sched/sch_hfsc.c to\ninclude/net/pkt_sched.h so that sch_qfq can reuse it.\n\n3. Applied qdisc_peek_len in agg_dequeue to avoid crashing.(CVE-2025-40083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvfs: Don\u0026apos;t leak disconnected dentries on umount\n\nWhen user calls open_by_handle_at() on some inode that is not cached, we\nwill create disconnected dentry for it. If such dentry is a directory,\nexportfs_decode_fh_raw() will then try to connect this dentry to the\ndentry tree through reconnect_path(). It may happen for various reasons\n(such as corrupted fs or race with rename) that the call to\nlookup_one_unlocked() in reconnect_one() will fail to find the dentry we\nare trying to reconnect and instead create a new dentry under the\nparent. Now this dentry will not be marked as disconnected although the\nparent still may well be disconnected (at least in case this\ninconsistency happened because the fs is corrupted and .. doesn\u0026apos;t point\nto the real parent directory). This creates inconsistency in\ndisconnected flags but AFAICS it was mostly harmless. At least until\ncommit f1ee616214cb (\u0026quot;VFS: don\u0026apos;t keep disconnected dentries on d_anon\u0026quot;)\nwhich removed adding of most disconnected dentries to sb-\u0026gt;s_anon list.\nThus after this commit cleanup of disconnected dentries implicitely\nrelies on the fact that dput() will immediately reclaim such dentries.\nHowever when some leaf dentry isn\u0026apos;t marked as disconnected, as in the\nscenario described above, the reclaim doesn\u0026apos;t happen and the dentries\nare \u0026quot;leaked\u0026quot;. Memory reclaim can eventually reclaim them but otherwise\nthey stay in memory and if umount comes first, we hit infamous \u0026quot;Busy\ninodes after unmount\u0026quot; bug. Make sure all dentries created under a\ndisconnected parent are marked as disconnected as well.(CVE-2025-40105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.449379768Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"OESA-2026-1305","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()\n\nJakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()\nto increase test coverage.\n\nsyzbot found a splat caused by hard irq blocking in\nptr_ring_resize_multiple() [1]\n\nAs current users of ptr_ring_resize_multiple() do not require\nhard irqs being masked, replace it to only block BH.\n\nRename helpers to better reflect they are safe against BH only.\n\n- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh()\n- skb_array_resize_multiple() to skb_array_resize_multiple_bh()\n\n[1]\n\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 __page_pool_put_page net/core/page_pool.c:709 [inline]\nWARNING: CPU: 1 PID: 9150 at net/core/page_pool.c:709 page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nModules linked in:\nCPU: 1 UID: 0 PID: 9150 Comm: syz.1.1052 Not tainted 6.11.0-rc3-syzkaller-00202-gf8669d7b5f5d #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nRIP: 0010:__page_pool_put_page net/core/page_pool.c:709 [inline]\nRIP: 0010:page_pool_put_unrefed_netmem+0x157/0xa40 net/core/page_pool.c:780\nCode: 74 0e e8 7c aa fb f7 eb 43 e8 75 aa fb f7 eb 3c 65 8b 1d 38 a8 6a 76 31 ff 89 de e8 a3 ae fb f7 85 db 74 0b e8 5a aa fb f7 90 \u0026lt;0f\u0026gt; 0b 90 eb 1d 65 8b 1d 15 a8 6a 76 31 ff 89 de e8 84 ae fb f7 85\nRSP: 0018:ffffc9000bda6b58 EFLAGS: 00010083\nRAX: ffffffff8997e523 RBX: 0000000000000000 RCX: 0000000000040000\nRDX: ffffc9000fbd0000 RSI: 0000000000001842 RDI: 0000000000001843\nRBP: 0000000000000000 R08: ffffffff8997df2c R09: 1ffffd40003a000d\nR10: dffffc0000000000 R11: fffff940003a000e R12: ffffea0001d00040\nR13: ffff88802e8a4000 R14: dffffc0000000000 R15: 00000000ffffffff\nFS:  00007fb7aaf716c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fa15a0d4b72 CR3: 00000000561b0000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tun_ptr_free drivers/net/tun.c:617 [inline]\n __ptr_ring_swap_queue include/linux/ptr_ring.h:571 [inline]\n ptr_ring_resize_multiple_noprof include/linux/ptr_ring.h:643 [inline]\n tun_queue_resize drivers/net/tun.c:3694 [inline]\n tun_device_event+0xaaf/0x1080 drivers/net/tun.c:3714\n notifier_call_chain+0x19f/0x3e0 kernel/notifier.c:93\n call_netdevice_notifiers_extack net/core/dev.c:2032 [inline]\n call_netdevice_notifiers net/core/dev.c:2046 [inline]\n dev_change_tx_queue_len+0x158/0x2a0 net/core/dev.c:9024\n do_setlink+0xff6/0x41f0 net/core/rtnetlink.c:2923\n rtnl_setlink+0x40d/0x5a0 net/core/rtnetlink.c:3201\n rtnetlink_rcv_msg+0x73f/0xcf0 net/core/rtnetlink.c:6647\n netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550(CVE-2024-57994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params\n\nEach cpu DAI should associate with a widget. However, the topology might\nnot create the right number of DAI widgets for aggregated amps. And it\nwill cause NULL pointer deference.\nCheck that the DAI widget associated with the CPU DAI is valid to prevent\nNULL pointer deference due to missing DAI widgets in topologies with\naggregated amps.(CVE-2024-58012)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndriver core: fix potential NULL pointer dereference in dev_uevent()\n\nIf userspace reads \u0026quot;uevent\u0026quot; device attribute at the same time as another\nthreads unbinds the device from its driver, change to dev-\u0026gt;driver from a\nvalid pointer to NULL may result in crash. Fix this by using READ_ONCE()\nwhen fetching the pointer, and take bus\u0026apos; drivers klist lock to make sure\ndriver instance will not disappear while we access it.\n\nUse WRITE_ONCE() when setting the driver pointer to ensure there is no\ntearing.(CVE-2025-37800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds clause 45 read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via C45 (clause 45) mdiobus,\nthere is no verification of parameters passed to the ioctl and\nit accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before C45 read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mdiobus: Fix potential out-of-bounds read/write access\n\nWhen using publicly available tools like \u0026apos;mdio-tools\u0026apos; to read/write data\nfrom/to network interface and its PHY via mdiobus, there is no verification of\nparameters passed to the ioctl and it accepts any mdio address.\nCurrently there is support for 32 addresses in kernel via PHY_MAX_ADDR define,\nbut it is possible to pass higher value than that via ioctl.\nWhile read/write operation should generally fail in this case,\nmdiobus provides stats array, where wrong address may allow out-of-bounds\nread/write.\n\nFix that by adding address verification before read/write operation.\nWhile this excludes this access from any statistics, it improves security of\nread/write operation.(CVE-2025-38111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev-\u0026gt;devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev-\u0026gt;devlink, so phydev-\u0026gt;devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \u0026quot;error\u0026quot; label and\ncalls phy_detach(). Since phydev-\u0026gt;devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev-\u0026gt;devlink needs to be cleared when the device link is\ndeleted.(CVE-2025-38149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: prevent overflow in lookup table allocation\n\nWhen calculating the lookup table size, ensure the following\nmultiplication does not overflow:\n\n- desc-\u0026gt;field_len[] maximum value is U8_MAX multiplied by\n  NFT_PIPAPO_GROUPS_PER_BYTE(f) that can be 2, worst case.\n- NFT_PIPAPO_BUCKETS(f-\u0026gt;bb) is 2^8, worst case.\n- sizeof(unsigned long), from sizeof(*f-\u0026gt;lt), lt in\n  struct nft_pipapo_field.\n\nThen, use check_mul_overflow() to multiply by bucket size and then use\ncheck_add_overflow() to the alignment for avx2 (if needed). Finally, add\nlt_size_check_overflow() helper and use it to consolidate this.\n\nWhile at it, replace leftover allocation using the GFP_KERNEL to\nGFP_KERNEL_ACCOUNT for consistency, in pipapo_resize().(CVE-2025-38162)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: add NULL check in automount_fullpath\n\npage is checked for null in __build_path_from_dentry_optional_prefix\nwhen tcon-\u0026gt;origin_fullpath is not set. However, the check is missing when\nit is set.\nAdd a check to prevent a potential NULL pointer dereference.(CVE-2025-38208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: fix race between nfsd registration and exports_proc\n\nAs of now nfsd calls create_proc_exports_entry() at start of init_nfsd\nand cleanup by remove_proc_entry() at last of exit_nfsd.\n\nWhich causes kernel OOPs if there is race between below 2 operations:\n(i) exportfs -r\n(ii) mount -t nfsd none /proc/fs/nfsd\n\nfor 5.4 kernel ARM64:\n\nCPU 1:\nel1_irq+0xbc/0x180\narch_counter_get_cntvct+0x14/0x18\nrunning_clock+0xc/0x18\npreempt_count_add+0x88/0x110\nprep_new_page+0xb0/0x220\nget_page_from_freelist+0x2d8/0x1778\n__alloc_pages_nodemask+0x15c/0xef0\n__vmalloc_node_range+0x28c/0x478\n__vmalloc_node_flags_caller+0x8c/0xb0\nkvmalloc_node+0x88/0xe0\nnfsd_init_net+0x6c/0x108 [nfsd]\nops_init+0x44/0x170\nregister_pernet_operations+0x114/0x270\nregister_pernet_subsys+0x34/0x50\ninit_nfsd+0xa8/0x718 [nfsd]\ndo_one_initcall+0x54/0x2e0\n\nCPU 2 :\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000010\n\nPC is at : exports_net_open+0x50/0x68 [nfsd]\n\nCall trace:\nexports_net_open+0x50/0x68 [nfsd]\nexports_proc_open+0x2c/0x38 [nfsd]\nproc_reg_open+0xb8/0x198\ndo_dentry_open+0x1c4/0x418\nvfs_open+0x38/0x48\npath_openat+0x28c/0xf18\ndo_filp_open+0x70/0xe8\ndo_sys_open+0x154/0x248\n\nSometimes it crashes at exports_net_open() and sometimes cache_seq_next_rcu().\n\nand same is happening on latest 6.14 kernel as well:\n\n[    0.000000] Linux version 6.14.0-rc5-next-20250304-dirty\n...\n[  285.455918] Unable to handle kernel paging request at virtual address 00001f4800001f48\n...\n[  285.464902] pc : cache_seq_next_rcu+0x78/0xa4\n...\n[  285.469695] Call trace:\n[  285.470083]  cache_seq_next_rcu+0x78/0xa4 (P)\n[  285.470488]  seq_read+0xe0/0x11c\n[  285.470675]  proc_reg_read+0x9c/0xf0\n[  285.470874]  vfs_read+0xc4/0x2fc\n[  285.471057]  ksys_read+0x6c/0xf4\n[  285.471231]  __arm64_sys_read+0x1c/0x28\n[  285.471428]  invoke_syscall+0x44/0x100\n[  285.471633]  el0_svc_common.constprop.0+0x40/0xe0\n[  285.471870]  do_el0_svc_compat+0x1c/0x34\n[  285.472073]  el0_svc_compat+0x2c/0x80\n[  285.472265]  el0t_32_sync_handler+0x90/0x140\n[  285.472473]  el0t_32_sync+0x19c/0x1a0\n[  285.472887] Code: f9400885 93407c23 937d7c27 11000421 (f86378a3)\n[  285.473422] ---[ end trace 0000000000000000 ]---\n\nIt reproduced simply with below script:\nwhile [ 1 ]\ndo\n/exportfs -r\ndone \u0026amp;\n\nwhile [ 1 ]\ndo\ninsmod /nfsd.ko\nmount -t nfsd none /proc/fs/nfsd\numount /proc/fs/nfsd\nrmmod nfsd\ndone \u0026amp;\n\nSo exporting interfaces to user space shall be done at last and\ncleanup at first place.\n\nWith change there is no Kernel OOPs.(CVE-2025-38232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential deadlock when reconnecting channels\n\nFix cifs_signal_cifsd_for_reconnect() to take the correct lock order\nand prevent the following deadlock from happening\n\n======================================================\nWARNING: possible circular locking dependency detected\n6.16.0-rc3-build2+ #1301 Tainted: G S      W\n------------------------------------------------------\ncifsd/6055 is trying to acquire lock:\nffff88810ad56038 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x134/0x200\n\nbut task is already holding lock:\nffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_setup_session+0x81/0x4b0\n       cifs_get_smb_ses+0x771/0x900\n       cifs_mount_get_session+0x7e/0x170\n       cifs_mount+0x92/0x2d0\n       cifs_smb3_do_mount+0x161/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}:\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_match_super+0x101/0x320\n       sget+0xab/0x270\n       cifs_smb3_do_mount+0x1e0/0x460\n       smb3_get_tree+0x55/0x90\n       vfs_get_tree+0x46/0x180\n       do_new_mount+0x1b0/0x2e0\n       path_mount+0x6ee/0x740\n       do_mount+0x98/0xe0\n       __do_sys_mount+0x148/0x180\n       do_syscall_64+0xa4/0x260\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #0 (\u0026amp;tcp_ses-\u0026gt;srv_lock){+.+.}-{3:3}:\n       check_noncircular+0x95/0xc0\n       check_prev_add+0x115/0x2f0\n       validate_chain+0x1cf/0x270\n       __lock_acquire+0x60e/0x780\n       lock_acquire.part.0+0xb4/0x1f0\n       _raw_spin_lock+0x2f/0x40\n       cifs_signal_cifsd_for_reconnect+0x134/0x200\n       __cifs_reconnect+0x8f/0x500\n       cifs_handle_standard+0x112/0x280\n       cifs_demultiplex_thread+0x64d/0xbc0\n       kthread+0x2f7/0x310\n       ret_from_fork+0x2a/0x230\n       ret_from_fork_asm+0x1a/0x30\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;tcp_ses-\u0026gt;srv_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;ses_lock --\u0026gt; \u0026amp;ret_buf-\u0026gt;chan_lock\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;ses_lock);\n                               lock(\u0026amp;ret_buf-\u0026gt;chan_lock);\n  lock(\u0026amp;tcp_ses-\u0026gt;srv_lock);\n\n *** DEADLOCK ***\n\n3 locks held by cifsd/6055:\n #0: ffffffff857de398 (\u0026amp;cifs_tcp_ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x7b/0x200\n #1: ffff888119c64060 (\u0026amp;ret_buf-\u0026gt;ses_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0x9c/0x200\n #2: ffff888119c64330 (\u0026amp;ret_buf-\u0026gt;chan_lock){+.+.}-{3:3}, at: cifs_signal_cifsd_for_reconnect+0xcf/0x200(CVE-2025-38244)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsoftware node: Correct a OOB check in software_node_get_reference_args()\n\nsoftware_node_get_reference_args() wants to get @index-th element, so\nthe property value requires at least \u0026apos;(index + 1) * sizeof(*ref)\u0026apos; bytes\nbut that can not be guaranteed by current OOB check, and may cause OOB\nfor malformed property.\n\nFix by using as OOB check \u0026apos;((index + 1) * sizeof(*ref) \u0026gt; prop-\u0026gt;length)\u0026apos;.(CVE-2025-38342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN\n\nWe found a few different systems hung up in writeback waiting on the same\npage lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in\npnfs_update_layout(), however the pnfs_layout_hdr\u0026apos;s plh_outstanding count\nwas zero.\n\nIt seems most likely that this is another race between the waiter and waker\nsimilar to commit ed0172af5d6f (\u0026quot;SUNRPC: Fix a race to wake a sync task\u0026quot;).\nFix it up by applying the advised barrier.(CVE-2025-38393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Reject SEV{-ES} intra host migration if vCPU creation is in-flight\n\nReject migration of SEV{-ES} state if either the source or destination VM\nis actively creating a vCPU, i.e. if kvm_vm_ioctl_create_vcpu() is in the\nsection between incrementing created_vcpus and online_vcpus.  The bulk of\nvCPU creation runs _outside_ of kvm-\u0026gt;lock to allow creating multiple vCPUs\nin parallel, and so sev_info.es_active can get toggled from false=\u0026gt;true in\nthe destination VM after (or during) svm_vcpu_create(), resulting in an\nSEV{-ES} VM effectively having a non-SEV{-ES} vCPU.\n\nThe issue manifests most visibly as a crash when trying to free a vCPU\u0026apos;s\nNULL VMSA page in an SEV-ES VM, but any number of things can go wrong.\n\n  BUG: unable to handle page fault for address: ffffebde00000000\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP KASAN NOPTI\n  CPU: 227 UID: 0 PID: 64063 Comm: syz.5.60023 Tainted: G     U     O        6.15.0-smp-DEV #2 NONE\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.52.0-0 10/28/2024\n  RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:206 [inline]\n  RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:238 [inline]\n  RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]\n  RIP: 0010:PageHead include/linux/page-flags.h:866 [inline]\n  RIP: 0010:___free_pages+0x3e/0x120 mm/page_alloc.c:5067\n  Code: \u0026lt;49\u0026gt; f7 06 40 00 00 00 75 05 45 31 ff eb 0c 66 90 4c 89 f0 4c 39 f0\n  RSP: 0018:ffff8984551978d0 EFLAGS: 00010246\n  RAX: 0000777f80000001 RBX: 0000000000000000 RCX: ffffffff918aeb98\n  RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffebde00000000\n  RBP: 0000000000000000 R08: ffffebde00000007 R09: 1ffffd7bc0000000\n  R10: dffffc0000000000 R11: fffff97bc0000001 R12: dffffc0000000000\n  R13: ffff8983e19751a8 R14: ffffebde00000000 R15: 1ffffd7bc0000000\n  FS:  0000000000000000(0000) GS:ffff89ee661d3000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: ffffebde00000000 CR3: 000000793ceaa000 CR4: 0000000000350ef0\n  DR0: 0000000000000000 DR1: 0000000000000b5f DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   sev_free_vcpu+0x413/0x630 arch/x86/kvm/svm/sev.c:3169\n   svm_vcpu_free+0x13a/0x2a0 arch/x86/kvm/svm/svm.c:1515\n   kvm_arch_vcpu_destroy+0x6a/0x1d0 arch/x86/kvm/x86.c:12396\n   kvm_vcpu_destroy virt/kvm/kvm_main.c:470 [inline]\n   kvm_destroy_vcpus+0xd1/0x300 virt/kvm/kvm_main.c:490\n   kvm_arch_destroy_vm+0x636/0x820 arch/x86/kvm/x86.c:12895\n   kvm_put_kvm+0xb8e/0xfb0 virt/kvm/kvm_main.c:1310\n   kvm_vm_release+0x48/0x60 virt/kvm/kvm_main.c:1369\n   __fput+0x3e4/0x9e0 fs/file_table.c:465\n   task_work_run+0x1a9/0x220 kernel/task_work.c:227\n   exit_task_work include/linux/task_work.h:40 [inline]\n   do_exit+0x7f0/0x25b0 kernel/exit.c:953\n   do_group_exit+0x203/0x2d0 kernel/exit.c:1102\n   get_signal+0x1357/0x1480 kernel/signal.c:3034\n   arch_do_signal_or_restart+0x40/0x690 arch/x86/kernel/signal.c:337\n   exit_to_user_mode_loop kernel/entry/common.c:111 [inline]\n   exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]\n   __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]\n   syscall_exit_to_user_mode+0x67/0xb0 kernel/entry/common.c:218\n   do_syscall_64+0x7c/0x150 arch/x86/entry/syscall_64.c:100\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7f87a898e969\n   \u0026lt;/TASK\u0026gt;\n  Modules linked in: gq(O)\n  gsmi: Log Shutdown Reason 0x03\n  CR2: ffffebde00000000\n  ---[ end trace 0000000000000000 ]---\n\nDeliberately don\u0026apos;t check for a NULL VMSA when freeing the vCPU, as crashing\nthe host is likely desirable due to the VMSA being consumed by hardware.\nE.g. if KVM manages to allow VMRUN on the vCPU, hardware may read/write a\nbogus VMSA page.  Accessing P\n---truncated---(CVE-2025-38455)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Abort __tc_modify_qdisc if parent class does not exist\n\nLion\u0026apos;s patch [1] revealed an ancient bug in the qdisc API.\nWhenever a user creates/modifies a qdisc specifying as a parent another\nqdisc, the qdisc API will, during grafting, detect that the user is\nnot trying to attach to a class and reject. However grafting is\nperformed after qdisc_create (and thus the qdiscs\u0026apos; init callback) is\nexecuted. In qdiscs that eventually call qdisc_tree_reduce_backlog\nduring init or change (such as fq, hhf, choke, etc), an issue\narises. For example, executing the following commands:\n\nsudo tc qdisc add dev lo root handle a: htb default 2\nsudo tc qdisc add dev lo parent a: handle beef fq\n\nQdiscs such as fq, hhf, choke, etc unconditionally invoke\nqdisc_tree_reduce_backlog() in their control path init() or change() which\nthen causes a failure to find the child class; however, that does not stop\nthe unconditional invocation of the assumed child qdisc\u0026apos;s qlen_notify with\na null class. All these qdiscs make the assumption that class is non-null.\n\nThe solution is ensure that qdisc_leaf() which looks up the parent\nclass, and is invoked prior to qdisc_create(), should return failure on\nnot finding the class.\nIn this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the\nparentid doesn\u0026apos;t correspond to a class, so that we can detect it\nearlier on and abort before qdisc_create is called.\n\n[1] https://lore.kernel.org/netdev/(CVE-2025-38457)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Prevent ALIGN() overflow\n\nWhen allocating IOVA the candidate range gets aligned to the target\nalignment. If the range is close to ULONG_MAX then the ALIGN() can\nwrap resulting in a corrupted iova.\n\nOpen code the ALIGN() using get_add_overflow() to prevent this.\nThis simplifies the checks as we don\u0026apos;t need to check for length earlier\neither.\n\nConsolidate the two copies of this code under a single helper.\n\nThis bug would allow userspace to create a mapping that overlaps with some\nother mapping or a reserved range.(CVE-2025-38688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: upper bound check of tree index in dbAllocAG\n\nWhen computing the tree index in dbAllocAG, we never check if we are\nout of bounds realative to the size of the stree.\nThis could happen in a scenario where the filesystem metadata are\ncorrupted.(CVE-2025-38697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: don\u0026apos;t use BUG_ON() in hfsplus_create_attributes_file()\n\nWhen the volume header contains erroneous values that do not reflect\nthe actual state of the filesystem, hfsplus_fill_super() assumes that\nthe attributes file is not yet created, which later results in hitting\nBUG_ON() when hfsplus_create_attributes_file() is called. Replace this\nBUG_ON() with -EIO error with a message to suggest running fsck tool.(CVE-2025-38712)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n\nThe hfsplus_readdir() method is capable to crash by calling\nhfsplus_uni2asc():\n\n[  667.121659][ T9805] ==================================================================\n[  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10\n[  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805\n[  667.124578][ T9805]\n[  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)\n[  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  667.124890][ T9805] Call Trace:\n[  667.124893][ T9805]  \u0026lt;TASK\u0026gt;\n[  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0\n[  667.124911][ T9805]  print_report+0xd0/0x660\n[  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610\n[  667.124928][ T9805]  ? __phys_addr+0xe8/0x180\n[  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124942][ T9805]  kasan_report+0xc6/0x100\n[  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10\n[  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10\n[  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360\n[  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0\n[  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10\n[  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0\n[  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0\n[  667.125022][ T9805]  ? lock_acquire+0x30/0x80\n[  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20\n[  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0\n[  667.125044][ T9805]  ? putname+0x154/0x1a0\n[  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10\n[  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0\n[  667.125069][ T9805]  iterate_dir+0x296/0xb20\n[  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10\n[  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200\n[  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10\n[  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0\n[  667.125143][ T9805]  do_syscall_64+0xc9/0x480\n[  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9\n[  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48\n[  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9\n[  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9\n[  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004\n[  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110\n[  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260\n[  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  667.125207][ T9805]  \u0026lt;/TASK\u0026gt;\n[  667.125210][ T9805]\n[  667.145632][ T9805] Allocated by task 9805:\n[  667.145991][ T9805]  kasan_save_stack+0x20/0x40\n[  667.146352][ T9805]  kasan_save_track+0x14/0x30\n[  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0\n[  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550\n[  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0\n[  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0\n[  667.148174][ T9805]  iterate_dir+0x296/0xb20\n[  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0\n[  667.148937][ T9805]  do_syscall_64+0xc9/0x480\n[  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  667.149809][ T9805]\n[  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000\n[  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048\n[  667.151282][ T9805] The buggy address is located 0 bytes to the right of\n[  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)\n[  667.1\n---truncated---(CVE-2025-38713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()\n\nThe hfsplus_bnode_read() method can trigger the issue:\n\n[  174.852007][ T9784] ==================================================================\n[  174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360\n[  174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784\n[  174.854059][ T9784]\n[  174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)\n[  174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  174.854286][ T9784] Call Trace:\n[  174.854289][ T9784]  \u0026lt;TASK\u0026gt;\n[  174.854292][ T9784]  dump_stack_lvl+0x10e/0x1f0\n[  174.854305][ T9784]  print_report+0xd0/0x660\n[  174.854315][ T9784]  ? __virt_addr_valid+0x81/0x610\n[  174.854323][ T9784]  ? __phys_addr+0xe8/0x180\n[  174.854330][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854337][ T9784]  kasan_report+0xc6/0x100\n[  174.854346][ T9784]  ? hfsplus_bnode_read+0x2f4/0x360\n[  174.854354][ T9784]  hfsplus_bnode_read+0x2f4/0x360\n[  174.854362][ T9784]  hfsplus_bnode_dump+0x2ec/0x380\n[  174.854370][ T9784]  ? __pfx_hfsplus_bnode_dump+0x10/0x10\n[  174.854377][ T9784]  ? hfsplus_bnode_write_u16+0x83/0xb0\n[  174.854385][ T9784]  ? srcu_gp_start+0xd0/0x310\n[  174.854393][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854402][ T9784]  hfsplus_brec_remove+0x3d2/0x4e0\n[  174.854411][ T9784]  __hfsplus_delete_attr+0x290/0x3a0\n[  174.854419][ T9784]  ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10\n[  174.854427][ T9784]  ? __pfx___hfsplus_delete_attr+0x10/0x10\n[  174.854436][ T9784]  ? __asan_memset+0x23/0x50\n[  174.854450][ T9784]  hfsplus_delete_all_attrs+0x262/0x320\n[  174.854459][ T9784]  ? __pfx_hfsplus_delete_all_attrs+0x10/0x10\n[  174.854469][ T9784]  ? rcu_is_watching+0x12/0xc0\n[  174.854476][ T9784]  ? __mark_inode_dirty+0x29e/0xe40\n[  174.854483][ T9784]  hfsplus_delete_cat+0x845/0xde0\n[  174.854493][ T9784]  ? __pfx_hfsplus_delete_cat+0x10/0x10\n[  174.854507][ T9784]  hfsplus_unlink+0x1ca/0x7c0\n[  174.854516][ T9784]  ? __pfx_hfsplus_unlink+0x10/0x10\n[  174.854525][ T9784]  ? down_write+0x148/0x200\n[  174.854532][ T9784]  ? __pfx_down_write+0x10/0x10\n[  174.854540][ T9784]  vfs_unlink+0x2fe/0x9b0\n[  174.854549][ T9784]  do_unlinkat+0x490/0x670\n[  174.854557][ T9784]  ? __pfx_do_unlinkat+0x10/0x10\n[  174.854565][ T9784]  ? __might_fault+0xbc/0x130\n[  174.854576][ T9784]  ? getname_flags.part.0+0x1c5/0x550\n[  174.854584][ T9784]  __x64_sys_unlink+0xc5/0x110\n[  174.854592][ T9784]  do_syscall_64+0xc9/0x480\n[  174.854600][ T9784]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[  174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167\n[  174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08\n[  174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057\n[  174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167\n[  174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50\n[  174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40\n[  174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0\n[  174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[  174.854658][ T9784]  \u0026lt;/TASK\u0026gt;\n[  174.854661][ T9784]\n[  174.879281][ T9784] Allocated by task 9784:\n[  174.879664][ T9784]  kasan_save_stack+0x20/0x40\n[  174.880082][ T9784]  kasan_save_track+0x14/0x30\n[  174.880500][ T9784]  __kasan_kmalloc+0xaa/0xb0\n[  174.880908][ T9784]  __kmalloc_noprof+0x205/0x550\n[  174.881337][ T9784]  __hfs_bnode_create+0x107/0x890\n[  174.881779][ T9784]  hfsplus_bnode_find+0x2d0/0xd10\n[  174.882222][ T9784]  hfsplus_brec_find+0x2b0/0x520\n[  174.882659][ T9784]  hfsplus_delete_all_attrs+0x23b/0x3\n---truncated---(CVE-2025-38714)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb3: fix for slab out of bounds on mount to ksmbd\n\nWith KASAN enabled, it is possible to get a slab out of bounds\nduring mount to ksmbd due to missing check in parse_server_interfaces()\n(see below):\n\n BUG: KASAN: slab-out-of-bounds in\n parse_server_interfaces+0x14ee/0x1880 [cifs]\n Read of size 4 at addr ffff8881433dba98 by task mount/9827\n\n CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G\n OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)\n Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,\n BIOS 2.13.1 06/14/2019\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x9f/0xf0\n print_report+0xd1/0x670\n __virt_addr_valid+0x22c/0x430\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? kasan_complete_mode_report_info+0x2a/0x1f0\n ? parse_server_interfaces+0x14ee/0x1880 [cifs]\n   kasan_report+0xd6/0x110\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n   __asan_report_load_n_noabort+0x13/0x20\n   parse_server_interfaces+0x14ee/0x1880 [cifs]\n ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]\n ? trace_hardirqs_on+0x51/0x60\n SMB3_request_interfaces+0x1ad/0x3f0 [cifs]\n ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]\n ? SMB2_tcon+0x23c/0x15d0 [cifs]\n smb3_qfs_tcon+0x173/0x2b0 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_get_tcon+0x105d/0x2120 [cifs]\n ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]\n cifs_mount_get_tcon+0x369/0xb90 [cifs]\n ? dfs_cache_find+0xe7/0x150 [cifs]\n dfs_mount_share+0x985/0x2970 [cifs]\n ? check_path.constprop.0+0x28/0x50\n ? save_trace+0x54/0x370\n ? __pfx_dfs_mount_share+0x10/0x10 [cifs]\n ? __lock_acquire+0xb82/0x2ba0\n ? __kasan_check_write+0x18/0x20\n cifs_mount+0xbc/0x9e0 [cifs]\n ? __pfx_cifs_mount+0x10/0x10 [cifs]\n ? do_raw_spin_unlock+0x5d/0x200\n ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]\n cifs_smb3_do_mount+0x263/0x1990 [cifs](CVE-2025-38728)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix refcount leak causing resource not released\n\nWhen ksmbd_conn_releasing(opinfo-\u0026gt;conn) returns true,the refcount was not\ndecremented properly, causing a refcount leak that prevents the count from\nreaching zero and the memory from being released.(CVE-2025-39720)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix filehandle bounds checking in nfs_fh_to_dentry()\n\nThe function needs to check the minimal filehandle length before it can\naccess the embedded filehandle.(CVE-2025-39730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()\n\nA soft lockup warning was observed on a relative small system x86-64\nsystem with 16 GB of memory when running a debug kernel with kmemleak\nenabled.\n\n  watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]\n\nThe test system was running a workload with hot unplug happening in\nparallel.  Then kemleak decided to disable itself due to its inability to\nallocate more kmemleak objects.  The debug kernel has its\nCONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.\n\nThe soft lockup happened in kmemleak_do_cleanup() when the existing\nkmemleak objects were being removed and deleted one-by-one in a loop via a\nworkqueue.  In this particular case, there are at least 40,000 objects\nthat need to be processed and given the slowness of a debug kernel and the\nfact that a raw_spinlock has to be acquired and released in\n__delete_object(), it could take a while to properly handle all these\nobjects.\n\nAs kmemleak has been disabled in this case, the object removal and\ndeletion process can be further optimized as locking isn\u0026apos;t really needed. \nHowever, it is probably not worth the effort to optimize for such an edge\ncase that should rarely happen.  So the simple solution is to call\ncond_resched() at periodic interval in the iteration loop to avoid soft\nlockup.(CVE-2025-39737)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix the setting of capabilities when automounting a new filesystem\n\nCapabilities cannot be inherited when we cross into a new filesystem.\nThey need to be reset to the minimal defaults, and then probed for\nagain.(CVE-2025-39798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: use array_index_nospec with indices that come from guest\n\nmin and dest_id are guest-controlled indices. Using array_index_nospec()\nafter the bounds checks clamps these values to mitigate speculative execution\nside-channels.(CVE-2025-39823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\natm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n\nsyzbot reported the splat below. [0]\n\nWhen atmtcp_v_open() or atmtcp_v_close() is called via connect()\nor close(), atmtcp_send_control() is called to send an in-kernel\nspecial message.\n\nThe message has ATMTCP_HDR_MAGIC in atmtcp_control.hdr.length.\nAlso, a pointer of struct atm_vcc is set to atmtcp_control.vcc.\n\nThe notable thing is struct atmtcp_control is uAPI but has a\nspace for an in-kernel pointer.\n\n  struct atmtcp_control {\n  \tstruct atmtcp_hdr hdr;\t/* must be first */\n  ...\n  \tatm_kptr_t vcc;\t\t/* both directions */\n  ...\n  } __ATM_API_ALIGN;\n\n  typedef struct { unsigned char _[8]; } __ATM_API_ALIGN atm_kptr_t;\n\nThe special message is processed in atmtcp_recv_control() called\nfrom atmtcp_c_send().\n\natmtcp_c_send() is vcc-\u0026gt;dev-\u0026gt;ops-\u0026gt;send() and called from 2 paths:\n\n  1. .ndo_start_xmit() (vcc-\u0026gt;send() == atm_send_aal0())\n  2. vcc_sendmsg()\n\nThe problem is sendmsg() does not validate the message length and\nuserspace can abuse atmtcp_recv_control() to overwrite any kptr\nby atmtcp_control.\n\nLet\u0026apos;s add a new -\u0026gt;pre_send() hook to validate messages from sendmsg().\n\n[0]:\nOops: general protection fault, probably for non-canonical address 0xdffffc00200000ab: 0000 [#1] SMP KASAN PTI\nKASAN: probably user-memory-access in range [0x0000000100000558-0x000000010000055f]\nCPU: 0 UID: 0 PID: 5865 Comm: syz-executor331 Not tainted 6.17.0-rc1-syzkaller-00215-gbab3ce404553 #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025\nRIP: 0010:atmtcp_recv_control drivers/atm/atmtcp.c:93 [inline]\nRIP: 0010:atmtcp_c_send+0x1da/0x950 drivers/atm/atmtcp.c:297\nCode: 4d 8d 75 1a 4c 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 15 06 00 00 41 0f b7 1e 4d 8d b7 60 05 00 00 4c 89 f0 48 c1 e8 03 \u0026lt;42\u0026gt; 0f b6 04 20 84 c0 0f 85 13 06 00 00 66 41 89 1e 4d 8d 75 1c 4c\nRSP: 0018:ffffc90003f5f810 EFLAGS: 00010203\nRAX: 00000000200000ab RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802a510000 RSI: 00000000ffffffff RDI: ffff888030a6068c\nRBP: ffff88802699fb40 R08: ffff888030a606eb R09: 1ffff1100614c0dd\nR10: dffffc0000000000 R11: ffffffff8718fc40 R12: dffffc0000000000\nR13: ffff888030a60680 R14: 000000010000055f R15: 00000000ffffffff\nFS:  00007f8d7e9236c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000045ad50 CR3: 0000000075bde000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n vcc_sendmsg+0xa10/0xc60 net/atm/common.c:645\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x219/0x270 net/socket.c:729\n ____sys_sendmsg+0x505/0x830 net/socket.c:2614\n ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2668\n __sys_sendmsg net/socket.c:2700 [inline]\n __do_sys_sendmsg net/socket.c:2705 [inline]\n __se_sys_sendmsg net/socket.c:2703 [inline]\n __x64_sys_sendmsg+0x19b/0x260 net/socket.c:2703\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f8d7e96a4a9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f8d7e923198 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 00007f8d7e9f4308 RCX: 00007f8d7e96a4a9\nRDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005\nRBP: 00007f8d7e9f4300 R08: 65732f636f72702f R09: 65732f636f72702f\nR10: 65732f636f72702f R11: 0000000000000246 R12: 00007f8d7e9c10ac\nR13: 00007f8d7e9231a0 R14: 0000200000000200 R15: 0000200000000250\n \u0026lt;/TASK\u0026gt;\nModules linked in:(CVE-2025-39828)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix OOB read/write in network-coding decode\n\nbatadv_nc_skb_decode_packet() trusts coded_len and checks only against\nskb-\u0026gt;len. XOR starts at sizeof(struct batadv_unicast_packet), reducing\npayload headroom, and the source skb length is not verified, allowing an\nout-of-bounds read and a small out-of-bounds write.\n\nValidate that coded_len fits within the payload area of both destination\nand source sk_buffs before XORing.(CVE-2025-39839)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix race condition validating r_parent before applying state\n\nAdd validation to ensure the cached parent directory inode matches the\ndirectory info in MDS replies. This prevents client-side race conditions\nwhere concurrent operations (e.g. rename) cause r_parent to become stale\nbetween request initiation and reply processing, which could lead to\napplying state changes to incorrect directory inodes.\n\n[ idryomov: folded a kerneldoc fixup and a follow-up fix from Alex to\n  move CEPH_CAP_PIN reference when r_parent is updated:\n\n  When the parent directory lock is not held, req-\u0026gt;r_parent can become\n  stale and is updated to point to the correct inode.  However, the\n  associated CEPH_CAP_PIN reference was not being adjusted.  The\n  CEPH_CAP_PIN is a reference on an inode that is tracked for\n  accounting purposes.  Moving this pin is important to keep the\n  accounting balanced. When the pin was not moved from the old parent\n  to the new one, it created two problems: The reference on the old,\n  stale parent was never released, causing a reference leak.\n  A reference for the new parent was never acquired, creating the risk\n  of a reference underflow later in ceph_mdsc_release_request().  This\n  patch corrects the logic by releasing the pin from the old parent and\n  acquiring it for the new parent when r_parent is switched.  This\n  ensures reference accounting stays balanced. ](CVE-2025-39927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path\n\nDuring tests of another unrelated patch I was able to trigger this\nerror: Objects remaining on __kmem_cache_shutdown()(CVE-2025-39929)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\num: virtio_uml: Fix use-after-free after put_device in probe\n\nWhen register_virtio_device() fails in virtio_uml_probe(),\nthe code sets vu_dev-\u0026gt;registered = 1 even though\nthe device was not successfully registered.\nThis can lead to use-after-free or other issues.(CVE-2025-39951)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: tuner: xc5000: Fix use-after-free in xc5000_release\n\nThe original code uses cancel_delayed_work() in xc5000_release(), which\ndoes not guarantee that the delayed work item timer_sleep has fully\ncompleted if it was already running. This leads to use-after-free scenarios\nwhere xc5000_release() may free the xc5000_priv while timer_sleep is still\nactive and attempts to dereference the xc5000_priv.\n\nA typical race condition is illustrated below:\n\nCPU 0 (release thread)                 | CPU 1 (delayed work callback)\nxc5000_release()                       | xc5000_do_timer_sleep()\n  cancel_delayed_work()                |\n  hybrid_tuner_release_state(priv)     |\n    kfree(priv)                        |\n                                       |   priv = container_of() // UAF\n\nReplace cancel_delayed_work() with cancel_delayed_work_sync() to ensure\nthat the timer_sleep is properly canceled before the xc5000_priv memory\nis deallocated.\n\nA deadlock concern was considered: xc5000_release() is called in a process\ncontext and is not holding any locks that the timer_sleep work item might\nalso need. Therefore, the use of the _sync() variant is safe here.\n\nThis bug was initially identified through static analysis.\n\n[hverkuil: fix typo in Subject: tunner -\u0026gt; tuner](CVE-2025-39994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Disallow dirty tracking if incoherent page walk\n\nDirty page tracking relies on the IOMMU atomically updating the dirty bit\nin the paging-structure entry. For this operation to succeed, the paging-\nstructure memory must be coherent between the IOMMU and the CPU. In\nanother word, if the iommu page walk is incoherent, dirty page tracking\ndoesn\u0026apos;t work.\n\nThe Intel VT-d specification, Section 3.10 \u0026quot;Snoop Behavior\u0026quot; states:\n\n\u0026quot;Remapping hardware encountering the need to atomically update A/EA/D bits\n in a paging-structure entry that is not snooped will result in a non-\n recoverable fault.\u0026quot;\n\nTo prevent an IOMMU from being incorrectly configured for dirty page\ntracking when it is operating in an incoherent mode, mark SSADS as\nsupported only when both ecap_slads and ecap_smpwc are supported.(CVE-2025-40058)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Define a proc_layoutcommit for the FlexFiles layout type\n\nAvoid a crash if a pNFS client should happen to send a LAYOUTCOMMIT\noperation on a FlexFiles layout.(CVE-2025-40087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: parse_dfs_referrals: prevent oob on malformed input\n\nMalicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS\n\n- reply smaller than sizeof(struct get_dfs_referral_rsp)\n- reply with number of referrals smaller than NumberOfReferrals in the\nheader\n\nProcessing of such replies will cause oob.\n\nReturn -EINVAL error on such replies to prevent oob-s.(CVE-2025-40099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Fix refcount leak for cifs_sb_tlink\n\nFix three refcount inconsistency issues related to `cifs_sb_tlink`.\n\nComments for `cifs_sb_tlink` state that `cifs_put_tlink()` needs to be\ncalled after successful calls to `cifs_sb_tlink()`. Three calls fail to\nupdate refcount accordingly, leading to possible resource leaks.(CVE-2025-40103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix Use-after-free in validation\n\nNodes stored in the validation duplicates hashtable come from an arena\nallocator that is cleared at the end of vmw_execbuf_process. All nodes\nare expected to be cleared in vmw_validation_drop_ht but this node escaped\nbecause its resource was destroyed prematurely.(CVE-2025-40111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Clean up only new IRQ glue on request_irq() failure\n\nThe mlx5_irq_alloc() function can inadvertently free the entire rmap\nand end up in a crash[1] when the other threads tries to access this,\nwhen request_irq() fails due to exhausted IRQ vectors. This commit\nmodifies the cleanup to remove only the specific IRQ mapping that was\njust added.\n\nThis prevents removal of other valid mappings and ensures precise\ncleanup of the failed IRQ allocation\u0026apos;s associated glue object.\n\nNote: This error is observed when both fwctl and rds configs are enabled.\n\n[1]\nmlx5_core 0000:05:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:05:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:06:00.0: Successfully registered panic handler for port 1\nmlx5_core 0000:06:00.0: mlx5_irq_alloc:293:(pid 66740): Failed to\nrequest irq. err = -28\ninfiniband mlx5_0: mlx5_ib_test_wc:290:(pid 66740): Error -28 while\ntrying to test write-combining support\nmlx5_core 0000:06:00.0: Successfully unregistered panic handler for port 1\nmlx5_core 0000:03:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\nmlx5_core 0000:05:00.0: mlx5_irq_alloc:293:(pid 28895): Failed to\nrequest irq. err = -28\ngeneral protection fault, probably for non-canonical address\n0xe277a58fde16f291: 0000 [#1] SMP NOPTI\n\nRIP: 0010:free_irq_cpu_rmap+0x23/0x7d\nCall Trace:\n   \u0026lt;TASK\u0026gt;\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? show_trace_log_lvl+0x1d6/0x2f9\n   ? mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   ? __die_body.cold+0x8/0xa\n   ? die_addr+0x39/0x53\n   ? exc_general_protection+0x1c4/0x3e9\n   ? dev_vprintk_emit+0x5f/0x90\n   ? asm_exc_general_protection+0x22/0x27\n   ? free_irq_cpu_rmap+0x23/0x7d\n   mlx5_irq_alloc.cold+0x5d/0xf3 [mlx5_core]\n   irq_pool_request_vector+0x7d/0x90 [mlx5_core]\n   mlx5_irq_request+0x2e/0xe0 [mlx5_core]\n   mlx5_irq_request_vector+0xad/0xf7 [mlx5_core]\n   comp_irq_request_pci+0x64/0xf0 [mlx5_core]\n   create_comp_eq+0x71/0x385 [mlx5_core]\n   ? mlx5e_open_xdpsq+0x11c/0x230 [mlx5_core]\n   mlx5_comp_eqn_get+0x72/0x90 [mlx5_core]\n   ? xas_load+0x8/0x91\n   mlx5_comp_irqn_get+0x40/0x90 [mlx5_core]\n   mlx5e_open_channel+0x7d/0x3c7 [mlx5_core]\n   mlx5e_open_channels+0xad/0x250 [mlx5_core]\n   mlx5e_open_locked+0x3e/0x110 [mlx5_core]\n   mlx5e_open+0x23/0x70 [mlx5_core]\n   __dev_open+0xf1/0x1a5\n   __dev_change_flags+0x1e1/0x249\n   dev_change_flags+0x21/0x5c\n   do_setlink+0x28b/0xcc4\n   ? __nla_parse+0x22/0x3d\n   ? inet6_validate_link_af+0x6b/0x108\n   ? cpumask_next+0x1f/0x35\n   ? __snmp6_fill_stats64.constprop.0+0x66/0x107\n   ? __nla_validate_parse+0x48/0x1e6\n   __rtnl_newlink+0x5ff/0xa57\n   ? kmem_cache_alloc_trace+0x164/0x2ce\n   rtnl_newlink+0x44/0x6e\n   rtnetlink_rcv_msg+0x2bb/0x362\n   ? __netlink_sendskb+0x4c/0x6c\n   ? netlink_unicast+0x28f/0x2ce\n   ? rtnl_calcit.isra.0+0x150/0x146\n   netlink_rcv_skb+0x5f/0x112\n   netlink_unicast+0x213/0x2ce\n   netlink_sendmsg+0x24f/0x4d9\n   __sock_sendmsg+0x65/0x6a\n   ____sys_sendmsg+0x28f/0x2c9\n   ? import_iovec+0x17/0x2b\n   ___sys_sendmsg+0x97/0xe0\n   __sys_sendmsg+0x81/0xd8\n   do_syscall_64+0x35/0x87\n   entry_SYSCALL_64_after_hwframe+0x6e/0x0\nRIP: 0033:0x7fc328603727\nCode: c3 66 90 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 0b ed\nff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00\nf0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 44 ed ff ff 48\nRSP: 002b:00007ffe8eb3f1a0 EFLAGS: 00000293 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fc328603727\nRDX: 0000000000000000 RSI: 00007ffe8eb3f1f0 RDI: 000000000000000d\nRBP: 00007ffe8eb3f1f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000\nR13: 00000000000\n---truncated---(CVE-2025-40250)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()\n\nThe loops in \u0026apos;qede_tpa_cont()\u0026apos; and \u0026apos;qede_tpa_end()\u0026apos;, iterate\nover \u0026apos;cqe-\u0026gt;len_list[]\u0026apos; using only a zero-length terminator as\nthe stopping condition. If the terminator was missing or\nmalformed, the loop could run past the end of the fixed-size array.\n\nAdd an explicit bound check using ARRAY_SIZE() in both loops to prevent\na potential out-of-bounds access.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-40252)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: sg: Do not sleep in atomic context\n\nsg_finish_rem_req() calls blk_rq_unmap_user(). The latter function may\nsleep. Hence, call sg_finish_rem_req() with interrupts enabled instead\nof disabled.(CVE-2025-40259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: nvme-fc: Ensure -\u0026gt;ioerr_work is cancelled in nvme_fc_delete_ctrl()\n\nnvme_fc_delete_assocation() waits for pending I/O to complete before\nreturning, and an error can cause -\u0026gt;ioerr_work to be queued after\ncancel_work_sync() had been called.  Move the call to cancel_work_sync() to\nbe after nvme_fc_delete_association() to ensure -\u0026gt;ioerr_work is not running\nwhen the nvme_fc_ctrl object is freed.  Otherwise the following can occur:\n\n[ 1135.911754] list_del corruption, ff2d24c8093f31f8-\u0026gt;next is NULL\n[ 1135.917705] ------------[ cut here ]------------\n[ 1135.922336] kernel BUG at lib/list_debug.c:52!\n[ 1135.926784] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[ 1135.931851] CPU: 48 UID: 0 PID: 726 Comm: kworker/u449:23 Kdump: loaded Not tainted 6.12.0 #1 PREEMPT(voluntary)\n[ 1135.943490] Hardware name: Dell Inc. PowerEdge R660/0HGTK9, BIOS 2.5.4 01/16/2025\n[ 1135.950969] Workqueue:  0x0 (nvme-wq)\n[ 1135.954673] RIP: 0010:__list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1135.961041] Code: c7 c7 98 68 72 94 e8 26 45 fe ff 0f 0b 48 c7 c7 70 68 72 94 e8 18 45 fe ff 0f 0b 48 89 fe 48 c7 c7 80 69 72 94 e8 07 45 fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 a0 6a 72 94 48 89 c2 e8 f3 44 fe ff 0f 0b\n[ 1135.979788] RSP: 0018:ff579b19482d3e50 EFLAGS: 00010046\n[ 1135.985015] RAX: 0000000000000033 RBX: ff2d24c8093f31f0 RCX: 0000000000000000\n[ 1135.992148] RDX: 0000000000000000 RSI: ff2d24d6bfa1d0c0 RDI: ff2d24d6bfa1d0c0\n[ 1135.999278] RBP: ff2d24c8093f31f8 R08: 0000000000000000 R09: ffffffff951e2b08\n[ 1136.006413] R10: ffffffff95122ac8 R11: 0000000000000003 R12: ff2d24c78697c100\n[ 1136.013546] R13: fffffffffffffff8 R14: 0000000000000000 R15: ff2d24c78697c0c0\n[ 1136.020677] FS:  0000000000000000(0000) GS:ff2d24d6bfa00000(0000) knlGS:0000000000000000\n[ 1136.028765] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1136.034510] CR2: 00007fd207f90b80 CR3: 000000163ea22003 CR4: 0000000000f73ef0\n[ 1136.041641] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 1136.048776] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[ 1136.055910] PKRU: 55555554\n[ 1136.058623] Call Trace:\n[ 1136.061074]  \u0026lt;TASK\u0026gt;\n[ 1136.063179]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.067540]  ? show_trace_log_lvl+0x1b0/0x2f0\n[ 1136.071898]  ? move_linked_works+0x4a/0xa0\n[ 1136.075998]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.081744]  ? __die_body.cold+0x8/0x12\n[ 1136.085584]  ? die+0x2e/0x50\n[ 1136.088469]  ? do_trap+0xca/0x110\n[ 1136.091789]  ? do_error_trap+0x65/0x80\n[ 1136.095543]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.101289]  ? exc_invalid_op+0x50/0x70\n[ 1136.105127]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.110874]  ? asm_exc_invalid_op+0x1a/0x20\n[ 1136.115059]  ? __list_del_entry_valid_or_report.cold+0xf/0x6f\n[ 1136.120806]  move_linked_works+0x4a/0xa0\n[ 1136.124733]  worker_thread+0x216/0x3a0\n[ 1136.128485]  ? __pfx_worker_thread+0x10/0x10\n[ 1136.132758]  kthread+0xfa/0x240\n[ 1136.135904]  ? __pfx_kthread+0x10/0x10\n[ 1136.139657]  ret_from_fork+0x31/0x50\n[ 1136.143236]  ? __pfx_kthread+0x10/0x10\n[ 1136.146988]  ret_from_fork_asm+0x1a/0x30\n[ 1136.150915]  \u0026lt;/TASK\u0026gt;(CVE-2025-40261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbe2net: pass wrb_params in case of OS2BMC\n\nbe_insert_vlan_in_pkt() is called with the wrb_params argument being NULL\nat be_send_pkt_to_bmc() call site.  This may lead to dereferencing a NULL\npointer when processing a workaround for specific packet, as commit\nbc0c3405abbb (\u0026quot;be2net: fix a Tx stall bug caused by a specific ipv6\npacket\u0026quot;) states.\n\nThe correct way would be to pass the wrb_params from be_xmit().(CVE-2025-40264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: client: fix memory leak in smb3_fs_context_parse_param\n\nThe user calls fsconfig twice, but when the program exits, free() only\nfrees ctx-\u0026gt;source for the second fsconfig, not the first.\nRegarding fc-\u0026gt;source, there is no code in the fs context related to its\nmemory reclamation.\n\nTo fix this memory leak, release the source memory corresponding to ctx\nor fc before each parsing.\n\nsyzbot reported:\nBUG: memory leak\nunreferenced object 0xffff888128afa360 (size 96):\n  backtrace (crc 79c9c7ba):\n    kstrdup+0x3c/0x80 mm/util.c:84\n    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444\n\nBUG: memory leak\nunreferenced object 0xffff888112c7d900 (size 96):\n  backtrace (crc 79c9c7ba):\n    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629\n    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438(CVE-2025-40268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: free copynotify stateid in nfs4_free_ol_stateid()\n\nTypically copynotify stateid is freed either when parent\u0026apos;s stateid\nis being close/freed or in nfsd4_laundromat if the stateid hasn\u0026apos;t\nbeen used in a lease period.\n\nHowever, in case when the server got an OPEN (which created\na parent stateid), followed by a COPY_NOTIFY using that stateid,\nfollowed by a client reboot. New client instance while doing\nCREATE_SESSION would force expire previous state of this client.\nIt leads to the open state being freed thru release_openowner-\u0026gt;\nnfs4_free_ol_stateid() and it finds that it still has copynotify\nstateid associated with it. We currently print a warning and is\ntriggerred\n\nWARNING: CPU: 1 PID: 8858 at fs/nfsd/nfs4state.c:1550 nfs4_free_ol_stateid+0xb0/0x100 [nfsd]\n\nThis patch, instead, frees the associated copynotify stateid here.\n\nIf the parent stateid is freed (without freeing the copynotify\nstateids associated with it), it leads to the list corruption\nwhen laundromat ends up freeing the copynotify state later.\n\n[ 1626.839430] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[ 1626.842828] Modules linked in: nfnetlink_queue nfnetlink_log bluetooth cfg80211 rpcrdma rdma_cm iw_cm ib_cm ib_core nfsd nfs_acl lockd grace nfs_localio ext4 crc16 mbcache jbd2 overlay uinput snd_seq_dummy snd_hrtimer qrtr rfkill vfat fat uvcvideo snd_hda_codec_generic videobuf2_vmalloc videobuf2_memops snd_hda_intel uvc snd_intel_dspcfg videobuf2_v4l2 videobuf2_common snd_hda_codec snd_hda_core videodev snd_hwdep snd_seq mc snd_seq_device snd_pcm snd_timer snd soundcore sg loop auth_rpcgss vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vmw_vmci vsock xfs 8021q garp stp llc mrp nvme ghash_ce e1000e nvme_core sr_mod nvme_keyring nvme_auth cdrom vmwgfx drm_ttm_helper ttm sunrpc dm_mirror dm_region_hash dm_log iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse dm_multipath dm_mod nfnetlink\n[ 1626.855594] CPU: 2 UID: 0 PID: 199 Comm: kworker/u24:33 Kdump: loaded Tainted: G    B   W           6.17.0-rc7+ #22 PREEMPT(voluntary)\n[ 1626.857075] Tainted: [B]=BAD_PAGE, [W]=WARN\n[ 1626.857573] Hardware name: VMware, Inc. VMware20,1/VBSA, BIOS VMW201.00V.24006586.BA64.2406042154 06/04/2024\n[ 1626.858724] Workqueue: nfsd4 laundromat_main [nfsd]\n[ 1626.859304] pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 1626.860010] pc : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.860601] lr : __list_del_entry_valid_or_report+0x148/0x200\n[ 1626.861182] sp : ffff8000881d7a40\n[ 1626.861521] x29: ffff8000881d7a40 x28: 0000000000000018 x27: ffff0000c2a98200\n[ 1626.862260] x26: 0000000000000600 x25: 0000000000000000 x24: ffff8000881d7b20\n[ 1626.862986] x23: ffff0000c2a981e8 x22: 1fffe00012410e7d x21: ffff0000920873e8\n[ 1626.863701] x20: ffff0000920873e8 x19: ffff000086f22998 x18: 0000000000000000\n[ 1626.864421] x17: 20747562202c3839 x16: 3932326636383030 x15: 3030666666662065\n[ 1626.865092] x14: 6220646c756f6873 x13: 0000000000000001 x12: ffff60004fd9e4a3\n[ 1626.865713] x11: 1fffe0004fd9e4a2 x10: ffff60004fd9e4a2 x9 : dfff800000000000\n[ 1626.866320] x8 : 00009fffb0261b5e x7 : ffff00027ecf2513 x6 : 0000000000000001\n[ 1626.866938] x5 : ffff00027ecf2510 x4 : ffff60004fd9e4a3 x3 : 0000000000000000\n[ 1626.867553] x2 : 0000000000000000 x1 : ffff000096069640 x0 : 000000000000006d\n[ 1626.868167] Call trace:\n[ 1626.868382]  __list_del_entry_valid_or_report+0x148/0x200 (P)\n[ 1626.868876]  _free_cpntf_state_locked+0xd0/0x268 [nfsd]\n[ 1626.869368]  nfs4_laundromat+0x6f8/0x1058 [nfsd]\n[ 1626.869813]  laundromat_main+0x24/0x60 [nfsd]\n[ 1626.870231]  process_one_work+0x584/0x1050\n[ 1626.870595]  worker_thread+0x4c4/0xc60\n[ 1626.870893]  kthread+0x2f8/0x398\n[ 1626.871146]  ret_from_fork+0x10/0x20\n[ 1626.871422] Code: aa1303e1 aa1403e3 910e8000 97bc55d7 (d4210000)\n[ 1626.871892] SMP: stopping secondary CPUs(CVE-2025-40273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: cancel mesh send timer when hdev removed\n\nmesh_send_done timer is not canceled when hdev is removed, which causes\ncrash if the timer triggers after hdev is gone.\n\nCancel the timer when MGMT removes the hdev, like other MGMT timers.\n\nShould fix the BUG: sporadically seen by BlueZ test bot\n(in \u0026quot;Mesh - Send cancel - 1\u0026quot; test).\n\nLog:\n------\nBUG: KASAN: slab-use-after-free in run_timer_softirq+0x76b/0x7d0\n...\nFreed by task 36:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x43/0x70\n kfree+0x103/0x500\n device_release+0x9a/0x210\n kobject_put+0x100/0x1e0\n vhci_release+0x18b/0x240\n------(CVE-2025-40284)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n\nAdd bounds checking to prevent writes past framebuffer boundaries when\nrendering text near screen edges. Return early if the Y position is off-screen\nand clip image height to screen boundary. Break from the rendering loop if the\nX position is off-screen. When clipping image width to fit the screen, update\nthe character count to match the clipped width to prevent buffer size\nmismatches.\n\nWithout the character count update, bit_putcs_aligned and bit_putcs_unaligned\nreceive mismatched parameters where the buffer is allocated for the clipped\nwidth but cnt reflects the original larger count, causing out-of-bounds writes.(CVE-2025-40304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naccel/habanalabs: support mapping cb with vmalloc-backed coherent memory\n\nWhen IOMMU is enabled, dma_alloc_coherent() with GFP_USER may return\naddresses from the vmalloc range. If such an address is mapped without\nVM_MIXEDMAP, vm_insert_page() will trigger a BUG_ON due to the\nVM_PFNMAP restriction.\n\nFix this by checking for vmalloc addresses and setting VM_MIXEDMAP\nin the VMA before mapping. This ensures safe mapping and avoids kernel\ncrashes. The memory is still driver-allocated and cannot be accessed\ndirectly by userspace.(CVE-2025-40311)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget\n\nIn the __cdnsp_gadget_init() and cdnsp_gadget_exit() functions, the gadget\nstructure (pdev-\u0026gt;gadget) was freed before its endpoints.\nThe endpoints are linked via the ep_list in the gadget structure.\nFreeing the gadget first leaves dangling pointers in the endpoint list.\nWhen the endpoints are subsequently freed, this results in a use-after-free.\n\nFix:\nBy separating the usb_del_gadget_udc() operation into distinct \u0026quot;del\u0026quot; and\n\u0026quot;put\u0026quot; steps, cdnsp_gadget_free_endpoints() can be executed prior to the\nfinal release of the gadget structure with usb_put_gadget().\n\nA patch similar to bb9c74a5bd14(\u0026quot;usb: dwc3: gadget: Free gadget structure\n only after freeing endpoints\u0026quot;).(CVE-2025-40314)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Sync pending IRQ work before freeing ring buffer\n\nFix a race where irq_work can be queued in bpf_ringbuf_commit()\nbut the ring buffer is freed before the work executes.\nIn the syzbot reproducer, a BPF program attached to sched_switch\ntriggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer\nis freed before this work executes, the irq_work thread may accesses\nfreed memory.\nCalling `irq_work_sync(\u0026amp;rb-\u0026gt;work)` ensures that all pending irq_work\ncomplete before freeing the buffer.(CVE-2025-40319)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential cfid UAF in smb2_query_info_compound\n\nWhen smb2_query_info_compound() retries, a previously allocated cfid may\nhave been freed in the first attempt.\nBecause cfid wasn\u0026apos;t reset on replay, later cleanup could act on a stale\npointer, leading to a potential use-after-free.\n\nReinitialize cfid to NULL under the replay label.\n\nExample trace (trimmed):\n\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110\n[...]\nRIP: 0010:refcount_warn_saturate+0x9c/0x110\n[...]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? step_into+0x10d/0x690\n ? __legitimize_path+0x28/0x60\n smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n ? kmem_cache_alloc+0x18a/0x340\n ? getname_flags+0x46/0x1e0\n cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f]\n statfs_by_dentry+0x67/0x90\n vfs_statfs+0x16/0xd0\n user_statfs+0x54/0xa0\n __do_sys_statfs+0x20/0x50\n do_syscall_64+0x58/0x80(CVE-2025-40320)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbdev: bitblit: bound-check glyph index in bit_putcs*\n\nbit_putcs_aligned()/unaligned() derived the glyph pointer from the\ncharacter value masked by 0xff/0x1ff, which may exceed the actual font\u0026apos;s\nglyph count and read past the end of the built-in font array.\nClamp the index to the actual glyph count before computing the address.\n\nThis fixes a global out-of-bounds read reported by syzbot.(CVE-2025-40322)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Fix crash in nfsd4_read_release()\n\nWhen tracing is enabled, the trace_nfsd_read_done trace point\ncrashes during the pynfs read.testNoFh test.(CVE-2025-40324)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix potential UAF in smb2_close_cached_fid()\n\nfind_or_create_cached_dir() could grab a new reference after kref_put()\nhad seen the refcount drop to zero but before cfid_list_lock is acquired\nin smb2_close_cached_fid(), leading to use-after-free.\n\nSwitch to kref_put_lock() so cfid_release() is called with\ncfid_list_lock held, closing that gap.(CVE-2025-40328)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: sddr55: Reject out-of-bound new_pba\n\nDiscovered by Atuin - Automated Vulnerability Discovery Engine.\n\nnew_pba comes from the status packet returned after each write.\nA bogus device could report values beyond the block count derived\nfrom info-\u0026gt;capacity, letting the driver walk off the end of\npba_to_lba[] and corrupt heap memory.\n\nReject PBAs that exceed the computed block count and fail the\ntransfer so we avoid touching out-of-range mapping entries.(CVE-2025-40345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ\n\nXDP programs can change the layout of an xdp_buff through\nbpf_xdp_adjust_tail() and bpf_xdp_adjust_head(). Therefore, the driver\ncannot assume the size of the linear data area nor fragments. Fix the\nbug in mlx5 by generating skb according to xdp_buff after XDP programs\nrun.\n\nCurrently, when handling multi-buf XDP, the mlx5 driver assumes the\nlayout of an xdp_buff to be unchanged. That is, the linear data area\ncontinues to be empty and fragments remain the same. This may cause\nthe driver to generate erroneous skb or triggering a kernel\nwarning. When an XDP program added linear data through\nbpf_xdp_adjust_head(), the linear data will be ignored as\nmlx5e_build_linear_skb() builds an skb without linear data and then\npull data from fragments to fill the linear data area. When an XDP\nprogram has shrunk the non-linear data through bpf_xdp_adjust_tail(),\nthe delta passed to __pskb_pull_tail() may exceed the actual nonlinear\ndata size and trigger the BUG_ON in it.\n\nTo fix the issue, first record the original number of fragments. If the\nnumber of fragments changes after the XDP program runs, rewind the end\nfragment pointer by the difference and recalculate the truesize. Then,\nbuild the skb with the linear data area matching the xdp_buff. Finally,\nonly pull data in if there is non-linear data and fill the linear part\nup to 256 bytes.(CVE-2025-40350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sysfb: Do not dereference NULL pointer in plane reset\n\nThe plane state in __drm_gem_reset_shadow_plane() can be NULL. Do not\nderef that pointer, but forward NULL to the other plane-reset helpers.\nClears plane-\u0026gt;state to NULL.\n\nv2:\n- fix typo in commit description (Javier)(CVE-2025-40360)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix field-spanning memcpy warning in AH output\n\nFix field-spanning memcpy warnings in ah6_output() and\nah6_output_done() where extension headers are copied to/from IPv6\naddress fields, triggering fortify-string warnings about writes beyond\nthe 16-byte address fields.\n\n  memcpy: detected field-spanning write (size 40) of single field \u0026quot;\u0026amp;top_iph-\u0026gt;saddr\u0026quot; at net/ipv6/ah6.c:439 (size 16)\n  WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_output+0xe7e/0x14e0 net/ipv6/ah6.c:439\n\nThe warnings are false positives as the extension headers are\nintentionally placed after the IPv6 header in memory. Fix by properly\ncopying addresses and extension headers separately, and introduce\nhelper functions to avoid code duplication.(CVE-2025-40363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: fix possible deadlock while configuring policy\n\nFollowing deadlock can be triggered easily by lockdep:\n\nWARNING: possible circular locking dependency detected\n6.17.0-rc3-00124-ga12c2658ced0 #1665 Not tainted\n------------------------------------------------------\ncheck/1334 is trying to acquire lock:\nff1100011d9d0678 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}, at: blk_unregister_queue+0x53/0x180\n\nbut task is already holding lock:\nff1100011d9d00e0 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}, at: del_gendisk+0xba/0x110\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-\u0026gt; #2 (\u0026amp;q-\u0026gt;q_usage_counter(queue)#3){++++}-{0:0}:\n       blk_queue_enter+0x40b/0x470\n       blkg_conf_prep+0x7b/0x3c0\n       tg_set_limit+0x10a/0x3e0\n       cgroup_file_write+0xc6/0x420\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n-\u0026gt; #1 (\u0026amp;q-\u0026gt;rq_qos_mutex){+.+.}-{4:4}:\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       wbt_init+0x17e/0x280\n       wbt_enable_default+0xe9/0x140\n       blk_register_queue+0x1da/0x2e0\n       __add_disk+0x38c/0x5d0\n       add_disk_fwnode+0x89/0x250\n       device_add_disk+0x18/0x30\n       virtblk_probe+0x13a3/0x1800\n       virtio_dev_probe+0x389/0x610\n       really_probe+0x136/0x620\n       __driver_probe_device+0xb3/0x230\n       driver_probe_device+0x2f/0xe0\n       __driver_attach+0x158/0x250\n       bus_for_each_dev+0xa9/0x130\n       driver_attach+0x26/0x40\n       bus_add_driver+0x178/0x3d0\n       driver_register+0x7d/0x1c0\n       __register_virtio_driver+0x2c/0x60\n       virtio_blk_init+0x6f/0xe0\n       do_one_initcall+0x94/0x540\n       kernel_init_freeable+0x56a/0x7b0\n       kernel_init+0x2b/0x270\n       ret_from_fork+0x268/0x4c0\n       ret_from_fork_asm+0x1a/0x30\n\n-\u0026gt; #0 (\u0026amp;q-\u0026gt;sysfs_lock){+.+.}-{4:4}:\n       __lock_acquire+0x1835/0x2940\n       lock_acquire+0xf9/0x450\n       __mutex_lock+0xd8/0xf50\n       mutex_lock_nested+0x2b/0x40\n       blk_unregister_queue+0x53/0x180\n       __del_gendisk+0x226/0x690\n       del_gendisk+0xba/0x110\n       sd_remove+0x49/0xb0 [sd_mod]\n       device_remove+0x87/0xb0\n       device_release_driver_internal+0x11e/0x230\n       device_release_driver+0x1a/0x30\n       bus_remove_device+0x14d/0x220\n       device_del+0x1e1/0x5a0\n       __scsi_remove_device+0x1ff/0x2f0\n       scsi_remove_device+0x37/0x60\n       sdev_store_delete+0x77/0x100\n       dev_attr_store+0x1f/0x40\n       sysfs_kf_write+0x65/0x90\n       kernfs_fop_write_iter+0x189/0x280\n       vfs_write+0x256/0x490\n       ksys_write+0x83/0x190\n       __x64_sys_write+0x21/0x30\n       x64_sys_call+0x4608/0x4630\n       do_syscall_64+0xdb/0x6b0\n       entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nother info that might help us debug this:\n\nChain exists of:\n  \u0026amp;q-\u0026gt;sysfs_lock --\u0026gt; \u0026amp;q-\u0026gt;rq_qos_mutex --\u0026gt; \u0026amp;q-\u0026gt;q_usage_counter(queue)#3\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n                               lock(\u0026amp;q-\u0026gt;rq_qos_mutex);\n                               lock(\u0026amp;q-\u0026gt;q_usage_counter(queue)#3);\n  lock(\u0026amp;q-\u0026gt;sysfs_lock);\n\nRoot cause is that queue_usage_counter is grabbed with rq_qos_mutex\nheld in blkg_conf_prep(), while queue should be freezed before\nrq_qos_mutex from other context.\n\nThe blk_queue_enter() from blkg_conf_prep() is used to protect against\npolicy deactivation, which is already protected with blkcg_mutex, hence\nconvert blk_queue_enter() to blkcg_mutex to fix this problem. Meanwhile,\nconsider that blkcg_mutex is held after queue is freezed from policy\ndeactivation, also convert blkg_alloc() to use GFP_NOIO.(CVE-2025-68178)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Disable AFBC support on Mediatek DRM driver\n\nCommit c410fa9b07c3 (\u0026quot;drm/mediatek: Add AFBC support to Mediatek DRM\ndriver\u0026quot;) added AFBC support to Mediatek DRM and enabled the\n32x8/split/sparse modifier.\n\nHowever, this is currently broken on Mediatek MT8188 (Genio 700 EVK\nplatform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by\ndefault since Mesa v25.0.\n\nKernel trace reports vblank timeouts constantly, and the render is garbled:\n\n```\n[CRTC:62:crtc-0] vblank wait timed out\nWARNING: CPU: 7 PID: 70 at drivers/gpu/drm/drm_atomic_helper.c:1835 drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\n[...]\nHardware name: MediaTek Genio-700 EVK (DT)\nWorkqueue: events_unbound commit_work\npstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nlr : drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c\nsp : ffff80008337bca0\nx29: ffff80008337bcd0 x28: 0000000000000061 x27: 0000000000000000\nx26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c9dcc000\nx23: 0000000000000001 x22: 0000000000000000 x21: ffff0000c66f2f80\nx20: ffff0000c0d7d880 x19: 0000000000000000 x18: 000000000000000a\nx17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000000\nx14: 0000000000000000 x13: 74756f2064656d69 x12: 742074696177206b\nx11: 0000000000000058 x10: 0000000000000018 x9 : ffff800082396a70\nx8 : 0000000000057fa8 x7 : 0000000000000cce x6 : ffff8000823eea70\nx5 : ffff0001fef5f408 x4 : ffff80017ccee000 x3 : ffff0000c12cb480\nx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c12cb480\nCall trace:\n drm_atomic_helper_wait_for_vblanks.part.0+0x24c/0x27c (P)\n drm_atomic_helper_commit_tail_rpm+0x64/0x80\n commit_tail+0xa4/0x1a4\n commit_work+0x14/0x20\n process_one_work+0x150/0x290\n worker_thread+0x2d0/0x3ec\n kthread+0x12c/0x210\n ret_from_fork+0x10/0x20\n---[ end trace 0000000000000000 ]---\n```\n\nUntil this gets fixed upstream, disable AFBC support on this platform, as\nit\u0026apos;s currently broken with upstream Mesa.(CVE-2025-68184)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfs4_setup_readdir(): insufficient locking for -\u0026gt;d_parent-\u0026gt;d_inode dereferencing\n\nTheoretically it\u0026apos;s an oopsable race, but I don\u0026apos;t believe one can manage\nto hit it on real hardware; might become doable on a KVM, but it still\nwon\u0026apos;t be easy to attack.\n\nAnyway, it\u0026apos;s easy to deal with - since xdr_encode_hyper() is just a call of\nput_unaligned_be64(), we can put that under -\u0026gt;d_lock and be done with that.(CVE-2025-68185)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: use netdev_warn() instead of netdev_WARN()\n\nnetdev_WARN() uses WARN/WARN_ON to print a backtrace along with\nfile and line information. In this case, udp_tunnel_nic_register()\nreturning an error is just a failed operation, not a kernel bug.\n\nudp_tunnel_nic_register() can fail due to a memory allocation\nfailure (kzalloc() or udp_tunnel_nic_alloc()).\nThis is a normal runtime error and not a kernel bug.\n\nReplace netdev_WARN() with netdev_warn() accordingly.(CVE-2025-68191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk-\u0026gt;open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq.(CVE-2025-68218)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: fix memory leak in smb3_fs_context_parse_param error path\n\nAdd proper cleanup of ctx-\u0026gt;source and fc-\u0026gt;source to the\ncifs_parse_mount_err error handler. This ensures that memory allocated\nfor the source strings is correctly freed on all error paths, matching\nthe cleanup already performed in the success path by\nsmb3_cleanup_fs_context_contents().\nPointers are also set to NULL after freeing to prevent potential\ndouble-free issues.\n\nThis change fixes a memory leak originally detected by syzbot. The\nleak occurred when processing Opt_source mount options if an error\nhappened after ctx-\u0026gt;source and fc-\u0026gt;source were successfully\nallocated but before the function completed.\n\nThe specific leak sequence was:\n1. ctx-\u0026gt;source = smb3_fs_context_fullpath(ctx, \u0026apos;/\u0026apos;) allocates memory\n2. fc-\u0026gt;source = kstrdup(ctx-\u0026gt;source, GFP_KERNEL) allocates more memory\n3. A subsequent error jumps to cifs_parse_mount_err\n4. The old error handler freed passwords but not the source strings,\ncausing the memory to leak.\n\nThis issue was not addressed by commit e8c73eb7db0a (\u0026quot;cifs: client:\nfix memory leak in smb3_fs_context_parse_param\u0026quot;), which only fixed\nleaks from repeated fsconfig() calls but not this error path.\n\nPatch updated with minor change suggested by kernel test robot(CVE-2025-68219)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u0026gt;sh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u0026gt;sh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...(CVE-2025-68229)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access before closing files opened by open_exec()\n\nbm_register_write() opens an executable file using open_exec(), which\ninternally calls do_open_execat() and denies write access on the file to\navoid modification while it is being executed.\n\nHowever, when an error occurs, bm_register_write() closes the file using\nfilp_close() directly. This does not restore the write permission, which\nmay cause subsequent write operations on the same file to fail.\n\nFix this by calling exe_file_allow_write_access() before filp_close() to\nrestore the write permission properly.(CVE-2025-68239)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n\nThe sit driver\u0026apos;s packet transmission path calls: sit_tunnel_xmit() -\u0026gt;\nupdate_or_create_fnhe(), which lead to fnhe_remove_oldest() being called\nto delete entries exceeding FNHE_RECLAIM_DEPTH+random.\n\nThe race window is between fnhe_remove_oldest() selecting fnheX for\ndeletion and the subsequent kfree_rcu(). During this time, the\nconcurrent path\u0026apos;s __mkroute_output() -\u0026gt; find_exception() can fetch the\nsoon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a\nnew dst using a dst_hold(). When the original fnheX is freed via RCU,\nthe dst reference remains permanently leaked.\n\nCPU 0                             CPU 1\n__mkroute_output()\n  find_exception() [fnheX]\n                                  update_or_create_fnhe()\n                                    fnhe_remove_oldest() [fnheX]\n  rt_bind_exception() [bind dst]\n                                  RCU callback [fnheX freed, dst leak]\n\nThis issue manifests as a device reference count leak and a warning in\ndmesg when unregistering the net device:\n\n  unregister_netdevice: waiting for sitX to become free. Usage count = N\n\nIdo Schimmel provided the simple test validation method [1].\n\nThe fix clears \u0026apos;oldest-\u0026gt;fnhe_daddr\u0026apos; before calling fnhe_flush_routes().\nSince rt_bind_exception() checks this field, setting it to zero prevents\nthe stale fnhe from being reused and bound to a new dst just before it\nis freed.\n\n[1]\nip netns add ns1\nip -n ns1 link set dev lo up\nip -n ns1 address add 192.0.2.1/32 dev lo\nip -n ns1 link add name dummy1 up type dummy\nip -n ns1 route add 192.0.2.2/32 dev dummy1\nip -n ns1 link add name gretap1 up arp off type gretap \\\n    local 192.0.2.1 remote 192.0.2.2\nip -n ns1 route add 198.51.0.0/16 dev gretap1\ntaskset -c 0 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\ntaskset -c 2 ip netns exec ns1 mausezahn gretap1 \\\n    -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q \u0026amp;\nsleep 10\nip netns pids ns1 | xargs kill\nip netns del ns1(CVE-2025-68241)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: netpoll: fix incorrect refcount handling causing incorrect cleanup\n\ncommit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) incorrectly\nignored the refcount and prematurely set dev-\u0026gt;npinfo to NULL during\nnetpoll cleanup, leading to improper behavior and memory leaks.\n\nScenario causing lack of proper cleanup:\n\n1) A netpoll is associated with a NIC (e.g., eth0) and netdev-\u0026gt;npinfo is\n   allocated, and refcnt = 1\n   - Keep in mind that npinfo is shared among all netpoll instances. In\n     this case, there is just one.\n\n2) Another netpoll is also associated with the same NIC and\n   npinfo-\u0026gt;refcnt += 1.\n   - Now dev-\u0026gt;npinfo-\u0026gt;refcnt = 2;\n   - There is just one npinfo associated to the netdev.\n\n3) When the first netpolls goes to clean up:\n   - The first cleanup succeeds and clears np-\u0026gt;dev-\u0026gt;npinfo, ignoring\n     refcnt.\n     - It basically calls `RCU_INIT_POINTER(np-\u0026gt;dev-\u0026gt;npinfo, NULL);`\n   - Set dev-\u0026gt;npinfo = NULL, without proper cleanup\n   - No -\u0026gt;ndo_netpoll_cleanup() is either called\n\n4) Now the second target tries to clean up\n   - The second cleanup fails because np-\u0026gt;dev-\u0026gt;npinfo is already NULL.\n     * In this case, ops-\u0026gt;ndo_netpoll_cleanup() was never called, and\n       the skb pool is not cleaned as well (for the second netpoll\n       instance)\n  - This leaks npinfo and skbpool skbs, which is clearly reported by\n    kmemleak.\n\nRevert commit efa95b01da18 (\u0026quot;netpoll: fix use after free\u0026quot;) and adds\nclarifying comments emphasizing that npinfo cleanup should only happen\nonce the refcount reaches zero, ensuring stable and correct netpoll\nbehavior.(CVE-2025-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: avoid infinite loops due to corrupted subpage compact indexes\n\nRobert reported an infinite loop observed by two crafted images.\n\nThe root cause is that `clusterofs` can be larger than `lclustersize`\nfor !NONHEAD `lclusters` in corrupted subpage compact indexes, e.g.:\n\n  blocksize = lclustersize = 512   lcn = 6   clusterofs = 515\n\nMove the corresponding check for full compress indexes to\n`z_erofs_load_lcluster_from_disk()` to also cover subpage compact\ncompress indexes.\n\nIt also fixes the position of `m-\u0026gt;type \u0026gt;= Z_EROFS_LCLUSTER_TYPE_MAX`\ncheck, since it should be placed right after\n`z_erofs_load_{compact,full}_lcluster()`.(CVE-2025-68251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: storage: Fix memory leak in USB bulk transport\n\nA kernel memory leak was identified by the \u0026apos;ioctl_sg01\u0026apos; test from Linux\nTest Project (LTP). The following bytes were mainly observed: 0x53425355.\n\nWhen USB storage devices incorrectly skip the data phase with status data,\nthe code extracts/validates the CSW from the sg buffer, but fails to clear\nit afterwards. This leaves status protocol data in srb\u0026apos;s transfer buffer,\nsuch as the US_BULK_CS_SIGN \u0026apos;USBS\u0026apos; signature observed here. Thus, this can\nlead to USB protocols leaks to user space through SCSI generic (/dev/sg*)\ninterfaces, such as the one seen here when the LTP test requested 512 KiB.\n\nFix the leak by zeroing the CSW data in srb\u0026apos;s transfer buffer immediately\nafter the validation of devices that skip data phase.\n\nNote: Differently from CVE-2018-1000204, which fixed a big leak by zero-\ning pages at allocation time, this leak occurs after allocation, when USB\nprotocol data is written to already-allocated sg pages.(CVE-2025-68288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u0026gt;domainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u0026gt; /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \u0026quot;ls\u0026quot;, pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2025-68295)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup\n\nProtect vga_switcheroo_client_fb_set() with console lock. Avoids OOB\naccess in fbcon_remap_all(). Without holding the console lock the call\nraces with switching outputs.\n\nVGA switcheroo calls fbcon_remap_all() when switching clients. The fbcon\nfunction uses struct fb_info.node, which is set by register_framebuffer().\nAs the fb-helper code currently sets up VGA switcheroo before registering\nthe framebuffer, the value of node is -1 and therefore not a legal value.\nFor example, fbcon uses the value within set_con2fb_map() [1] as an index\ninto an array.\n\nMoving vga_switcheroo_client_fb_set() after register_framebuffer() can\nresult in VGA switching that does not switch fbcon correctly.\n\nTherefore move vga_switcheroo_client_fb_set() under fbcon_fb_registered(),\nwhich already holds the console lock. Fbdev calls fbcon_fb_registered()\nfrom within register_framebuffer(). Serializes the helper with VGA\nswitcheroo\u0026apos;s call to fbcon_remap_all().\n\nAlthough vga_switcheroo_client_fb_set() takes an instance of struct fb_info\nas parameter, it really only needs the contained fbcon state. Moving the\ncall to fbcon initialization is therefore cleaner than before. Only amdgpu,\ni915, nouveau and radeon support vga_switcheroo. For all other drivers,\nthis change does nothing.(CVE-2025-68296)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sock: Prevent race in socket write iter and sock bind\n\nThere is a potential race condition between sock bind and socket write\niter. bind may free the same cmd via mgmt_pending before write iter sends\nthe cmd, just as syzbot reported in UAF[1].\n\nHere we use hci_dev_lock to synchronize the two, thereby avoiding the\nUAF mentioned in [1].\n\n[1]\nsyzbot reported:\nBUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\nRead of size 8 at addr ffff888077164818 by task syz.0.17/5989\nCall Trace:\n mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316\n set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nAllocated by task 5989:\n mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296\n set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910\n hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719\n hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg+0x21c/0x270 net/socket.c:742\n sock_write_iter+0x279/0x360 net/socket.c:1195\n\nFreed by task 5991:\n mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline]\n mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257\n mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477\n hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314(CVE-2025-68305)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump\n\nDo not block PCI config accesses through pci_cfg_access_lock() when\nexecuting the s390 variant of PCI error recovery: Acquire just\ndevice_lock() instead of pci_dev_lock() as powerpc\u0026apos;s EEH and\ngenerig PCI AER processing do.\n\nDuring error recovery testing a pair of tasks was reported to be hung:\n\nmlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working\nINFO: task kmcheck:72 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kmcheck         state:D stack:0     pid:72    tgid:72    ppid:2      flags:0x00000000\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;000000065256f572\u0026gt;] schedule_preempt_disabled+0x22/0x30\n [\u0026lt;0000000652570a94\u0026gt;] __mutex_lock.constprop.0+0x484/0x8a8\n [\u0026lt;000003ff800673a4\u0026gt;] mlx5_unload_one+0x34/0x58 [mlx5_core]\n [\u0026lt;000003ff8006745c\u0026gt;] mlx5_pci_err_detected+0x94/0x140 [mlx5_core]\n [\u0026lt;0000000652556c5a\u0026gt;] zpci_event_attempt_error_recovery+0xf2/0x398\n [\u0026lt;0000000651b9184a\u0026gt;] __zpci_event_error+0x23a/0x2c0\nINFO: task kworker/u1664:6:1514 blocked for more than 122 seconds.\n      Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1\n\u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\ntask:kworker/u1664:6 state:D stack:0     pid:1514  tgid:1514  ppid:2      flags:0x00000000\nWorkqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core]\nCall Trace:\n [\u0026lt;000000065256f030\u0026gt;] __schedule+0x2a0/0x590\n [\u0026lt;000000065256f356\u0026gt;] schedule+0x36/0xe0\n [\u0026lt;0000000652172e28\u0026gt;] pci_wait_cfg+0x80/0xe8\n [\u0026lt;0000000652172f94\u0026gt;] pci_cfg_access_lock+0x74/0x88\n [\u0026lt;000003ff800916b6\u0026gt;] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core]\n [\u0026lt;000003ff80098824\u0026gt;] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core]\n [\u0026lt;000003ff80074b62\u0026gt;] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core]\n [\u0026lt;0000000652512242\u0026gt;] devlink_health_do_dump.part.0+0x82/0x168\n [\u0026lt;0000000652513212\u0026gt;] devlink_health_report+0x19a/0x230\n [\u0026lt;000003ff80075a12\u0026gt;] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]\n\nNo kernel log of the exact same error with an upstream kernel is\navailable - but the very same deadlock situation can be constructed there,\ntoo:\n\n- task: kmcheck\n  mlx5_unload_one() tries to acquire devlink lock while the PCI error\n  recovery code has set pdev-\u0026gt;block_cfg_access by way of\n  pci_cfg_access_lock()\n- task: kworker\n  mlx5_crdump_collect() tries to set block_cfg_access through\n  pci_cfg_access_lock() while devlink_health_report() had acquired\n  the devlink lock.\n\nA similar deadlock situation can be reproduced by requesting a\ncrdump with\n  \u0026gt; devlink health dump show pci/\u0026lt;BDF\u0026gt; reporter fw_fatal\n\nwhile PCI error recovery is executed on the same \u0026lt;BDF\u0026gt; physical function\nby mlx5_core\u0026apos;s pci_error_handlers. On s390 this can be injected with\n  \u0026gt; zpcictl --reset-fw \u0026lt;BDF\u0026gt;\n\nTests with this patch failed to reproduce that second deadlock situation,\nthe devlink command is rejected with \u0026quot;kernel answers: Permission denied\u0026quot; -\nand we get a kernel log message of:\n\nmlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5\n\nbecause the config read of VSC_SEMAPHORE is rejected by the underlying\nhardware.\n\nTwo prior attempts to address this issue have been discussed and\nultimately rejected [see link], with the primary argument that s390\u0026apos;s\nimplementation of PCI error recovery is imposing restrictions that\nneither powerpc\u0026apos;s EEH nor PCI AER handling need. Tests show that PCI\nerror recovery on s390 is running to completion even without blocking\naccess to PCI config space.(CVE-2025-68310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusbnet: Prevents free active kevent\n\nThe root cause of this issue are:\n1. When probing the usbnet device, executing usbnet_link_change(dev, 0, 0);\nput the kevent work in global workqueue. However, the kevent has not yet\nbeen scheduled when the usbnet device is unregistered. Therefore, executing\nfree_netdev() results in the \u0026quot;free active object (kevent)\u0026quot; error reported\nhere.\n\n2. Another factor is that when calling usbnet_disconnect()-\u0026gt;unregister_netdev(),\nif the usbnet device is up, ndo_stop() is executed to cancel the kevent.\nHowever, because the device is not up, ndo_stop() is not executed.\n\nThe solution to this problem is to cancel the kevent before executing\nfree_netdev().(CVE-2025-68312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config unlock in nbd_genl_connect\n\nThere is one use-after-free warning when running NBD_CMD_CONNECT and\nNBD_CLEAR_SOCK:\n\nnbd_genl_connect\n  nbd_alloc_and_init_config // config_refs=1\n  nbd_start_device // config_refs=2\n  set NBD_RT_HAS_CONFIG_REF\t\t\topen nbd // config_refs=3\n  recv_work done // config_refs=2\n\t\t\t\t\t\tNBD_CLEAR_SOCK // config_refs=1\n\t\t\t\t\t\tclose nbd // config_refs=0\n  refcount_inc -\u0026gt; uaf\n\n------------[ cut here ]------------\nrefcount_t: addition on 0; use-after-free.\nWARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290\n nbd_genl_connect+0x16d0/0x1ab0\n genl_family_rcv_msg_doit+0x1f3/0x310\n genl_rcv_msg+0x44a/0x790\n\nThe issue can be easily reproduced by adding a small delay before\nrefcount_inc(\u0026amp;nbd-\u0026gt;config_refs) in nbd_genl_connect():\n\n        mutex_unlock(\u0026amp;nbd-\u0026gt;config_lock);\n        if (!ret) {\n                set_bit(NBD_RT_HAS_CONFIG_REF, \u0026amp;config-\u0026gt;runtime_flags);\n+               printk(\u0026quot;before sleep\\n\u0026quot;);\n+               mdelay(5 * 1000);\n+               printk(\u0026quot;after sleep\\n\u0026quot;);\n                refcount_inc(\u0026amp;nbd-\u0026gt;config_refs);\n                nbd_connect_reply(info, nbd-\u0026gt;index);\n        }(CVE-2025-68366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse\n\nThe following warning appears when running syzkaller, and this issue also\nexists in the mainline code.\n\n ------------[ cut here ]------------\n list_add double add: new=ffffffffa57eee28, prev=ffffffffa57eee28, next=ffffffffa5e63100.\n WARNING: CPU: 0 PID: 1491 at lib/list_debug.c:35 __list_add_valid_or_report+0xf7/0x130\n Modules linked in:\n CPU: 0 PID: 1491 Comm: syz.1.28 Not tainted 6.6.0+ #3\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:__list_add_valid_or_report+0xf7/0x130\n RSP: 0018:ff1100010dfb7b78 EFLAGS: 00010282\n RAX: 0000000000000000 RBX: ffffffffa57eee18 RCX: ffffffff97fc9817\n RDX: 0000000000040000 RSI: ffa0000002383000 RDI: 0000000000000001\n RBP: ffffffffa57eee28 R08: 0000000000000001 R09: ffe21c0021bf6f2c\n R10: 0000000000000001 R11: 6464615f7473696c R12: ffffffffa5e63100\n R13: ffffffffa57eee28 R14: ffffffffa57eee28 R15: ff1100010dfb7d48\n FS:  00007fb14398b640(0000) GS:ff11000119600000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000000 CR3: 000000010d096005 CR4: 0000000000773ef0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 80000000\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  input_register_handler+0xb3/0x210\n  mac_hid_start_emulation+0x1c5/0x290\n  mac_hid_toggle_emumouse+0x20a/0x240\n  proc_sys_call_handler+0x4c2/0x6e0\n  new_sync_write+0x1b1/0x2d0\n  vfs_write+0x709/0x950\n  ksys_write+0x12a/0x250\n  do_syscall_64+0x5a/0x110\n  entry_SYSCALL_64_after_hwframe+0x78/0xe2\n\nThe WARNING occurs when two processes concurrently write to the mac-hid\nemulation sysctl, causing a race condition in mac_hid_toggle_emumouse().\nBoth processes read old_val=0, then both try to register the input handler,\nleading to a double list_add of the same handler.\n\n  CPU0                             CPU1\n  -------------------------        -------------------------\n  vfs_write() //write 1            vfs_write()  //write 1\n    proc_sys_write()                 proc_sys_write()\n      mac_hid_toggle_emumouse()          mac_hid_toggle_emumouse()\n        old_val = *valp // old_val=0\n                                           old_val = *valp // old_val=0\n                                           mutex_lock_killable()\n                                           proc_dointvec() // *valp=1\n                                           mac_hid_start_emulation()\n                                             input_register_handler()\n                                           mutex_unlock()\n        mutex_lock_killable()\n        proc_dointvec()\n        mac_hid_start_emulation()\n          input_register_handler() //Trigger Warning\n        mutex_unlock()\n\nFix this by moving the old_val read inside the mutex lock region.(CVE-2025-68367)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: smartpqi: Fix device resources accessed after device removal\n\nCorrect possible race conditions during device removal.\n\nPreviously, a scheduled work item to reset a LUN could still execute\nafter the device was removed, leading to use-after-free and other\nresource access issues.\n\nThis race condition occurs because the abort handler may schedule a LUN\nreset concurrently with device removal via sdev_destroy(), leading to\nuse-after-free and improper access to freed resources.\n\n  - Check in the device reset handler if the device is still present in\n    the controller\u0026apos;s SCSI device list before running; if not, the reset\n    is skipped.\n\n  - Cancel any pending TMF work that has not started in sdev_destroy().\n\n  - Ensure device freeing in sdev_destroy() is done while holding the\n    LUN reset mutex to avoid races with ongoing resets.(CVE-2025-68371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: defer config put in recv_work\n\nThere is one uaf issue in recv_work when running NBD_CLEAR_SOCK and\nNBD_CMD_RECONFIGURE:\n  nbd_genl_connect     // conf_ref=2 (connect and recv_work A)\n  nbd_open\t       // conf_ref=3\n  recv_work A done     // conf_ref=2\n  NBD_CLEAR_SOCK       // conf_ref=1\n  nbd_genl_reconfigure // conf_ref=2 (trigger recv_work B)\n  close nbd\t       // conf_ref=1\n  recv_work B\n    config_put         // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nOr only running NBD_CLEAR_SOCK:\n  nbd_genl_connect   // conf_ref=2\n  nbd_open \t     // conf_ref=3\n  NBD_CLEAR_SOCK     // conf_ref=2\n  close nbd\n    nbd_release\n      config_put     // conf_ref=1\n  recv_work\n    config_put \t     // conf_ref=0\n    atomic_dec(\u0026amp;config-\u0026gt;recv_threads); -\u0026gt; UAF\n\nCommit 87aac3a80af5 (\u0026quot;nbd: call nbd_config_put() before notifying the\nwaiter\u0026quot;) moved nbd_config_put() to run before waking up the waiter in\nrecv_work, in order to ensure that nbd_start_device_ioctl() would not\nbe woken up while nbd-\u0026gt;task_recv was still uncleared.\n\nHowever, in nbd_start_device_ioctl(), after being woken up it explicitly\ncalls flush_workqueue() to make sure all current works are finished.\nTherefore, there is no need to move the config put ahead of the wakeup.\n\nMove nbd_config_put() to the end of recv_work, so that the reference is\nheld for the whole lifetime of the worker thread. This makes sure the\nconfig cannot be freed while recv_work is still running, even if clear\n+ reconfigure interleave.\n\nIn addition, we don\u0026apos;t need to worry about recv_work dropping the last\nnbd_put (which causes deadlock):\n\npath A (netlink with NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=1 (trigger recv_work)\n  open nbd // nbd_refs=2\n  NBD_CLEAR_SOCK\n  close nbd\n    nbd_release\n      nbd_disconnect_and_put\n        flush_workqueue // recv_work done\n      nbd_config_put\n        nbd_put // nbd_refs=1\n      nbd_put // nbd_refs=0\n        queue_work\n\npath B (netlink without NBD_CFLAG_DESTROY_ON_DISCONNECT):\n  connect  // nbd_refs=2 (trigger recv_work)\n  open nbd // nbd_refs=3\n  NBD_CLEAR_SOCK // conf_refs=2\n  close nbd\n    nbd_release\n      nbd_config_put // conf_refs=1\n      nbd_put // nbd_refs=2\n  recv_work done // conf_refs=0, nbd_refs=1\n  rmmod // nbd_refs=0\n\nDepends-on: e2daec488c57 (\u0026quot;nbd: Fix hungtask when nbd_config_put\u0026quot;)(CVE-2025-68372)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix rcu protection in md_wakeup_thread\n\nWe attempted to use RCU to protect the pointer \u0026apos;thread\u0026apos;, but directly\npassed the value when calling md_wakeup_thread(). This means that the\nRCU pointer has been acquired before rcu_read_lock(), which renders\nrcu_read_lock() ineffective and could lead to a use-after-free.(CVE-2025-68374)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix null deref on srq-\u0026gt;rq.queue after resize failure\n\nA NULL pointer dereference can occur in rxe_srq_chk_attr() when\nibv_modify_srq() is invoked twice in succession under certain error\nconditions. The first call may fail in rxe_queue_resize(), which leads\nrxe_srq_from_attr() to set srq-\u0026gt;rq.queue = NULL. The second call then\ntriggers a crash (null deref) when accessing\nsrq-\u0026gt;rq.queue-\u0026gt;buf-\u0026gt;index_mask.\n\nCall Trace:\n\u0026lt;TASK\u0026gt;\nrxe_modify_srq+0x170/0x480 [rdma_rxe]\n? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]\n? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]\n? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]\nib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]\n? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]\n? tryinc_node_nr_active+0xe6/0x150\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\n? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]\nib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]\n? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]\nib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]\n? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]\n? __pfx___raw_spin_lock_irqsave+0x10/0x10\n? __pfx_do_vfs_ioctl+0x10/0x10\n? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0\n? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10\nib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]\n? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]\n__x64_sys_ioctl+0x138/0x1c0\ndo_syscall_64+0x82/0x250\n? fdget_pos+0x58/0x4c0\n? ksys_write+0xf3/0x1c0\n? __pfx_ksys_write+0x10/0x10\n? do_syscall_64+0xc8/0x250\n? __pfx_vm_mmap_pgoff+0x10/0x10\n? fget+0x173/0x230\n? fput+0x2a/0x80\n? ksys_mmap_pgoff+0x224/0x4c0\n? do_syscall_64+0xc8/0x250\n? do_user_addr_fault+0x37b/0xfe0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\n? clear_bhb_loop+0x50/0xa0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2025-68379)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags\n\nWhen a filesystem is being automounted, it needs to preserve the\nuser-set superblock mount options, such as the \u0026quot;ro\u0026quot; flag.(CVE-2025-68764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfsnotify: do not generate ACCESS/MODIFY events on child for special files\n\ninotify/fanotify do not allow users with no read access to a file to\nsubscribe to events (e.g. IN_ACCESS/IN_MODIFY), but they do allow the\nsame user to subscribe for watching events on children when the user\nhas access to the parent directory (e.g. /dev).\n\nUsers with no read access to a file but with read access to its parent\ndirectory can still stat the file and see if it was accessed/modified\nvia atime/mtime change.\n\nThe same is not true for special files (e.g. /dev/null). Users will not\ngenerally observe atime/mtime changes when other users read/write to\nspecial files, only when someone sets atime/mtime via utimensat().\n\nAlign fsnotify events with this stat behavior and do not generate\nACCESS/MODIFY events to parent watchers on read/write of special files.\nThe events are still generated to parent watchers on utimensat(). This\ncloses some side-channels that could be possibly used for information\nexfiltration [1].\n\n[1] https://snee.la/pdf/pubs/file-notification-attacks.pdf(CVE-2025-68788)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: missing copy_finish in fuse-over-io-uring argument copies\n\nFix a possible reference count leak of payload pages during\nfuse argument copies.\n\n[Joanne: simplified error cleanup](CVE-2025-68791)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd: Check event before enable to avoid GPF\n\nOn AMD machines cpuc-\u0026gt;events[idx] can become NULL in a subtle race\ncondition with NMI-\u0026gt;throttle-\u0026gt;x86_pmu_stop().\n\nCheck event for NULL in amd_pmu_enable_all() before enable to avoid a GPF.\nThis appears to be an AMD only issue.\n\nSyzkaller reported a GPF in amd_pmu_enable_all.\n\nINFO: NMI handler (perf_event_nmi_handler) took too long to run: 13.143\n    msecs\nOops: general protection fault, probably for non-canonical address\n    0xdffffc0000000034: 0000  PREEMPT SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x00000000000001a0-0x00000000000001a7]\nCPU: 0 UID: 0 PID: 328415 Comm: repro_36674776 Not tainted 6.12.0-rc1-syzk\nRIP: 0010:x86_pmu_enable_event (arch/x86/events/perf_event.h:1195\n    arch/x86/events/core.c:1430)\nRSP: 0018:ffff888118009d60 EFLAGS: 00010012\nRAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: 0000000000000034 RSI: 0000000000000000 RDI: 00000000000001a0\nRBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002\nR13: ffff88811802a440 R14: ffff88811802a240 R15: ffff8881132d8601\nFS:  00007f097dfaa700(0000) GS:ffff888118000000(0000) GS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000200001c0 CR3: 0000000103d56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;IRQ\u0026gt;\namd_pmu_enable_all (arch/x86/events/amd/core.c:760 (discriminator 2))\nx86_pmu_enable (arch/x86/events/core.c:1360)\nevent_sched_out (kernel/events/core.c:1191 kernel/events/core.c:1186\n    kernel/events/core.c:2346)\n__perf_remove_from_context (kernel/events/core.c:2435)\nevent_function (kernel/events/core.c:259)\nremote_function (kernel/events/core.c:92 (discriminator 1)\n    kernel/events/core.c:72 (discriminator 1))\n__flush_smp_call_function_queue (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207 ./include/trace/events/csd.h:64\n    kernel/smp.c:135 kernel/smp.c:540)\n__sysvec_call_function_single (./arch/x86/include/asm/jump_label.h:27\n    ./include/linux/jump_label.h:207\n    ./arch/x86/include/asm/trace/irq_vectors.h:99 arch/x86/kernel/smp.c:272)\nsysvec_call_function_single (arch/x86/kernel/smp.c:266 (discriminator 47)\n    arch/x86/kernel/smp.c:266 (discriminator 47))\n \u0026lt;/IRQ\u0026gt;(CVE-2025-68798)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats\n\nCited commit added a dedicated mutex (instead of RTNL) to protect the\nmulticast route list, so that it will not change while the driver\nperiodically traverses it in order to update the kernel about multicast\nroute stats that were queried from the device.\n\nOne instance of list entry deletion (during route replace) was missed\nand it can result in a use-after-free [1].\n\nFix by acquiring the mutex before deleting the entry from the list and\nreleasing it afterwards.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\nRead of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043\n\nCPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full)\nHardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017\nWorkqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xba/0x110\n print_report+0x174/0x4f5\n kasan_report+0xdf/0x110\n mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x8f/0xa0\n mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 29933:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x70\n __kasan_slab_free+0x43/0x70\n kfree+0x14e/0x700\n mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum]\n mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum]\n process_one_work+0x9cc/0x18e0\n worker_thread+0x5df/0xe40\n kthread+0x3b8/0x730\n ret_from_fork+0x3e9/0x560\n ret_from_fork_asm+0x1a/0x30(CVE-2025-68800)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix io-uring list corruption for terminated non-committed requests\n\nWhen a request is terminated before it has been committed, the request\nis not removed from the queue\u0026apos;s list. This leaves a dangling list entry\nthat leads to list corruption and use-after-free issues.\n\nRemove the request from the queue\u0026apos;s list for terminated non-committed\nrequests.(CVE-2025-68805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix readahead reclaim deadlock\n\nCommit e26ee4efbc79 (\u0026quot;fuse: allocate ff-\u0026gt;release_args only if release is\nneeded\u0026quot;) skips allocating ff-\u0026gt;release_args if the server does not\nimplement open. However in doing so, fuse_prepare_release() now skips\ngrabbing the reference on the inode, which makes it possible for an\ninode to be evicted from the dcache while there are inflight readahead\nrequests. This causes a deadlock if the server triggers reclaim while\nservicing the readahead request and reclaim attempts to evict the inode\nof the file being read ahead. Since the folio is locked during\nreadahead, when reclaim evicts the fuse inode and fuse_evict_inode()\nattempts to remove all folios associated with the inode from the page\ncache (truncate_inode_pages_range()), reclaim will block forever waiting\nfor the lock since readahead cannot relinquish the lock because it is\nitself blocked in reclaim:\n\n\u0026gt;\u0026gt;\u0026gt; stack_trace(1504735)\n folio_wait_bit_common (mm/filemap.c:1308:4)\n folio_lock (./include/linux/pagemap.h:1052:3)\n truncate_inode_pages_range (mm/truncate.c:336:10)\n fuse_evict_inode (fs/fuse/inode.c:161:2)\n evict (fs/inode.c:704:3)\n dentry_unlink_inode (fs/dcache.c:412:3)\n __dentry_kill (fs/dcache.c:615:3)\n shrink_kill (fs/dcache.c:1060:12)\n shrink_dentry_list (fs/dcache.c:1087:3)\n prune_dcache_sb (fs/dcache.c:1168:2)\n super_cache_scan (fs/super.c:221:10)\n do_shrink_slab (mm/shrinker.c:435:9)\n shrink_slab (mm/shrinker.c:626:10)\n shrink_node (mm/vmscan.c:5951:2)\n shrink_zones (mm/vmscan.c:6195:3)\n do_try_to_free_pages (mm/vmscan.c:6257:3)\n do_swap_page (mm/memory.c:4136:11)\n handle_pte_fault (mm/memory.c:5562:10)\n handle_mm_fault (mm/memory.c:5870:9)\n do_user_addr_fault (arch/x86/mm/fault.c:1338:10)\n handle_page_fault (arch/x86/mm/fault.c:1481:3)\n exc_page_fault (arch/x86/mm/fault.c:1539:2)\n asm_exc_page_fault+0x22/0x27\n\nFix this deadlock by allocating ff-\u0026gt;release_args and grabbing the\nreference on the inode when preparing the file for release even if the\nserver does not implement open. The inode reference will be dropped when\nthe last reference on the fuse file is dropped (see fuse_file_put() -\u0026gt;\nfuse_release_end()).(CVE-2025-68821)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ne1000: fix OOB in e1000_tbi_should_accept()\n\nIn e1000_tbi_should_accept() we read the last byte of the frame via\n\u0026apos;data[length - 1]\u0026apos; to evaluate the TBI workaround. If the descriptor-\nreported length is zero or larger than the actual RX buffer size, this\nread goes out of bounds and can hit unrelated slab objects. The issue\nis observed from the NAPI receive path (e1000_clean_rx_irq):\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790\nRead of size 1 at addr ffff888014114e54 by task sshd/363\n\nCPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x5a/0x74\n print_address_description+0x7b/0x440\n print_report+0x101/0x200\n kasan_report+0xc1/0xf0\n e1000_tbi_should_accept+0x610/0x790\n e1000_clean_rx_irq+0xa8c/0x1110\n e1000_clean+0xde2/0x3c10\n __napi_poll+0x98/0x380\n net_rx_action+0x491/0xa20\n __do_softirq+0x2c9/0x61d\n do_softirq+0xd1/0x120\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xfe/0x130\n ip_finish_output2+0x7d5/0xb00\n __ip_queue_xmit+0xe24/0x1ab0\n __tcp_transmit_skb+0x1bcb/0x3340\n tcp_write_xmit+0x175d/0x6bd0\n __tcp_push_pending_frames+0x7b/0x280\n tcp_sendmsg_locked+0x2e4f/0x32d0\n tcp_sendmsg+0x24/0x40\n sock_write_iter+0x322/0x430\n vfs_write+0x56c/0xa60\n ksys_write+0xd1/0x190\n do_syscall_64+0x43/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f511b476b10\nCode: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24\nRSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10\nRDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003\nRBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00\nR10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003\n \u0026lt;/TASK\u0026gt;\nAllocated by task 1:\n __kasan_krealloc+0x131/0x1c0\n krealloc+0x90/0xc0\n add_sysfs_param+0xcb/0x8a0\n kernel_add_sysfs_param+0x81/0xd4\n param_sysfs_builtin+0x138/0x1a6\n param_sysfs_init+0x57/0x5b\n do_one_initcall+0x104/0x250\n do_initcall_level+0x102/0x132\n do_initcalls+0x46/0x74\n kernel_init_freeable+0x28f/0x393\n kernel_init+0x14/0x1a0\n ret_from_fork+0x22/0x30\nThe buggy address belongs to the object at ffff888014114000\n which belongs to the cache kmalloc-2k of size 2048\nThe buggy address is located 1620 bytes to the right of\n 2048-byte region [ffff888014114000, ffff888014114800]\nThe buggy address belongs to the physical page:\npage:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110\nhead:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0\nflags: 0x100000000010200(slab|head|node=0|zone=1)\nraw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000\nraw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000\npage dumped because: kasan: bad access detected\n==================================================================\n\nThis happens because the TBI check unconditionally dereferences the last\nbyte without validating the reported length first:\n\n\tu8 last_byte = *(data + length - 1);\n\nFix by rejecting the frame early if the length is zero, or if it exceeds\nadapter-\u0026gt;rx_buffer_len. This preserves the TBI workaround semantics for\nvalid frames and prevents touching memory beyond the RX buffer.(CVE-2025-71093)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Handle incorrect num_connectors capability\n\nThe UCSI spec states that the num_connectors field is 7 bits, and the\n8th bit is reserved and should be set to zero.\nSome buggy FW has been known to set this bit, and it can lead to a\nsystem not booting.\nFlag that the FW is not behaving correctly, and auto-fix the value\nso that the system boots correctly.\n\nFound on Lenovo P1 G8 during Linux enablement program. The FW will\nbe fixed, but seemed worth addressing in case it hit platforms that\naren\u0026apos;t officially Linux supported.(CVE-2025-71108)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - zero initialize memory allocated via sock_kmalloc\n\nSeveral crypto user API contexts and requests allocated with\nsock_kmalloc() were left uninitialized, relying on callers to\nset fields explicitly. This resulted in the use of uninitialized\ndata in certain error paths or when new fields are added in the\nfuture.\n\nThe ACVP patches also contain two user-space interface files:\nalgif_kpp.c and algif_akcipher.c. These too rely on proper\ninitialization of their context structures.\n\nA particular issue has been observed with the newly added\n\u0026apos;inflight\u0026apos; variable introduced in af_alg_ctx by commit:\n\n  67b164a871af (\u0026quot;crypto: af_alg - Disallow multiple in-flight AIO requests\u0026quot;)\n\nBecause the context is not memset to zero after allocation,\nthe inflight variable has contained garbage values. As a result,\naf_alg_alloc_areq() has incorrectly returned -EBUSY randomly when\nthe garbage value was interpreted as true:\n\n  https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209\n\nThe check directly tests ctx-\u0026gt;inflight without explicitly\ncomparing against true/false. Since inflight is only ever set to\ntrue or false later, an uninitialized value has triggered\n-EBUSY failures. Zero-initializing memory allocated with\nsock_kmalloc() ensures inflight and other fields start in a known\nstate, removing random issues caused by uninitialized data.(CVE-2025-71113)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec: Enable SMT before waking offline CPUs\n\nIf SMT is disabled or a partial SMT state is enabled, when a new kernel\nimage is loaded for kexec, on reboot the following warning is observed:\n\nkexec: Waking offline cpu 228.\nWARNING: CPU: 0 PID: 9062 at arch/powerpc/kexec/core_64.c:223 kexec_prepare_cpus+0x1b0/0x1bc\n[snip]\n NIP kexec_prepare_cpus+0x1b0/0x1bc\n LR  kexec_prepare_cpus+0x1a0/0x1bc\n Call Trace:\n  kexec_prepare_cpus+0x1a0/0x1bc (unreliable)\n  default_machine_kexec+0x160/0x19c\n  machine_kexec+0x80/0x88\n  kernel_kexec+0xd0/0x118\n  __do_sys_reboot+0x210/0x2c4\n  system_call_exception+0x124/0x320\n  system_call_vectored_common+0x15c/0x2ec\n\nThis occurs as add_cpu() fails due to cpu_bootable() returning false for\nCPUs that fail the cpu_smt_thread_allowed() check or non primary\nthreads if SMT is disabled.\n\nFix the issue by enabling SMT and resetting the number of SMT threads to\nthe number of threads per core, before attempting to wake up all present\nCPUs.(CVE-2025-71119)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Do not register unsupported perf events\n\nSynthetic events currently do not have a function to register perf events.\nThis leads to calling the tracepoint register functions with a NULL\nfunction pointer which triggers:\n\n ------------[ cut here ]------------\n WARNING: kernel/tracepoint.c:175 at tracepoint_add_func+0x357/0x370, CPU#2: perf/2272\n Modules linked in: kvm_intel kvm irqbypass\n CPU: 2 UID: 0 PID: 2272 Comm: perf Not tainted 6.18.0-ftest-11964-ge022764176fc-dirty #323 PREEMPTLAZY\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:tracepoint_add_func+0x357/0x370\n Code: 28 9c e8 4c 0b f5 ff eb 0f 4c 89 f7 48 c7 c6 80 4d 28 9c e8 ab 89 f4 ff 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc \u0026lt;0f\u0026gt; 0b 49 c7 c6 ea ff ff ff e9 ee fe ff ff 0f 0b e9 f9 fe ff ff 0f\n RSP: 0018:ffffabc0c44d3c40 EFLAGS: 00010246\n RAX: 0000000000000001 RBX: ffff9380aa9e4060 RCX: 0000000000000000\n RDX: 000000000000000a RSI: ffffffff9e1d4a98 RDI: ffff937fcf5fd6c8\n RBP: 0000000000000001 R08: 0000000000000007 R09: ffff937fcf5fc780\n R10: 0000000000000003 R11: ffffffff9c193910 R12: 000000000000000a\n R13: ffffffff9e1e5888 R14: 0000000000000000 R15: ffffabc0c44d3c78\n FS:  00007f6202f5f340(0000) GS:ffff93819f00f000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000055d3162281a8 CR3: 0000000106a56003 CR4: 0000000000172ef0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  tracepoint_probe_register+0x5d/0x90\n  synth_event_reg+0x3c/0x60\n  perf_trace_event_init+0x204/0x340\n  perf_trace_init+0x85/0xd0\n  perf_tp_event_init+0x2e/0x50\n  perf_try_init_event+0x6f/0x230\n  ? perf_event_alloc+0x4bb/0xdc0\n  perf_event_alloc+0x65a/0xdc0\n  __se_sys_perf_event_open+0x290/0x9f0\n  do_syscall_64+0x93/0x7b0\n  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ? trace_hardirqs_off+0x53/0xc0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nInstead, have the code return -ENODEV, which doesn\u0026apos;t warn and has perf\nerror out with:\n\n # perf record -e synthetic:futex_wait\nError:\nThe sys_perf_event_open() syscall returned with 19 (No such device) for event (synthetic:futex_wait).\n\u0026quot;dmesg | grep -i perf\u0026quot; may provide additional information.\n\nIdeally perf should support synthetic events, but for now just fix the\nwarning. The support can come later.(CVE-2025-71125)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncifs: Fix memory and information leak in smb3_reconfigure()\n\nIn smb3_reconfigure(), if smb3_sync_session_ctx_passwords() fails, the\nfunction returns immediately without freeing and erasing the newly\nallocated new_password and new_password2. This causes both a memory leak\nand a potential information leak.\n\nFix this by calling kfree_sensitive() on both password buffers before\nreturning in this error case.(CVE-2025-71151)","status":"published","published":"2026-02-06T11:10:20Z","modified":"2026-08-18T01:19:32.443986305Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.339366Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2025-38713","title":"CVE-2025-38713 in linux - Patched by Root","description":"Root has patched CVE-2025-38713 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:42.666032265Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:29.356832Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2025-38713","title":"CVE-2025-38713 in linux - Patched by Root","description":"Root has patched CVE-2025-38713 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:17:35.777607756Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:31.251695Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2025-38713","title":"CVE-2025-38713 in linux - Patched by Root","description":"Root has patched CVE-2025-38713 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:16:47.4114148Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-06T14:57:21.851945Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-38713","title":"CVE-2025-38713 in linux - Patched by Root","description":"Root has patched CVE-2025-38713 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:16:15.473544144Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-06T16:59:12.925458Z"},{"id":"UBUNTU-CVE-2025-38713","description":"In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc(): [  667.121659][ T9805] ================================================================== [  667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10 [  667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805 [  667.124578][ T9805] [  667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full) [  667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [  667.124890][ T9805] Call Trace: [  667.124893][ T9805]  \u003cTASK\u003e [  667.124896][ T9805]  dump_stack_lvl+0x10e/0x1f0 [  667.124911][ T9805]  print_report+0xd0/0x660 [  667.124920][ T9805]  ? __virt_addr_valid+0x81/0x610 [  667.124928][ T9805]  ? __phys_addr+0xe8/0x180 [  667.124934][ T9805]  ? hfsplus_uni2asc+0x902/0xa10 [  667.124942][ T9805]  kasan_report+0xc6/0x100 [  667.124950][ T9805]  ? hfsplus_uni2asc+0x902/0xa10 [  667.124959][ T9805]  hfsplus_uni2asc+0x902/0xa10 [  667.124966][ T9805]  ? hfsplus_bnode_read+0x14b/0x360 [  667.124974][ T9805]  hfsplus_readdir+0x845/0xfc0 [  667.124984][ T9805]  ? __pfx_hfsplus_readdir+0x10/0x10 [  667.124994][ T9805]  ? stack_trace_save+0x8e/0xc0 [  667.125008][ T9805]  ? iterate_dir+0x18b/0xb20 [  667.125015][ T9805]  ? trace_lock_acquire+0x85/0xd0 [  667.125022][ T9805]  ? lock_acquire+0x30/0x80 [  667.125029][ T9805]  ? iterate_dir+0x18b/0xb20 [  667.125037][ T9805]  ? down_read_killable+0x1ed/0x4c0 [  667.125044][ T9805]  ? putname+0x154/0x1a0 [  667.125051][ T9805]  ? __pfx_down_read_killable+0x10/0x10 [  667.125058][ T9805]  ? apparmor_file_permission+0x239/0x3e0 [  667.125069][ T9805]  iterate_dir+0x296/0xb20 [  667.125076][ T9805]  __x64_sys_getdents64+0x13c/0x2c0 [  667.125084][ T9805]  ? __pfx___x64_sys_getdents64+0x10/0x10 [  667.125091][ T9805]  ? __x64_sys_openat+0x141/0x200 [  667.125126][ T9805]  ? __pfx_filldir64+0x10/0x10 [  667.125134][ T9805]  ? do_user_addr_fault+0x7fe/0x12f0 [  667.125143][ T9805]  do_syscall_64+0xc9/0x480 [  667.125151][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f [  667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9 [  667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48 [  667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9 [  667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9 [  667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004 [  667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110 [  667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260 [  667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [  667.125207][ T9805]  \u003c/TASK\u003e [  667.125210][ T9805] [  667.145632][ T9805] Allocated by task 9805: [  667.145991][ T9805]  kasan_save_stack+0x20/0x40 [  667.146352][ T9805]  kasan_save_track+0x14/0x30 [  667.146717][ T9805]  __kasan_kmalloc+0xaa/0xb0 [  667.147065][ T9805]  __kmalloc_noprof+0x205/0x550 [  667.147448][ T9805]  hfsplus_find_init+0x95/0x1f0 [  667.147813][ T9805]  hfsplus_readdir+0x220/0xfc0 [  667.148174][ T9805]  iterate_dir+0x296/0xb20 [  667.148549][ T9805]  __x64_sys_getdents64+0x13c/0x2c0 [  667.148937][ T9805]  do_syscall_64+0xc9/0x480 [  667.149291][ T9805]  entry_SYSCALL_64_after_hwframe+0x77/0x7f [  667.149809][ T9805] [  667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000 [  667.150030][ T9805]  which belongs to the cache kmalloc-2k of size 2048 [  667.151282][ T9805] The buggy address is located 0 bytes to the right of [  667.151282][ T9805]  allocated 1036-byte region [ffff88802592f000, ffff88802592f40c) [  667.1 ---truncated---","status":"published","published":"2025-09-04T16:15:00Z","modified":"2026-11-11T09:39:07.023933895Z","cvss":[{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-11T10:00:55.303961Z"},{"id":"CLSA-2026-1773832495","title":"Fix of 132 CVEs","description":"   * CVE-2023-53515\n     - virtio-mmio: don't break lifecycle of vm_dev {CVE-2023-53515}\n   * CVE-2025-39967\n     - fbcon: fix integer overflow in fbcon_do_set_font {CVE-2025-39967}\n     - fbcon: Fix OOB access in font allocation {CVE-2025-39967}\n   * CVE-2025-38702\n     - fbdev: fix potential buffer overflow in do_register_framebuffer()\n       {CVE-2025-38702}\n   * CVE-2025-38563\n     - perf/core: Prevent VMA split of buffer mappings {CVE-2025-38563}\n   * CVE-2025-39869\n     - dmaengine: ti: edma: Fix memory allocation size for queue_priority_map\n       {CVE-2025-39869}\n   * CVE-2023-53577\n     - bpf, cpumap: Make sure kthread is running before map update returns\n       {CVE-2023-53577}\n   * CVE-2023-53608\n     - nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()\n       {CVE-2023-53608}\n   * CVE-2023-53604\n     - dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path\n       {CVE-2023-53604}\n   * CVE-2023-53619\n     - netfilter: Replace printk() with pr_*() and define pr_fmt() {CVE-2023-53619}\n     - netfilter: use kvmalloc_array to allocate memory for hashtable\n       {CVE-2023-53619}\n     - netfilter: conntrack: Avoid nf_ct_helper_hash uses after free\n       {CVE-2023-53619}\n   * CVE-2025-38680\n     - media: uvcvideo: Fix 1-byte out-of-bounds read in {CVE-2025-38680}\n   * CVE-2023-53454\n     - HID: multitouch: Correct devm device reference for hidinput {CVE-2023-53454}\n   * CVE-2025-38699\n     - scsi: bfa: Double-free fix {CVE-2025-38699}\n     - ubi: ensure that VID header offset + VID header size \u003c= alloc, size\n       {CVE-2023-53265}\n     - scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()\n       {CVE-2023-53676}\n     - fs: jfs: Fix UBSAN: array-index-out-of-bounds in {CVE-2025-38699}\n   * CVE-2023-53596\n     - drivers: base: Free devm resources when unregistering a {CVE-2023-53596}\n   * CVE-2023-53622\n     - gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n     - HSI: ssi_protocol: Fix use after free vulnerability in ssi_protocol Driver\n       Due to Race Condition {CVE-2023-53622}\n   * CVE-2023-53090\n     - drm/amdkfd: Fix an illegal memory access {CVE-2023-53090}\n   * CVE-2023-53116\n     - nvmet: avoid potential UAF in nvmet_req_complete() {CVE-2023-53116}\n   * CVE-2023-53138\n     - net: caif: Fix use-after-free in cfusbl_device_notify() {CVE-2023-53138}\n   * CVE-2023-53035\n     - nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() {CVE-2023-53035}\n   * CVE-2023-53668\n     - ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n   * CVE-2023-53616\n     - jfs: fix invalid free of JFS_IP(ipimap)-\u003ei_imap in diUnmount\n       {CVE-2023-53616}\n   * CVE-2023-53554\n     - staging: ks7010: potential buffer overflow in ks_wlan_set_encode_ext()\n       {CVE-2023-53554}\n   * CVE-2023-53587\n     - ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n   * CVE-2023-53541\n     - mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write\n       {CVE-2023-53541}\n   * CVE-2023-53559\n     - ip_vti: fix potential slab-use-after-free in decode_session6\n       {CVE-2023-53559}\n   * CVE-2023-53484\n     - lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries\n       {CVE-2023-53484}\n     - lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()\n       {CVE-2023-53484}\n   * CVE-2025-39824\n     - HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}\n   * CVE-2025-38715\n     - hfs: fix slab-out-of-bounds in hfs_bnode_read() {CVE-2025-38715}\n   * CVE-2023-53153\n     - wifi: cfg80211: Fix use after free for wext {CVE-2023-53153}\n   * CVE-2025-38555\n     - usb: gadget : fix use-after-free in composite_dev_cleanup() {CVE-2025-38555}\n   * CVE-2025-39743\n     - jfs: truncate good inode pages when hard link is 0 {CVE-2025-39743}\n   * CVE-2025-39945\n     - cnic: Fix use-after-free bugs in cnic_delete_task {CVE-2025-39945}\n   * CVE-2023-53506\n     - udf: Do not bother merging very long extents {CVE-2023-53506}\n   * CVE-2025-38714\n     - hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() {CVE-2025-38714}\n   * CVE-2025-39685\n     - comedi: pcl726: Prevent invalid irq number {CVE-2025-39685}\n   * CVE-2025-39839\n     - batman-adv: fix OOB read/write in network-coding decode {CVE-2025-39839}\n   * CVE-2025-38708\n     - drbd: add missing kref_get in handle_write_conflicts {CVE-2025-38708}\n   * CVE-2023-53521\n     - scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() {CVE-2023-53521}\n   * CVE-2025-38713\n     - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() {CVE-2025-38713}\n   * CVE-2023-53675\n     - scsi: ses: Fix possible desc_ptr out-of-bounds accesses {CVE-2023-53675}\n   * CVE-2025-39691\n     - fs/buffer: fix use-after-free when call bh_read() helper {CVE-2025-39691}\n   * CVE-2023-53259\n     - VMCI: check context-\u003enotify_page after call to get_user_pages_fast() to\n       avoid GPF {CVE-2023-53259}\n   * CVE-2023-53285\n     - ext4: add bounds checking in get_max_inline_xattr_value_size()\n       {CVE-2023-53285}\n   * CVE-2023-53148\n     - igb: Fix igb_down hung on surprise removal {CVE-2023-53148}\n   * CVE-2023-53219\n     - media: netup_unidvb: fix use-after-free at del_timer() {CVE-2023-53219}\n   * CVE-2023-53215\n     - sched/fair: Don't balance task to its current running CPU {CVE-2023-53215}\n   * CVE-2023-53305\n     - Bluetooth: L2CAP: Fix use-after-free {CVE-2023-53305}\n   * CVE-2025-38103\n     - HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()\n       {CVE-2025-38103}\n   * CVE-2025-38051\n     - smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}\n   * CVE-2025-38157\n     - wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}\n   * CVE-2023-53373\n     - crypto: seqiv - Handle EBUSY correctly {CVE-2023-53373}\n   * CVE-2025-38079\n     - crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}\n   * CVE-2025-38212\n     - ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n   * CVE-2025-38313\n     - bus: fsl-mc: fix double-free on mc_dev {CVE-2025-38313}\n   * CVE-2023-53311\n     - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput\n       {CVE-2023-53311}\n   * CVE-2023-53307\n     - rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails\n       {CVE-2023-53307}\n   * CVE-2025-38403\n     - vsock/vmci: Clear the vmci transport packet properly when initializing it\n       {CVE-2025-38403}\n   * CVE-2025-39683\n     - tracing: Limit access to parser-\u003ebuffer when trace_get_user failed\n       {CVE-2025-39683}\n   * CVE-2025-38697\n     - jfs: upper bound check of tree index in dbAllocAG {CVE-2025-38697}\n   * CVE-2025-39689\n     - ftrace: Also allocate and copy hash for reading of filter files\n       {CVE-2025-39689}\n   * CVE-2025-38574\n     - pptp: ensure minimal skb length in pptp_xmit() {CVE-2025-38574}\n   * CVE-2025-38572\n     - ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}\n   * CVE-2025-38685\n     - fbdev: Fix vmalloc out-of-bounds write in fast_imageblit {CVE-2025-38685}\n   * CVE-2025-39911\n     - i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path\n       {CVE-2025-39911}\n   * CVE-2025-39973\n     - i40e: increase max descriptors for XL710 {CVE-2025-39973}\n     - i40e: add validation for ring_len param {CVE-2025-39973}\n   * CVE-2025-38724\n     - nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()\n       {CVE-2025-38724}\n   * CVE-2025-39860\n     - Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen()\n       {CVE-2025-39860}\n   * CVE-2025-38530\n     - comedi: pcl812: Fix bit shift out of bounds {CVE-2025-38530}\n   * CVE-2025-38529\n     - comedi: aio_iiro_16: Fix bit shift out of bounds {CVE-2025-38529}\n   * CVE-2025-38497\n     - usb: gadget: configfs: Fix OOB read on empty string write {CVE-2025-38497}\n   * CVE-2025-38483\n     - comedi: das16m1: Fix bit shift out of bounds {CVE-2025-38483}\n   * CVE-2025-38482\n     - comedi: das6402: Fix bit shift out of bounds {CVE-2025-38482}\n   * CVE-2025-39702\n     - ipv6: sr: Fix MAC comparison to be constant-time {CVE-2025-39702}\n   * CVE-2025-39730\n     - NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() {CVE-2025-39730}\n   * CVE-2025-39817\n     - efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare {CVE-2025-39817}\n   * CVE-2025-38494\n     - HID: core: ensure the allocated report buffer can contain the reserved\n       report ID {CVE-2025-38494}\n     - HID: core: ensure __hid_request reserves the report ID as the first byte\n       {CVE-2025-38494}\n     - HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}\n   * CVE-2025-38527\n     - smb: client: fix use-after-free in cifs_oplock_break {CVE-2025-38527}\n   * CVE-2025-39965\n     - xfrm: Duplicate SPI Handling {CVE-2025-39965}\n   * CVE-2025-37927\n     - iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid\n       {CVE-2025-37927}\n   * CVE-2025-37817\n     - mcb: fix error handling for different scenarios when parsing\n       {CVE-2025-37817}\n     - mcb: fix a double free bug in chameleon_parse_gdd() {CVE-2025-37817}\n   * CVE-2025-38204\n     - jfs: fix array-index-out-of-bounds read in add_missing_indices\n       {CVE-2025-38204}\n   * CVE-2025-38323\n     - net: atm: add lec_mutex {CVE-2025-38323}\n   * CVE-2025-38346\n     - ftrace: Fix UAF when lookup kallsym after ftrace disabled {CVE-2025-38346}\n   * CVE-2025-38348\n     - wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n       {CVE-2025-38348}\n   * CVE-2025-38416\n     - NFC: nci: uart: Set tty-\u003edisc_data only in success path {CVE-2025-38416}\n   * CVE-2025-38428\n     - Input: ims-pcu - check record size in ims_pcu_flash_firmware()\n       {CVE-2025-38428}\n   * CVE-2025-38245\n     - atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().\n       {CVE-2025-38245}\n   * CVE-2025-38377\n     - rose: fix dangling neighbour pointers in rose_rt_device_down()\n       {CVE-2025-38377}\n   * CVE-2025-38459\n     - atm: clip: Fix infinite recursive call of clip_push(). {CVE-2025-38459}\n   * CVE-2025-39863\n     - wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work\n       {CVE-2025-39863}\n   * CVE-2025-21726\n     - padata: avoid UAF for reorder_work {CVE-2025-21726}\n   * CVE-2025-39760\n     - usb: core: config: Prevent OOB read in SS endpoint companion parsing\n       {CVE-2025-39760}\n   * CVE-2025-38198\n     - fbcon: Make sure modelist not set on unregistered console {CVE-2025-38198}\n   * CVE-2025-38375\n     - virtio-net: ensure the received length does not exceed allocated size\n       {CVE-2025-38375}\n   * CVE-2025-39993\n     - media: imon: reorganize serialization {CVE-2025-39993}\n     - media: rc: fix races with imon_disconnect() {CVE-2025-39993}\n   * CVE-2025-39883\n     - mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison\n       memory {CVE-2025-39883}\n   * Focal update: v5.4.211 upstream stable release (LP: #1990190)\n     - scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user\n       input\n   * Focal update: v5.4.231 upstream stable release (LP: #2011226) //\n     CVE-2023-53000\n     - netlink: prevent potential spectre v1 gadgets\n   * CVE-2022-49980\n     - USB: gadget: Fix use-after-free Read in usb_udc_uevent()\n   * CVE-2022-21546\n     - scsi: target: Fix WRITE_SAME No Data Buffer crash\n   * Focal update: v5.4.225 upstream stable release (LP: #2002347) //\n     CVE-2022-49763\n     - ntfs: fix use-after-free in ntfs_attr_find()\n   * Focal update: Focal update: v5.4.235 upstream stable release\n     (LP: #2017706) // CVE-2022-50258\n     - wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds()\n   * CVE-2025-21727\n     - padata: fix UAF in padata_reorder\n   * CVE-2025-37882\n     - usb: xhci: Fix isochronous Ring Underrun/Overrun event handling\n   * CVE-2025-38250\n     - Bluetooth: hci_core: Fix use-after-free in vhci_flush()\n   * CVE-2025-39751\n     - ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control\n   * CVE-2025-37810\n     - usb: dwc3: gadget: check that event count does not exceed event buffer\n       length\n   * CVE-2025-37839\n     - jbd2: remove wrong sb-\u003es_sequence check\n   * CVE-2025-37892\n     - mtd: inftlcore: Add error check for inftl_read_oob()\n   * CVE-2025-37923\n     - tracing: Fix oob write in trace_seq_to_buffer()\n   * CVE-2024-43883\n     - usb: vhci-hcd: Do not drop references before new references are gained\n   * CVE-2025-37739\n     - f2fs: lost matching-pair of trace in f2fs_truncate_inode_blocks\n     - f2fs: fix to avoid out-of-bounds access in f2fs_truncate_inode_blocks()\n   * CVE-2025-38069\n     - PCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops\n   * CVE-2025-22083\n     - vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint\n   * Miscellaneous upstream changes\n     - net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too\n     - HID: core: Harden s32ton() against conversion to 0 bits\n     - fbcon: Introduce wrapper for console-\u003efb_info lookup {CVE-2025-38198}\n     - net: atm: fix /proc/net/atm/lec handling {CVE-2025-38323}","status":"published","published":"2026-10-21T08:20:59Z","modified":"2026-10-26T09:32:03.234434244Z","updated_at":"2026-11-02T15:43:43.621843Z"},{"id":"CLSA-2026-1773872435","title":"Fix of 137 CVEs","description":"   * Miscellaneous Ubuntu changes\n     - update-from-bionic-master repo has been updated\n   * Miscellaneous upstream changes\n     - debian: add control and changeg files\n   [ Ubuntu: 4.15.0-254.265 ]\n   * CVE-2023-53515\n     - virtio-mmio: don't break lifecycle of vm_dev {CVE-2023-53515}\n   * CVE-2025-39967\n     - fbcon: fix integer overflow in fbcon_do_set_font {CVE-2025-39967}\n     - fbcon: Fix OOB access in font allocation {CVE-2025-39967}\n   * CVE-2025-38702\n     - fbdev: fix potential buffer overflow in do_register_framebuffer()\n       {CVE-2025-38702}\n   * CVE-2025-38563\n     - perf/core: Prevent VMA split of buffer mappings {CVE-2025-38563}\n   * CVE-2025-39869\n     - dmaengine: ti: edma: Fix memory allocation size for queue_priority_map\n       {CVE-2025-39869}\n   * CVE-2023-53577\n     - bpf, cpumap: Make sure kthread is running before map update returns\n       {CVE-2023-53577}\n   * CVE-2023-53608\n     - nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()\n       {CVE-2023-53608}\n   * CVE-2023-53604\n     - dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path\n       {CVE-2023-53604}\n   * CVE-2023-53619\n     - netfilter: Replace printk() with pr_*() and define pr_fmt() {CVE-2023-53619}\n     - netfilter: use kvmalloc_array to allocate memory for hashtable\n       {CVE-2023-53619}\n     - netfilter: conntrack: Avoid nf_ct_helper_hash uses after free\n       {CVE-2023-53619}\n   * CVE-2025-38680\n     - media: uvcvideo: Fix 1-byte out-of-bounds read in {CVE-2025-38680}\n   * CVE-2023-53454\n     - HID: multitouch: Correct devm device reference for hidinput {CVE-2023-53454}\n   * CVE-2025-38699\n     - scsi: bfa: Double-free fix {CVE-2025-38699}\n     - ubi: ensure that VID header offset + VID header size \u003c= alloc, size\n       {CVE-2023-53265}\n     - scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()\n       {CVE-2023-53676}\n     - fs: jfs: Fix UBSAN: array-index-out-of-bounds in {CVE-2025-38699}\n   * CVE-2023-53596\n     - drivers: base: Free devm resources when unregistering a {CVE-2023-53596}\n   * CVE-2023-53622\n     - gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n     - HSI: ssi_protocol: Fix use after free vulnerability in ssi_protocol Driver\n       Due to Race Condition {CVE-2023-53622}\n   * CVE-2023-53090\n     - drm/amdkfd: Fix an illegal memory access {CVE-2023-53090}\n   * CVE-2023-53116\n     - nvmet: avoid potential UAF in nvmet_req_complete() {CVE-2023-53116}\n   * CVE-2023-53138\n     - net: caif: Fix use-after-free in cfusbl_device_notify() {CVE-2023-53138}\n   * CVE-2023-53035\n     - nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() {CVE-2023-53035}\n   * CVE-2023-53668\n     - ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n   * CVE-2023-53616\n     - jfs: fix invalid free of JFS_IP(ipimap)-\u003ei_imap in diUnmount\n       {CVE-2023-53616}\n   * CVE-2023-53554\n     - staging: ks7010: potential buffer overflow in ks_wlan_set_encode_ext()\n       {CVE-2023-53554}\n   * CVE-2023-53587\n     - ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n   * CVE-2023-53541\n     - mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write\n       {CVE-2023-53541}\n   * CVE-2023-53559\n     - ip_vti: fix potential slab-use-after-free in decode_session6\n       {CVE-2023-53559}\n   * CVE-2023-53484\n     - lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries\n       {CVE-2023-53484}\n     - lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()\n       {CVE-2023-53484}\n   * CVE-2025-39824\n     - HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}\n   * CVE-2025-38715\n     - hfs: fix slab-out-of-bounds in hfs_bnode_read() {CVE-2025-38715}\n   * CVE-2023-53153\n     - wifi: cfg80211: Fix use after free for wext {CVE-2023-53153}\n   * CVE-2025-38555\n     - usb: gadget : fix use-after-free in composite_dev_cleanup() {CVE-2025-38555}\n   * CVE-2025-39743\n     - jfs: truncate good inode pages when hard link is 0 {CVE-2025-39743}\n   * CVE-2025-39945\n     - cnic: Fix use-after-free bugs in cnic_delete_task {CVE-2025-39945}\n   * CVE-2023-53506\n     - udf: Do not bother merging very long extents {CVE-2023-53506}\n   * CVE-2025-38714\n     - hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() {CVE-2025-38714}\n   * CVE-2025-39685\n     - comedi: pcl726: Prevent invalid irq number {CVE-2025-39685}\n   * CVE-2025-39839\n     - batman-adv: fix OOB read/write in network-coding decode {CVE-2025-39839}\n   * CVE-2025-38708\n     - drbd: add missing kref_get in handle_write_conflicts {CVE-2025-38708}\n   * CVE-2023-53521\n     - scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() {CVE-2023-53521}\n   * CVE-2025-38713\n     - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() {CVE-2025-38713}\n   * CVE-2023-53675\n     - scsi: ses: Fix possible desc_ptr out-of-bounds accesses {CVE-2023-53675}\n   * CVE-2025-39691\n     - fs/buffer: fix use-after-free when call bh_read() helper {CVE-2025-39691}\n   * CVE-2023-53259\n     - VMCI: check context-\u003enotify_page after call to get_user_pages_fast() to\n       avoid GPF {CVE-2023-53259}\n   * CVE-2023-53285\n     - ext4: add bounds checking in get_max_inline_xattr_value_size()\n       {CVE-2023-53285}\n   * CVE-2023-53148\n     - igb: Fix igb_down hung on surprise removal {CVE-2023-53148}\n   * CVE-2023-53219\n     - media: netup_unidvb: fix use-after-free at del_timer() {CVE-2023-53219}\n   * CVE-2023-53215\n     - sched/fair: Don't balance task to its current running CPU {CVE-2023-53215}\n   * CVE-2023-53305\n     - Bluetooth: L2CAP: Fix use-after-free {CVE-2023-53305}\n   * CVE-2025-38103\n     - HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()\n       {CVE-2025-38103}\n   * CVE-2025-38051\n     - smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}\n   * CVE-2025-38157\n     - wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}\n   * CVE-2023-53373\n     - crypto: seqiv - Handle EBUSY correctly {CVE-2023-53373}\n   * CVE-2025-38079\n     - crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}\n   * CVE-2025-38212\n     - ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n   * CVE-2025-38313\n     - bus: fsl-mc: fix double-free on mc_dev {CVE-2025-38313}\n   * CVE-2023-53311\n     - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput\n       {CVE-2023-53311}\n   * CVE-2023-53307\n     - rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails\n       {CVE-2023-53307}\n   * CVE-2025-38403\n     - vsock/vmci: Clear the vmci transport packet properly when initializing it\n       {CVE-2025-38403}\n   * CVE-2025-39683\n     - tracing: Limit access to parser-\u003ebuffer when trace_get_user failed\n       {CVE-2025-39683}\n   * CVE-2025-38697\n     - jfs: upper bound check of tree index in dbAllocAG {CVE-2025-38697}\n   * CVE-2025-39689\n     - ftrace: Also allocate and copy hash for reading of filter files\n       {CVE-2025-39689}\n   * CVE-2025-38574\n     - pptp: ensure minimal skb length in pptp_xmit() {CVE-2025-38574}\n   * CVE-2025-38572\n     - ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}\n   * CVE-2025-38685\n     - fbdev: Fix vmalloc out-of-bounds write in fast_imageblit {CVE-2025-38685}\n   * CVE-2025-39911\n     - i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path\n       {CVE-2025-39911}\n   * CVE-2025-39973\n     - i40e: increase max descriptors for XL710 {CVE-2025-39973}\n     - i40e: add validation for ring_len param {CVE-2025-39973}\n   * CVE-2025-38724\n     - nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()\n       {CVE-2025-38724}\n   * CVE-2025-39860\n     - Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen()\n       {CVE-2025-39860}\n   * CVE-2025-38530\n     - comedi: pcl812: Fix bit shift out of bounds {CVE-2025-38530}\n   * CVE-2025-38529\n     - comedi: aio_iiro_16: Fix bit shift out of bounds {CVE-2025-38529}\n   * CVE-2025-38497\n     - usb: gadget: configfs: Fix OOB read on empty string write {CVE-2025-38497}\n   * CVE-2025-38483\n     - comedi: das16m1: Fix bit shift out of bounds {CVE-2025-38483}\n   * CVE-2025-38482\n     - comedi: das6402: Fix bit shift out of bounds {CVE-2025-38482}\n   * CVE-2025-39702\n     - ipv6: sr: Fix MAC comparison to be constant-time {CVE-2025-39702}\n   * CVE-2025-39730\n     - NFS: Fix filehandle bounds checking in nfs_fh_to_dentry() {CVE-2025-39730}\n   * CVE-2025-39817\n     - efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare {CVE-2025-39817}\n   * CVE-2025-38494\n     - HID: core: ensure the allocated report buffer can contain the reserved\n       report ID {CVE-2025-38494}\n     - HID: core: ensure __hid_request reserves the report ID as the first byte\n       {CVE-2025-38494}\n     - HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}\n   * CVE-2025-38527\n     - smb: client: fix use-after-free in cifs_oplock_break {CVE-2025-38527}\n   * CVE-2025-39965\n     - xfrm: Duplicate SPI Handling {CVE-2025-39965}\n   * CVE-2025-37927\n     - iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid\n       {CVE-2025-37927}\n   * CVE-2025-37817\n     - mcb: fix error handling for different scenarios when parsing\n       {CVE-2025-37817}\n     - mcb: fix a double free bug in chameleon_parse_gdd() {CVE-2025-37817}\n   * CVE-2025-38204\n     - jfs: fix array-index-out-of-bounds read in add_missing_indices\n       {CVE-2025-38204}\n   * CVE-2025-38323\n     - net: atm: add lec_mutex {CVE-2025-38323}\n   * CVE-2025-38346\n     - ftrace: Fix UAF when lookup kallsym after ftrace disabled {CVE-2025-38346}\n   * CVE-2025-38348\n     - wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()\n       {CVE-2025-38348}\n   * CVE-2025-38416\n     - NFC: nci: uart: Set tty-\u003edisc_data only in success path {CVE-2025-38416}\n   * CVE-2025-38428\n     - Input: ims-pcu - check record size in ims_pcu_flash_firmware()\n       {CVE-2025-38428}\n   * CVE-2025-38245\n     - atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().\n       {CVE-2025-38245}\n   * CVE-2025-38377\n     - rose: fix dangling neighbour pointers in rose_rt_device_down()\n       {CVE-2025-38377}\n   * CVE-2025-38459\n     - atm: clip: Fix infinite recursive call of clip_push(). {CVE-2025-38459}\n   * CVE-2025-39863\n     - wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work\n       {CVE-2025-39863}\n   * CVE-2025-21726\n     - padata: avoid UAF for reorder_work {CVE-2025-21726}\n   * CVE-2025-39760\n     - usb: core: config: Prevent OOB read in SS endpoint companion parsing\n       {CVE-2025-39760}\n   * CVE-2025-38198\n     - fbcon: Make sure modelist not set on unregistered console {CVE-2025-38198}\n   * CVE-2025-38375\n     - virtio-net: ensure the received length does not exceed allocated size\n       {CVE-2025-38375}\n   * CVE-2025-39993\n     - media: imon: reorganize serialization {CVE-2025-39993}\n     - media: rc: fix races with imon_disconnect() {CVE-2025-39993}\n   * CVE-2025-39883\n     - mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison\n       memory {CVE-2025-39883}\n   * Focal update: v5.4.211 upstream stable release (LP: #1990190)\n     - scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user\n       input\n   * Focal update: v5.4.231 upstream stable release (LP: #2011226) //\n     CVE-2023-53000\n     - netlink: prevent potential spectre v1 gadgets\n   * CVE-2022-49980\n     - USB: gadget: Fix use-after-free Read in usb_udc_uevent()\n   * CVE-2022-21546\n     - scsi: target: Fix WRITE_SAME No Data Buffer crash\n   * Focal update: v5.4.225 upstream stable release (LP: #2002347) //\n     CVE-2022-49763\n     - ntfs: fix use-after-free in ntfs_attr_find()\n   * Focal update: Focal update: v5.4.235 upstream stable release\n     (LP: #2017706) // CVE-2022-50258\n     - wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds()\n   * CVE-2025-21727\n     - padata: fix UAF in padata_reorder\n   * CVE-2025-37882\n     - usb: xhci: Fix isochronous Ring Underrun/Overrun event handling\n   * CVE-2025-38250\n     - Bluetooth: hci_core: Fix use-after-free in vhci_flush()\n   * CVE-2025-39751\n     - ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control\n   * CVE-2025-37810\n     - usb: dwc3: gadget: check that event count does not exceed event buffer\n       length\n   * CVE-2025-37839\n     - jbd2: remove wrong sb-\u003es_sequence check\n   * CVE-2025-37892\n     - mtd: inftlcore: Add error check for inftl_read_oob()\n   * CVE-2025-37923\n     - tracing: Fix oob write in trace_seq_to_buffer()\n   * CVE-2024-43883\n     - usb: vhci-hcd: Do not drop references before new references are gained\n   * CVE-2025-37739\n     - f2fs: lost matching-pair of trace in f2fs_truncate_inode_blocks\n     - f2fs: fix to avoid out-of-bounds access in f2fs_truncate_inode_blocks()\n   * CVE-2025-38069\n     - PCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops\n   * CVE-2025-22083\n     - vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint\n   * Miscellaneous upstream changes\n     - net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too\n     - HID: core: Harden s32ton() against conversion to 0 bits\n     - fbcon: Introduce wrapper for console-\u003efb_info lookup {CVE-2025-38198}\n     - net: atm: fix /proc/net/atm/lec handling {CVE-2025-38323}","status":"published","published":"2026-10-21T08:36:28Z","modified":"2026-10-26T09:43:13.436707495Z","updated_at":"2026-11-02T15:43:43.621843Z"},{"id":"CLSA-2026-1775224807","title":"Fix of 95 CVEs","description":"   * CVE-2025-39683\n     - tracing: Remove unneeded goto out logic {CVE-2025-39683}\n     - tracing: Limit access to parser-\u003ebuffer when trace_get_user failed\n       {CVE-2025-39683}\n   * CVE-2025-38079\n     - crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}\n   * CVE-2025-38159\n     - wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds\n       {CVE-2025-38159}\n   * CVE-2025-38211\n     - RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction\n       {CVE-2025-38211}\n   * CVE-2025-38024\n     - RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug\n       {CVE-2025-38024}\n   * CVE-2025-38103\n     - HID: hyperv: Correctly access fields declared as __le16 {CVE-2025-38103}\n     - HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()\n       {CVE-2025-38103}\n   * CVE-2025-38157\n     - wifi: ath9k_htc: Abort software beacon handling if disabled\n       {CVE-2025-38157}\n   * CVE-2025-38230\n     - jfs: add sanity check for agwidth in dbMount {CVE-2025-38230}\n     - fs/jfs: consolidate sanity checking in dbMount {CVE-2025-38230}\n     - jfs: validate AG parameters in dbMount() to prevent crashes\n       {CVE-2025-38230}\n   * CVE-2025-39955\n     - tcp: Clear tcp_sk(sk)-\u003efastopen_rsk in tcp_disconnect().\n       {CVE-2025-39955}\n   * CVE-2025-38680\n     - media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()\n       {CVE-2025-38680}\n   * CVE-2025-38708\n     - drbd: add missing kref_get in handle_write_conflicts {CVE-2025-38708}\n   * CVE-2025-39759\n     - btrfs: qgroup: introduce quota mode {CVE-2025-39759}\n     - btrfs: qgroup: fix race between quota disable and quota rescan ioctl\n       {CVE-2025-39759}\n   * CVE-2025-38666\n     - net: appletalk: Fix use-after-free in AARP proxy probe {CVE-2025-38666}\n   * CVE-2025-40269\n     - ALSA: usb-audio: Improve frames size computation {CVE-2025-40269}\n     - ALSA: usb-audio: Replace s/frame/packet/ where appropriate\n       {CVE-2025-40269}\n     - ALSA: usb-audio: Fix potential overflow of PCM transfer buffer\n       {CVE-2025-40269}\n   * CVE-2025-40149\n     - net: netdevice: Add operation ndo_sk_get_lower_dev {CVE-2025-40149}\n     - net/tls: Device offload to use lowest netdevice in chain\n       {CVE-2025-40149}\n     - tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock().\n       {CVE-2025-40149}\n   * CVE-2025-71089\n     - iommu: disable SVA when CONFIG_X86 is set {CVE-2025-71089}\n   * CVE-2026-23234\n     - f2fs: fix to avoid UAF in f2fs_write_end_io() {CVE-2026-23234}\n   * CVE-2026-23089\n     - ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free()\n       {CVE-2026-23089}\n   * CVE-2026-23074\n     - net/sched: Enforce that teql can only be used as root qdisc\n       {CVE-2026-23074}\n   * CVE-2026-23061\n     - can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak\n       {CVE-2026-23061}\n   * CVE-2026-23060\n     - crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN\n       spec {CVE-2026-23060}\n   * CVE-2026-22997\n     - net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session\n       upon receiving the second rts {CVE-2026-22997}\n   * CVE-2026-22991\n     - libceph: make free_choose_arg_map() resilient to partial allocation\n       {CVE-2026-22991}\n   * CVE-2026-22990\n     - libceph: replace overzealous BUG_ON in osdmap_apply_incremental()\n       {CVE-2026-22990}\n   * CVE-2026-22978\n     - wifi: avoid kernel-infoleak from struct iw_point {CVE-2026-22978}\n   * CVE-2026-22977\n     - net: sock: fix hardened usercopy panic in sock_recv_errqueue\n       {CVE-2026-22977}\n   * CVE-2025-71154\n     - net: usb: rtl8150: fix memory leak on usb_submit_urb() failure\n       {CVE-2025-71154}\n   * CVE-2025-71085\n     - ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr()\n       {CVE-2025-71085}\n   * CVE-2025-68734\n     - isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n       {CVE-2025-68734}\n   * CVE-2025-68349\n     - NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in\n       pnfs_mark_layout_stateid_invalid {CVE-2025-68349}\n   * CVE-2025-68340\n     - team: Move team device type change at the end of team_port_add\n       {CVE-2025-68340}\n   * CVE-2025-68325\n     - net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop\n       {CVE-2025-68325}\n   * CVE-2025-68287\n     - usb: dwc3: Fix race condition between concurrent dwc3_remove_requests()\n       call paths {CVE-2025-68287}\n   * CVE-2025-68285\n     - libceph: fix potential use-after-free in have_mon_and_osd_map()\n       {CVE-2025-68285}\n   * CVE-2025-68241\n     - ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe\n       {CVE-2025-68241}\n   * CVE-2025-68229\n     - scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n       {CVE-2025-68229}\n   * CVE-2025-68220\n     - net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return\n       NULL on error {CVE-2025-68220}\n   * CVE-2025-68194\n     - media: imon: make send_packet() more robust {CVE-2025-68194}\n   * CVE-2025-68192\n     - net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n       {CVE-2025-68192}\n   * CVE-2025-68185\n     - nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode\n       dereferencing {CVE-2025-68185}\n   * CVE-2025-68168\n     - jfs: fix uninitialized waitqueue in transaction manager {CVE-2025-68168}\n   * CVE-2025-40363\n     - net: ipv6: fix field-spanning memcpy warning in AH output\n       {CVE-2025-40363}\n   * CVE-2025-40331\n     - sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}\n   * CVE-2025-40322\n     - fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}\n   * CVE-2025-40317\n     - regmap: slimbus: fix bus_context pointer in regmap init calls\n       {CVE-2025-40317}\n   * CVE-2025-40315\n     - usb: gadget: f_fs: Fix epfile null pointer access after ep enable.\n       {CVE-2025-40315}\n   * CVE-2025-40309\n     - Bluetooth: SCO: Fix UAF on sco_conn_free {CVE-2025-40309}\n   * CVE-2025-40308\n     - Bluetooth: bcsp: receive data only if registered {CVE-2025-40308}\n   * CVE-2025-40306\n     - orangefs: fix xattr related buffer overflow... {CVE-2025-40306}\n   * CVE-2025-40304\n     - fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds\n       {CVE-2025-40304}\n   * CVE-2025-40283\n     - Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF\n       {CVE-2025-40283}\n   * CVE-2025-40282\n     - Bluetooth: 6lowpan: reset link-local header on ipv6 recv path\n       {CVE-2025-40282}\n   * CVE-2025-40277\n     - drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n       {CVE-2025-40277}\n   * CVE-2025-40275\n     - ALSA: usb-audio: Fix NULL pointer dereference in\n       snd_usb_mixer_controls_badd {CVE-2025-40275}\n   * CVE-2025-40264\n     - be2net: pass wrb_params in case of OS2BMC {CVE-2025-40264}\n   * CVE-2025-40263\n     - Input: cros_ec_keyb - fix an invalid memory access {CVE-2025-40263}\n   * CVE-2025-40259\n     - scsi: sg: Do not sleep in atomic context {CVE-2025-40259}\n   * CVE-2025-40254\n     - net: openvswitch: remove never-working support for setting nsh fields\n       {CVE-2025-40254}\n   * CVE-2025-40248\n     - vsock: Ignore signal/timeout on connect() if already established\n       {CVE-2025-40248}\n   * CVE-2025-40211\n     - ACPI: video: Fix use-after-free in acpi_video_switch_brightness()\n       {CVE-2025-40211}\n   * CVE-2025-40106\n     - comedi: fix divide-by-zero in comedi_buf_munge() {CVE-2025-40106}\n   * CVE-2025-40087\n     - NFSD: Define a proc_layoutcommit for the FlexFiles layout type\n       {CVE-2025-40087}\n   * CVE-2025-40055\n     - ocfs2: fix double free in user_cluster_connect() {CVE-2025-40055}\n   * CVE-2025-39945\n     - cnic: Fix use-after-free bugs in cnic_delete_task {CVE-2025-39945}\n   * CVE-2025-39738\n     - btrfs: do proper error handling in create_reloc_root {CVE-2025-39738}\n     - btrfs: do not allow relocation of partially dropped subvolumes\n       {CVE-2025-39738}\n   * CVE-2025-39685\n     - comedi: pcl726: Prevent invalid irq number {CVE-2025-39685}\n   * CVE-2024-46830\n     - KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS\n       {CVE-2024-46830}\n   * CVE-2024-41014\n     - xfs: add bounds checking to xlog_recover_process_data {CVE-2024-41014}\n   * CVE-2025-39866\n     - fs: writeback: fix use-after-free in __mark_inode_dirty()\n       {CVE-2025-39866}\n   * CVE-2025-39686\n     - comedi: Fix some signed shift left operations {CVE-2025-39686}\n     - comedi: Make insn_rw_emulate_bits() do insn-\u003en samples {CVE-2025-39686}\n   * CVE-2025-39766\n     - net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit\n       {CVE-2025-39766}\n   * CVE-2025-39828\n     - net/atm: remove the atmdev_ops {get, set}sockopt methods\n       {CVE-2025-39828}\n     - atm: atmtcp: Free invalid length skb in atmtcp_c_send().\n       {CVE-2025-39828}\n     - atm: Revert atm_account_tx() if copy_from_iter_full() fails.\n       {CVE-2025-39828}\n     - atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control().\n       {CVE-2025-39828}\n   * CVE-2022-49267\n     - mmc: core: Do not export MMC_NAME= and MODALIAS=mmc:block for SDIO cards\n       {CVE-2022-49267}\n     - mmc: core: Export device/vendor ids from Common CIS for SDIO cards\n       {CVE-2022-49267}\n     - mmc: sdio: Extend sdio_config_attr macro and use it also for modalias\n       {CVE-2022-49267}\n     - mmc: sdio: Export SDIO revision and info strings to userspace\n       {CVE-2022-49267}\n     - mmc: sdio: Parse CISTPL_VERS_1 major and minor revision numbers\n       {CVE-2022-49267}\n     - mmc: core: use sysfs_emit() instead of sprintf() {CVE-2022-49267}\n   * CVE-2025-39967\n     - fbcon: fix integer overflow in fbcon_do_set_font {CVE-2025-39967}\n   * CVE-2025-38108\n     - net_sched: red: fix a race in __red_change() {CVE-2025-38108}\n   * CVE-2025-38212\n     - ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n   * CVE-2025-38403\n     - vsock/vmci: Clear the vmci transport packet properly when initializing\n       it {CVE-2025-38403}\n   * CVE-2025-38464\n     - tipc: Fix use-after-free in tipc_conn_close(). {CVE-2025-38464}\n   * CVE-2025-38555\n     - usb: gadget : fix use-after-free in composite_dev_cleanup()\n       {CVE-2025-38555}\n   * CVE-2025-38652\n     - f2fs: fix to avoid out-of-boundary access in devs.path {CVE-2025-38652}\n   * CVE-2025-38677\n     - f2fs: fix to avoid out-of-boundary access in dnode page {CVE-2025-38677}\n   * CVE-2025-38713\n     - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n       {CVE-2025-38713}\n   * CVE-2025-38714\n     - hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() {CVE-2025-38714}\n   * CVE-2025-38715\n     - hfs: fix slab-out-of-bounds in hfs_bnode_read() {CVE-2025-38715}\n   * CVE-2025-38729\n     - ALSA: usb-audio: Validate UAC3 power domain descriptors, too\n       {CVE-2025-38729}\n   * CVE-2025-39691\n     - fs/buffer: fix use-after-free when call bh_read() helper\n       {CVE-2025-39691}\n   * CVE-2025-39743\n     - jfs: truncate good inode pages when hard link is 0 {CVE-2025-39743}\n   * CVE-2025-39783\n     - PCI: endpoint: Fix configfs group list head handling {CVE-2025-39783}\n   * CVE-2025-39824\n     - HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}\n   * CVE-2025-39839\n     - batman-adv: fix OOB read/write in network-coding decode {CVE-2025-39839}\n   * CVE-2025-39913\n     - tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to\n       allocate psock-\u003ecork. {CVE-2025-39913}\n   * CVE-2025-40240\n     - sctp: avoid NULL dereference when chunk data buffer is missing\n       {CVE-2025-40240}\n   * CVE-2025-38004\n     - can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}\n   * Miscellaneous upstream changes\n     - wifi: wilc1000: avoid buffer overflow in WID string configuration\n       {CVE-2025-39952}\n     - Revert \"dm-bufio: don't schedule in atomic context {CVE-2025-37928}\"","status":"published","published":"2026-04-03T17:49:22Z","modified":"2026-06-04T10:03:46.1958865Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"CLSA-2026-1775779453","title":"Fix of 119 CVEs","description":"   * CVE-2025-39743\n     - jfs: truncate good inode pages when hard link is 0 {CVE-2025-39743}\n   * CVE-2025-39685\n     - comedi: pcl726: Prevent invalid irq number {CVE-2025-39685}\n   * CVE-2025-38713\n     - hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()\n       {CVE-2025-38713}\n   * CVE-2025-38699\n     - scsi: bfa: Double-free fix {CVE-2025-38699}\n   * CVE-2025-38697\n     - jfs: upper bound check of tree index in dbAllocAG {CVE-2025-38697}\n   * CVE-2025-38680\n     - media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()\n       {CVE-2025-38680}\n   * CVE-2025-38677\n     - f2fs: fix to avoid out-of-boundary access in dnode page {CVE-2025-38677}\n   * CVE-2025-38572\n     - ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}\n   * CVE-2025-38538\n     - dmaengine: nbpfaxi: Fix memory corruption in probe() {CVE-2025-38538}\n   * CVE-2025-38530\n     - comedi: pcl812: Fix bit shift out of bounds {CVE-2025-38530}\n   * CVE-2025-38529\n     - comedi: aio_iiro_16: Fix bit shift out of bounds {CVE-2025-38529}\n   * CVE-2025-38494\n     - HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}\n   * CVE-2025-38482\n     - comedi: das6402: Fix bit shift out of bounds {CVE-2025-38482}\n   * CVE-2025-38428\n     - Input: ims-pcu - check record size in ims_pcu_flash_firmware()\n       {CVE-2025-38428}\n   * CVE-2025-38416\n     - NFC: nci: uart: Set tty-\u003edisc_data only in success path {CVE-2025-38416}\n   * CVE-2025-38415\n     - Squashfs: check return result of sb_min_blocksize {CVE-2025-38415}\n   * CVE-2025-38403\n     - vsock/vmci: Clear the vmci transport packet properly when initializing\n       it {CVE-2025-38403}\n   * CVE-2025-38286\n     - pinctrl: at91: Fix possible out-of-boundary access {CVE-2025-38286}\n   * CVE-2025-38245\n     - atm: Release atm_dev_mutex after removing procfs in\n       atm_dev_deregister(). {CVE-2025-38245}\n   * CVE-2025-38212\n     - ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}\n   * CVE-2025-38204\n     - jfs: fix array-index-out-of-bounds read in add_missing_indices\n       {CVE-2025-38204}\n   * CVE-2025-38157\n     - wifi: ath9k_htc: Abort software beacon handling if disabled\n       {CVE-2025-38157}\n   * CVE-2025-38079\n     - crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}\n   * CVE-2025-38051\n     - smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}\n   * CVE-2023-53676\n     - scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()\n       {CVE-2023-53676}\n   * CVE-2023-53675\n     - scsi: ses: Fix possible desc_ptr out-of-bounds accesses {CVE-2023-53675}\n   * CVE-2023-53668\n     - ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n   * CVE-2023-53622\n     - gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n   * CVE-2023-53616\n     - jfs: fix invalid free of JFS_IP(ipimap)-\u003ei_imap in diUnmount\n       {CVE-2023-53616}\n   * CVE-2023-53608\n     - nilfs2: fix potential UAF of struct nilfs_sc_info in\n       nilfs_segctor_thread() {CVE-2023-53608}\n   * CVE-2023-53587\n     - ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n   * CVE-2023-53569\n     - ext2: Check block size validity during mount {CVE-2023-53569}\n   * CVE-2023-53559\n     - ip_vti: fix potential slab-use-after-free in decode_session6\n       {CVE-2023-53559}\n   * CVE-2023-53541\n     - mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write\n       {CVE-2023-53541}\n   * CVE-2023-53521\n     - scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() {CVE-2023-53521}\n   * CVE-2023-53506\n     - udf: Do not bother merging very long extents {CVE-2023-53506}\n   * CVE-2023-53485\n     - fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev\n       {CVE-2023-53485}\n   * CVE-2023-53484\n     - lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries\n       {CVE-2023-53484}\n   * CVE-2023-53454\n     - HID: multitouch: Correct devm device reference for hidinput input_dev\n       name {CVE-2023-53454}\n   * CVE-2023-53322\n     - scsi: qla2xxx: Wait for io return on terminate rport {CVE-2023-53322}\n   * CVE-2023-53311\n     - nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput\n       {CVE-2023-53311}\n   * CVE-2023-53259\n     - VMCI: check context-\u003enotify_page after call to get_user_pages_fast() to\n       avoid GPF {CVE-2023-53259}\n   * CVE-2023-53219\n     - media: netup_unidvb: fix use-after-free at del_timer() {CVE-2023-53219}\n   * CVE-2023-53138\n     - net: caif: Fix use-after-free in cfusbl_device_notify() {CVE-2023-53138}\n   * CVE-2023-53075\n     - ftrace: Fix invalid address access in lookup_rec() when index is 0\n       {CVE-2023-53075}\n   * CVE-2023-53035\n     - nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy() {CVE-2023-53035}\n   * CVE-2022-50542\n     - media: si470x: Fix use-after-free in si470x_int_in_callback()\n       {CVE-2022-50542}\n   * CVE-2022-50496\n     - dm cache: Fix UAF in destroy() {CVE-2022-50496}\n   * CVE-2022-50478\n     - nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset()\n       {CVE-2022-50478}\n   * CVE-2022-50470\n     - xhci: Remove device endpoints from bandwidth list when freeing the\n       device {CVE-2022-50470}\n   * CVE-2022-50432\n     - kernfs: fix use-after-free in __kernfs_remove {CVE-2022-50432}\n   * CVE-2022-50423\n     - ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage()\n       {CVE-2022-50423}\n   * CVE-2022-50419\n     - Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times\n       {CVE-2022-50419}\n   * CVE-2022-50411\n     - ACPICA: Fix error code path in acpi_ds_call_control_method()\n       {CVE-2022-50411}\n   * CVE-2022-50394\n     - i2c: ismt: Fix an out-of-bounds bug in ismt_access() {CVE-2022-50394}\n   * CVE-2022-50384\n     - staging: vme_user: Fix possible UAF in tsi148_dma_list_add\n       {CVE-2022-50384}\n   * CVE-2022-50333\n     - fs: jfs: fix shift-out-of-bounds in dbDiscardAG {CVE-2022-50333}\n   * CVE-2022-50301\n     - iommu/omap: Fix buffer overflow in debugfs {CVE-2022-50301}\n   * CVE-2022-50094\n     - spmi: trace: fix stack-out-of-bound access in SPMI tracing functions\n       {CVE-2022-50094}\n   * CVE-2022-50022\n     - drivers:md:fix a potential use-after-free bug {CVE-2022-50022}\n   * CVE-2022-49945\n     - hwmon: (gpio-fan) Fix array out of bounds access {CVE-2022-49945}\n   * CVE-2022-49865\n     - ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to\n       network {CVE-2022-49865}\n   * CVE-2022-49775\n     - tcp: cdg: allow tcp_cdg_release() to be called multiple times\n       {CVE-2022-49775}\n   * CVE-2022-49581\n     - be2net: Fix buffer overflow in be_get_module_eeprom {CVE-2022-49581}\n   * CVE-2022-49503\n     - ath9k_htc: fix potential out of bounds access with invalid\n       rxstatus-\u003ers_keyix {CVE-2022-49503}\n   * CVE-2021-47142\n     - drm/amdgpu: Fix a use-after-free {CVE-2021-47142}\n   * CVE-url: https://ubuntu.com/security/CVE-2025-38477\n     - net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in\n       qfq_delete_class\n   * Focal update: v5.4.255 upstream stable release (LP: #2039440)\n     - Bluetooth: L2CAP: Fix use-after-free\n   * Bionic update: upstream stable patchset 2022-11-15 (LP: #1996650)\n     - Bluetooth: L2CAP: Fix user-after-free\n     - wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit()\n   * Focal update: v5.4.253 upstream stable release (LP: #2038652)\n     - ip6mr: Fix skb_under_panic in ip6mr_cache_report()\n   * Focal update: v5.4.224 upstream stable release (LP: #1999273)\n     - ipvs: use explicitly signed chars\n     - ipvs: fix WARNING in __ip_vs_cleanup_batch()\n     - ipvs: fix WARNING in ip_vs_app_net_cleanup()\n   * Bionic update: upstream stable patchset 2022-10-18 (LP: #1993349)\n     - vt: Clear selection before changing the font\n   * Focal update: v5.4.237 upstream stable release (LP: #2023420)\n     - fs: prevent out-of-bounds array speculation when closing a file\n       descriptor\n   * Focal update: v5.4.231 upstream stable release (LP: #2011226)\n     - netlink: prevent potential spectre v1 gadgets\n   * Bionic update: upstream stable patchset 2022-09-23 (LP: #1990698)\n     - ALSA: bcd2000: Fix a UAF bug on the error path of probing\n     - drm/radeon: fix potential buffer overflow in\n       ni_set_mc_special_registers()\n     - md-raid10: fix KASAN warning\n     - selinux: Add boundary check in put_entry()\n     - video: fbdev: vt8623fb: Check the size of screen before memset_io()\n     - video: fbdev: arkfb: Check the size of screen before memset_io()\n     - video: fbdev: s3fb: Check the size of screen before memset_io()\n   * Bionic update: upstream stable patchset 2023-02-06 (LP: #2006403)\n     - igb: Do not free q_vector unless new one was allocated\n   * Bionic update: upstream stable patchset 2023-01-20 (LP: #2003596)\n     - capabilities: fix undefined behavior in bit shift for CAP_TO_MASK\n     - net: mdio: fix undefined behavior in bit shift for __mdiobus_register\n   * CVE-url: https://ubuntu.com/security/CVE-2023-1989\n     - Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race\n       condition\n   * Focal update: v5.4.225 upstream stable release (LP: #2002347)\n     - ntfs: fix use-after-free in ntfs_attr_find()\n   * Focal update: Focal update: v5.4.235 upstream stable release\n     (LP: #2017706)\n     - wifi: brcmfmac: Fix potential stack-out-of-bounds in\n       brcmf_c_preinit_dcmds()\n   * Miscellaneous upstream changes\n     - debian: add control and changelog files\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - Merge branch 'master' into master-build\n     - vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint\n     - f2fs: return error when accessing insane flie offset\n     - f2fs: lost matching-pair of trace in f2fs_truncate_inode_blocks\n     - f2fs: fix to avoid out-of-bounds access in f2fs_truncate_inode_blocks()\n     - usb: vhci-hcd: Do not drop references before new references are gained\n     - tracing: Fix oob write in trace_seq_to_buffer()\n     - mtd: inftlcore: Add error check for inftl_read_oob()\n     - jbd2: remove wrong sb-\u003es_sequence check\n     - usb: dwc3: gadget: check that event count does not exceed event buffer\n       length\n     - ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control\n     - Bluetooth: hci_core: Fix use-after-free in vhci_flush()\n     - usb: xhci: Fix isochronous Ring Underrun/Overrun event handling\n     - Revert \"Bluetooth: btsdio: fix use after free bug in btsdio_remove due\n       to unfinished work\"\n     - scsi: target: Fix WRITE_SAME No Data Buffer crash\n     - net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too\n     - HID: core: Harden s32ton() against conversion to 0 bits\n     - scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()\n     - wifi: mac80211_hwsim: drop short frames\n     - ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer\n     - scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware\n       write","status":"published","published":"2026-10-21T08:53:18Z","modified":"2026-10-26T09:32:00.783544307Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"DLA-4327-1","title":"linux - security update","status":"published","published":"2025-10-13T00:00:00Z","modified":"2026-03-09T02:11:02.149849Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DLA-4328-1","title":"linux-6.1 - security update","status":"published","published":"2025-10-13T00:00:00Z","modified":"2026-03-09T02:10:14.677479Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DSA-6009-1","title":"linux - security update","status":"published","published":"2025-09-22T00:00:00Z","modified":"2026-03-09T02:10:23.945475Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"MGASA-2025-0234","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.105 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-10-09T20:24:52Z","modified":"2026-04-16T04:40:41.340027043Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2025-0235","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.105 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\nThe newer meta-task and mageia-repos packages are required to simplify\nthe correct installation of the kernel-stable-userspace-headers (for\nbackport kernel-stable) and back to kernel-userspace-headers (for 6.6\nkernels) packages see https://bugs.mageia.org/show_bug.cgi?id=34545.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2025-10-10T03:12:21Z","modified":"2026-04-16T04:42:23.092534093Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"SUSE-SU-2025:03600-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Correct typos of References tags in some patches\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for 'spurious' preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb 'force_immediate_exit' into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free 'ks-pcie-error-irq' on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert 'SUNRPC: Do not allow waiting for exiting tasks' (git-fixes).\n- Revert 'drm/amdgpu: fix incorrect vm flags to map bo' (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arch: arm64: Drop arm64 patches that may lead to module load failure (bsc#1250057).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- fs: Limit patch filenames to 100 characters (bsc#1249604).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206). \n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for 'netfilter: nf_tables: Audit log rule reset' (git-fixes).\n- kABI workaround for 'drm/dp: Add an EDID quirk for the DPCD register access probe' (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522). \n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- wrt: Regression fix for  wrt s2idle on AMD laptops (bsc#1243112).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-15T12:54:53Z","modified":"2026-03-23T04:48:49.308799Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03613-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50248: wifi: iwlwifi: mvm: fix double free on tx path (bsc#1249840).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50258: wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() (bsc#1249947).\n- CVE-2022-50381: md: fix a crash in mempool_free (bsc#1250257).\n- CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free (bsc#1250301).\n- CVE-2022-50401: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (bsc#1250140).\n- CVE-2022-50408: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() (bsc#1250391).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2025-21969: kABI workaround for l2cap_conn changes (bsc#1240784).\n- CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n\nThe following non-security bugs were fixed:\n\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (git-fixes).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879)\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rpm: Configure KABI checkingness macro (bsc#1249186)\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186)\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- use uniform permission checks for all mount propagation changes (git-fixes).\n","status":"published","published":"2025-10-16T05:47:42Z","modified":"2026-02-04T04:36:55.813082Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03614-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50242: drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() (bsc#1249696).\n- CVE-2022-50244: cxl: fix possible null-ptr-deref in cxl_pci_init_afu|adapter() (bsc#1249647).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50258: wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() (bsc#1249947).\n- CVE-2022-50265: kcm: annotate data-races around kcm-\u003erx_wait (bsc#1249744).\n- CVE-2022-50278: PNP: fix name memory leak in pnp_alloc_dev() (bsc#1249715).\n- CVE-2022-50285: mm,hugetlb: take hugetlb_lock before decrementing h-\u003eresv_huge_pages (bsc#1249803).\n- CVE-2022-50288: qlcnic: prevent -\u003edcb use-after-free on qlcnic_dcb_enable() failure (bsc#1249802).\n- CVE-2022-50291: kcm: annotate data-races around kcm-\u003erx_psock (bsc#1249798).\n- CVE-2022-50294: wifi: libertas: fix memory leak in lbs_init_adapter() (bsc#1249799).\n- CVE-2022-50297: wifi: ath9k: verify the expected usb_endpoints are present (bsc#1250250).\n- CVE-2022-50304: mm: export bdi_unregister (bsc#1249725).\n- CVE-2022-50311: cxl: Fix refcount leak in cxl_calc_capp_routing (bsc#1249720).\n- CVE-2022-50312: drivers: serial: jsm: fix some leaks in probe (bsc#1249716).\n- CVE-2022-50321: wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() (bsc#1249706).\n- CVE-2022-50330: crypto: cavium - prevent integer overflow loading firmware (bsc#1249700).\n- CVE-2022-50349: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (bsc#1249920).\n- CVE-2022-50352: net: hns: fix possible memory leak in hnae_ae_register() (bsc#1249922).\n- CVE-2022-50359: media: cx88: Fix a null-ptr-deref bug in buffer_prepare() (bsc#1250269).\n- CVE-2022-50365: skbuff: Account for tail adjustment during pull operations (bsc#1250084).\n- CVE-2022-50375: tty: serial: fsl_lpuart: disable dma rx/tx use flags in lpuart_dma_shutdown (bsc#1250132).\n- CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free (bsc#1250301).\n- CVE-2022-50396: net: sched: fix memory leak in tcindex_set_parms (bsc#1250104).\n- CVE-2022-50402: drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() (bsc#1250363).\n- CVE-2022-50405: net/tunnel: wait until all sk_user_data reader finish before releasing the sock (bsc#1250155).\n- CVE-2022-50406: iomap: iomap: fix memory corruption when recording errors during writeback (bsc#1250165).\n- CVE-2022-50408: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() (bsc#1250391).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2022-50419: Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times (bsc#1250394).\n- CVE-2023-53148: igb: Do not bring the device up after non-fatal error (bsc#1249842).\n- CVE-2023-53153: wifi: cfg80211: Partial revert 'wifi: cfg80211: Fix use after free for wext' (bsc#1249877).\n- CVE-2023-53176: serial: 8250: Fix oops for port-\u003epm on uart_change_pm() (bsc#1249991).\n- CVE-2023-53178: mm: zswap: fix missing folio cleanup in writeback race path (bsc#1249827 git-fix).\n- CVE-2023-53199: wifi: ath9k: hif_usb: clean up skbs if ath9k_hif_usb_rx_stream() fails (bsc#1249683).\n- CVE-2023-53201: RDMA/bnxt_re: wraparound mbox producer index (bsc#1249687).\n- CVE-2023-53226: wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet (bsc#1249658).\n- CVE-2023-53248: drm/amdgpu: install stub fence into potential unused fence pointers (bsc#1249779).\n- CVE-2023-53254: drivers: base: cacheinfo: Fix shared_cpu_map changes in event of CPU hotplug (bsc#1249871).\n- CVE-2023-53272: net: ena: fix shift-out-of-bounds in exponential backoff (bsc#1249917).\n- CVE-2023-53277: wifi: iwl3945: Add missing check for create_singlethread_workqueue (bsc#1249936).\n- CVE-2023-53288: drm/client: Fix memory leak in drm_client_modeset_probe (bsc#1250058).\n- CVE-2023-53298: nfc: fix memory leak of se_io context in nfc_genl_se_io (bsc#1249944).\n- CVE-2023-53302: wifi: iwl4965: Add missing check for create_singlethread_workqueue() (bsc#1249958).\n- CVE-2023-53305: Bluetooth: L2CAP: Fix use-after-free (bsc#1250049).\n- CVE-2023-53309: drm/radeon: Fix integer overflow in radeon_cs_parser_init (bsc#1250055).\n- CVE-2023-53317: ext4: fix WARNING in mb_find_extent (bsc#1250081).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53335: RDMA/cxgb4: Fix potential null-ptr-deref in pass_establish() (bsc#1250072).\n- CVE-2023-53344: can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write (bsc#1250023).\n- CVE-2023-53348: btrfs: fix deadlock when aborting transaction during relocation with scrub (bsc#1250018).\n- CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).\n- CVE-2023-53384: wifi: mwifiex: avoid possible NULL skb pointer dereference (bsc#1250127).\n- CVE-2023-53393: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device (bsc#1250114).\n- CVE-2023-53395: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer (bsc#1250358).\n- CVE-2023-53397: modpost: fix off by one in is_executable_section() (bsc#1250125).\n- CVE-2023-53400: ALSA: hda: Fix Oops by 9.1 surround channel names (bsc#1250328).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2023-53441: bpf: cpumap: Fix memory leak in cpu_map_update_elem (bsc#1250150).\n- CVE-2024-53194: PCI: Fix use-after-free of slot-\u003ebus on hot remove (bsc#1235459).\n- CVE-2024-58240: tls: separate no-async decryption request handling from async (bsc#1248847).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38602: wifi: iwlwifi: Fix error code in iwl_op_mode_dvm_start() (bsc#1248341).\n- CVE-2025-38604: wifi: rtl818x: Kill URBs before clearing tx status queue (bsc#1248333).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38624: PCI: pnv_php: Clean up allocated IRQs on unplug (bsc#1248617).\n- CVE-2025-38632: pinmux: fix race causing mux_owner NULL with active mux_usecount (bsc#1248669).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38665: can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode (bsc#1248648).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38702: fbdev: fix potential buffer overflow in do_register_framebuffer() (bsc#1249254).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38712: hfsplus: do not use BUG_ON() in hfsplus_create_attributes_file() (bsc#1249194).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-38729: ALSA: usb-audio: Validate UAC3 power domain descriptors, too (bsc#1249164).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39706: drm/amdkfd: Destroy KFD debugfs after destroy KFD wq (bsc#1249413).\n- CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39757: ALSA: usb-audio: Fix size validation in convert_chmap_v3() (bsc#1249515).\n- CVE-2025-39760: usb: core: config: Prevent OOB read in SS endpoint companion parsing (bsc#1249598).\n- CVE-2025-39763: ACPICA: Fix error code path in acpi_ds_call_control_method() (bsc#1249615).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39800: btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (bsc#1250177).\n- CVE-2025-39808: HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (bsc#1250088).\n- CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).\n- CVE-2025-39833: mISDN: hfcpci: Fix warning when deleting uninitialized timer (bsc#1250028).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).\n- CVE-2025-39863: wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (bsc#1250281).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- Bluetooth: hci_core: Fix calling mgmt_device_connected (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Do not self obsolete older kernel variants\n- Limit patch filenames to 100 characters (bsc#1249604).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- build_bug.h: add wrapper for _Static_assert (bsc#1249186).\n- dma-buf: add dma_fence_get_stub (bsc#1249779)\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346).\n- l2tp: remove unused list_head member in l2tp_tunnel (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- tipc: improve function tipc_wait_for_cond() (bsc#1249037).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- x86/tsc: Append the 'tsc=' description for the 'tsc=unstable' boot parameter (git-fixes).\n","status":"published","published":"2025-10-16T05:48:12Z","modified":"2026-02-04T03:03:12.918222Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03615-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53257: wifi: mac80211: check S1G action frame size (bsc#1249869).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).\n- CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).\n- CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).\n- CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).\n\nThe following non-security bugs were fixed:\n\n- !CONFIG \u0026 reference -\u003e this is bug, immediate fail\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Do not self obsolete older kernel variants\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- Update config files. (bsc#1249186) Enable where we define KABI refs + rely on Kconfig deps.\n- build_bug.h: Add KABI assert (bsc#1249186).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- net/sched: ets: use old 'nbands' while purging unused classes (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- supported.conf: mark hyperv_drm as external\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n","status":"published","published":"2025-10-16T05:49:13Z","modified":"2026-02-04T04:05:18.57449Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03626-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50248: wifi: iwlwifi: mvm: fix double free on tx path (bsc#1249840).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50258: wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() (bsc#1249947).\n- CVE-2022-50381: md: fix a crash in mempool_free (bsc#1250257).\n- CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free (bsc#1250301).\n- CVE-2022-50401: nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (bsc#1250140).\n- CVE-2022-50408: wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() (bsc#1250391).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2022-50412: drm: bridge: adv7511: unregister cec i2c device after cec adapter (bsc#1250189).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53220: media: az6007: Fix null-ptr-deref in az6007_i2c_xfer() (bsc#1250337).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2024-53093: nvme-multipath: defer partition scanning (bsc#1233640).\n- CVE-2025-21969: kABI workaround for l2cap_conn changes (bsc#1240784).\n- CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).\n- CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).\n- CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n\nThe following non-security bugs were fixed:\n\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- git_sort: Make tests independent of environment.\n- hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (git-fixes).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346).\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- scripts/python/kss-dashboard: attempt getting smash data\n- scripts/python/kss-dashboard: fetch into repos if stale\n- scripts/python/kss-dashboard: implement CVSSv3.1 score consistency check\n- scripts/python/kss-dashboard: prepare for the alternative CVE branch\n- scripts/python/kss-dashboard: simplify control flow\n- scripts/python/kss-dashboard: speed up patch checking a bit\n- scripts/python/kss-dashboard: use decorator to handle exceptions\n- scripts/tar-up: Remove mkspec only affter running it.\n- scripts: Import arch-symbols script from packaging\n- scripts: Import guards script from packaging\n- scripts: test_linux_git.py: Do not complain about missing cwd\n- sequence-patch: Use arch-symbols\n- suse_git/header: Complain about patch filenames over 100 characters.\n- tar-up: Also sort generated tar archives\n- tar-up: Handle multiple levels of symlinks\n- tar-up: Normalize file modes to ones supported by git\n- tar-up: Remove mkspec and its inputs as from target directory (bsc#1250522).\n- tar-up: Remove the $build_dir prefix when in $build_dir\n- tar-up: Set owner of files in generated tar archives to root rather than nobody\n- tar_up: Handle symlinks in rpm directory\n- use uniform permission checks for all mount propagation changes (git-fixes).\n","status":"published","published":"2025-10-17T06:14:11Z","modified":"2026-02-04T03:58:44.137535Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03628-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).\n- CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).\n- CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).\n- CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).\n- CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).\n- CVE-2025-38470: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime (bsc#1247288).\n- CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).\n- CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).\n- CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).\n\nThe following non-security bugs were fixed:\n\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- README.BRANCH: Add Lidong Zhong as a SLE15-SP4-LTSS co-maintainer.\n- Revert backported patches for bsc#1238160 because the CVSS less than 7.0\n- Update config files. (bsc#1249186) Enable where we define KABI refs + rely on Kconfig deps.\n- btrfs: avoid NULL pointer dereference if no valid extent tree (bsc#1249158).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- kabi/severities: ignore kABI for atheros helper modules The symbols are used only internally by atheros drivers.\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- net/sched: ets: use old 'nbands' while purging unused classes (git-fixes).\n- netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186). \n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- use uniform permission checks for all mount propagation changes (git-fixes).\n","status":"published","published":"2025-10-17T11:34:59Z","modified":"2026-02-04T03:26:33.317216Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:03634-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-46733: btrfs: fix qgroup reserve leaks in cow_file_range (bsc#1230708).\n- CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).\n- CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).\n- CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).\n- CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).\n- CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).\n- CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).\n- CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).\n- CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).\n- CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).\n- CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).\n- CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38245: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister() (bsc#1246193).\n- CVE-2025-38251: atm: clip: prevent NULL deref in clip_push() (bsc#1246181).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38360: drm/amd/display: Add more checks for DSC / HUBP ONO guarantees (bsc#1247078).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38439: bnxt_en: Set DMA unmap len correctly for XDP_REDIRECT (bsc#1247155).\n- CVE-2025-38441: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() (bsc#1247167).\n- CVE-2025-38444: raid10: cleanup memleak at raid10_make_request (bsc#1247162).\n- CVE-2025-38445: md/raid1: Fix stack memory use after return in raid1_reshape (bsc#1247229).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38458: atm: clip: Fix NULL pointer dereference in vcc_sendmsg() (bsc#1247116).\n- CVE-2025-38459: atm: clip: Fix infinite recursive call of clip_push() (bsc#1247119).\n- CVE-2025-38464: tipc: Fix use-after-free in tipc_conn_close() (bsc#1247112).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38472: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (bsc#1247313).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38490: net: libwx: remove duplicate page_pool_put_full_page() (bsc#1247243).\n- CVE-2025-38491: mptcp: make fallback action and fallback decision atomic (bsc#1247280).\n- CVE-2025-38499: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns (bsc#1247976).\n- CVE-2025-38500: xfrm: interface: fix use-after-free after changing collect_md xfrm interface (bsc#1248088).\n- CVE-2025-38506: KVM: Allow CPU to reschedule while setting per-page memory attributes (bsc#1248186).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38520: drm/amdkfd: Do not call mmput from MMU notifier callback (bsc#1248217).\n- CVE-2025-38524: rxrpc: Fix recv-recv race of completed call (bsc#1248194).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38528: bpf: Reject %p% format string in bprintf-like helpers (bsc#1248198).\n- CVE-2025-38531: iio: common: st_sensors: Fix use of uninitialize device structs (bsc#1248205).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc (bsc#1248223).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38560: x86/sev: Evict cache lines during SNP memory validation (bsc#1248312).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38585: staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int() (bsc#1248355).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38591: bpf: Reject narrower access to pointer ctx fields (bsc#1248363).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38608: bpf, ktls: Fix data corruption when using bpf_msg_pop_data() in ktls (bsc#1248338).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38618: vsock: Do not allow binding to VMADDR_PORT_ANY (bsc#1248511).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39828: kABI workaround for struct atmdev_ops extension (bsc#1250205).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered (stable-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: pfr_update: Fix the driver update version check (git-fixes).\n- ACPI: processor: fix acpi_object initialization (stable-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: processor: perflib: Move problematic pr-\u003eperformance check (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add Framework Laptop 13 (AMD Ryzen AI 300) to quirks (stable-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Add support for HP EliteBook x360 830 G6 and EliteBook 830 G6 (stable-fixes).\n- ALSA: hda/realtek: Audio disappears on HP 15-fc000 after warm boot again (git-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic on ASUS Zenbook 14 (git-fixes).\n- ALSA: hda/realtek: Fix headset mic on HONOR BRB-X (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: Disable jack polling at shutdown (stable-fixes).\n- ALSA: hda: Handle the jack polling always via a work (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: intel8x0: Fix incorrect codec index usage in mixer for ICH4 (stable-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: pcm: Rewrite recalculate_boundary() to avoid costly loop (stable-fixes).\n- ALSA: scarlett2: Add retry on -EPROTO from scarlett2_usb_tx() (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Avoid precedence issues in mixer_quirks macros (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Fix size validation in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Use correct sub-type for UAC3 feature unit validation (git-fixes).\n- ALSA: usb-audio: Validate UAC3 cluster segment descriptors (git-fixes).\n- ALSA: usb-audio: Validate UAC3 power domain descriptors, too (git-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: avs: Fix uninitialized pointer error in probe() (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: fix SND_SOC_SOF dependencies (stable-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: amd: yc: Add DMI entries to support HP 15-fb1xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for HP Laptop 17 cp-2033dx (stable-fixes).\n- ASoC: amd: yc: add DMI quirk for ASUS M6501RM (stable-fixes).\n- ASoC: codecs: rt5640: Retry DEVICE_ID verification (stable-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (stable-fixes).\n- ASoC: hdac_hdmi: Rate limit logging on connection and disconnection (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: soc-dapm: set bias_level if snd_soc_dapm_set_bias_level() was successed (stable-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: btusb: Add USB ID 3625:010b for TP-LINK Archer TX10UB Nano (stable-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_conn: do return error from hci_enhanced_setup_sync() (git-fixes).\n- Bluetooth: hci_event: Detect if HCI_EV_NUM_COMP_PKTS is unbalanced (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_event: Mark connection as closed during suspend disconnect (git-fixes).\n- Bluetooth: hci_event: Treat UNKNOWN_CONN_ID on disconnect as success (git-fixes).\n- Bluetooth: hci_event: fix MTU for BN == 0 in CIS Established (git-fixes).\n- Bluetooth: hci_sock: Reset cookie to zero in hci_sock_free_cookie() (stable-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: hci_sync: fix set_local_name race condition (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Correct typos of References tags in some patches\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- HID: asus: fix UAF via HID_CLAIMED_INPUT validation (git-fixes).\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() (git-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for 'spurious' preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb 'force_immediate_exit' into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/portdrv: Use is_pciehp instead of is_hotplug_bridge (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Add ACS quirk for Loongson PCIe (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: Support Immediate Readiness on devices without PM capabilities (git-fixes).\n- PCI: apple: Fix missing OF node reference in apple_pcie_setup_port (git-fixes).\n- PCI: imx6: Add IMX8MM_EP and IMX8MP_EP fixed 256-byte BAR 4 in epc_features (git-fixes).\n- PCI: imx6: Delay link start until configfs 'start' written (git-fixes).\n- PCI: imx6: Remove apps_reset toggling from imx_pcie_{assert/deassert}_core_reset (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free 'ks-pcie-error-irq' on exit (git-fixes).\n- PCI: pnv_php: Clean up allocated IRQs on unplug (bsc#1215199).\n- PCI: pnv_php: Work around switches with broken presence detection (bsc#1215199).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: rockchip: Set Target Link Speed to 5.0 GT/s before retraining (git-fixes).\n- PCI: rockchip: Use standard PCIe definitions (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: governor: Replace sscanf() with kstrtoul() in set_freq_store() (stable-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: runtime: Clear power.needs_force_resume in pm_runtime_reinit() (stable-fixes).\n- PM: sleep: console: Fix the black screen issue (stable-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RAS/AMD/ATL: Include row bit in row retirement (bsc#1242034).\n- RAS/AMD/FMPM: Get masked address (bsc#1242034).\n- RAS/AMD/FMPM: Use atl internal.h for INVALID_SPA (bsc#1242034).\n- RDMA/bnxt_re: Fix a possible memory leak in the driver (git-fixes)\n- RDMA/bnxt_re: Fix to do SRQ armena by default (git-fixes)\n- RDMA/bnxt_re: Fix to initialize the PBL array (git-fixes)\n- RDMA/bnxt_re: Fix to remove workload check in SRQ limit path (git-fixes)\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/core: reduce stack using in nldev_stat_get_doit() (git-fixes)\n- RDMA/erdma: Fix ignored return value of init_kernel_qp (git-fixes)\n- RDMA/hns: Fix dip entries leak on devices newer than hip09 (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (git-fixes)\n- Refresh patches.suse/kernel-add-product-identifying-information-to-kernel-build.patch. (bsc#1249186)\n- Revert 'SUNRPC: Do not allow waiting for exiting tasks' (git-fixes).\n- Revert 'drm/amdgpu: fix incorrect vm flags to map bo' (stable-fixes).\n- Revert 'gpio: mlxbf3: only get IRQ for device instance 0' (git-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Foxconn T99W709 (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- USB: storage: Add unusual-devs entry for Novatek NTK96550-based camera (stable-fixes).\n- USB: storage: Ignore driver CD mode for Realtek multi-mode Wi-Fi dongles (stable-fixes).\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- aoe: defer rexmit timer downdev work to workqueue (git-fixes).\n- arch/powerpc: Remove .interp section in vmlinux (bsc#1215199).\n- arm64/cpufeatures/kvm: Add ARMv8.9 FEAT_ECBHB bits in ID_AA64MMFR1 (git-fixes)\n- arm64/entry: Mask DAIF in cpu_switch_to(), call_on_irq_stack() (git-fixes)\n- arm64/mm: Check PUD_TYPE_TABLE in pud_bad() (git-fixes)\n- arm64: Add support for HIP09 Spectre-BHB mitigation (git-fixes)\n- arm64: Filter out SME hwcaps when FEAT_SME isn't implemented (git-fixes)\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: Restrict pagetable teardown to avoid false warning (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: apple: t8103: Fix PCIe BCM4377 nodename (git-fixes)\n- arm64: dts: freescale: imx8mm-verdin: Keep LDO5 always on (git-fixes)\n- arm64: dts: imx8mm-beacon: Fix HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mm-beacon: Fix RTC capacitive load (git-fixes)\n- arm64: dts: imx8mm-venice-gw700x: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mm-venice-gw7901: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mm-venice-gw7902: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mm-venice-gw7903: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mm-venice-gw7904: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mn-beacon: Fix HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mn-beacon: Fix RTC capacitive load (git-fixes)\n- arm64: dts: imx8mn-venice-gw7902: Increase HS400 USDHC clock speed (git-fixes)\n- arm64: dts: imx8mp-beacon: Fix RTC capacitive load (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: Update eMMC for NanoPi R5 series (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix endpoint dtc warning for PX30 ISP (git-fixes)\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- arm64: tegra: Drop remaining serial clock-names and reset-names (git-fixes)\n- arm64: tegra: p2597: Fix gpio for vdd-1v8-dis regulator (git-fixes)\n- arm64: zynqmp: add clock-output-names property in clock nodes (git-fixes)\n- ata: libata-scsi: Fix CDL control (git-fixes).\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- block: fix kobject leak in blk_unregister_queue (git-fixes).\n- block: mtip32xx: Fix usage of dma_map_sg() (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: fix kfunc btf caching for modules (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpf: use kvzmalloc to allocate BPF verifier environment (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: convert BUG_ON in btrfs_reloc_cow_block() to proper error handling (git-fixes).\n- btrfs: correctly escape subvol in btrfs_show_options() (git-fixes).\n- btrfs: fix adding block group to a reclaim list and the unused list during reclaim (git-fixes).\n- btrfs: fix bitmap leak when loading free space cache on duplicate entry (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix data race when accessing the inode's disk_i_size at btrfs_drop_extents() (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: fix the length of reserved qgroup to free (bsc#1240708)\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: retry block group reclaim without infinite loop (git-fixes).\n- btrfs: return accurate error code on open failure in open_fs_devices() (bsc#1233120)\n- btrfs: run delayed iputs when flushing delalloc (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: update target inode's ctime on unlink (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- cdx: Fix off-by-one error in cdx_rpmsg_probe() (git-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- char: misc: Fix improper and inaccurate error code returned by misc_init() (stable-fixes).\n- comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() (git-fixes).\n- comedi: Make insn_rw_emulate_bits() do insn-\u003en samples (git-fixes).\n- comedi: fix race between polling and detaching (git-fixes).\n- comedi: pcl726: Prevent invalid irq number (git-fixes).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/hpre - fix dma unmap sequence (stable-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: jitter - fix intermediary handling (stable-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: octeontx2 - add timeout for load_fvc completion poll (stable-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- crypto: qat - lower priority for skcipher and aead algorithms (stable-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session() (git-fixes).\n- drm/amd/display: Add primary plane to commits for correct VRR handling (stable-fixes).\n- drm/amd/display: Adjust DCE 8-10 clock, do not overclock by 15% (git-fixes).\n- drm/amd/display: Avoid a NULL pointer dereference (stable-fixes).\n- drm/amd/display: Avoid configuring PSR granularity if PSR-SU not supported (stable-fixes).\n- drm/amd/display: Avoid trying AUX transactions on disconnected ports (stable-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not overclock DCE 6 by 15% (git-fixes).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Fill display clock and vblank time in dce110_fill_display_configs (stable-fixes).\n- drm/amd/display: Find first CRTC and its line time in dce110_fill_display_configs (stable-fixes).\n- drm/amd/display: Fix 'failed to blank crtc!' (stable-fixes).\n- drm/amd/display: Fix DP audio DTO1 clock source on DCE 6 (stable-fixes).\n- drm/amd/display: Fix fractional fb divider in set_pixel_clock_v3 (git-fixes).\n- drm/amd/display: Only finalize atomic_obj if it was initialized (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: Separate set_gsl from set_gsl_source_select (stable-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amd: Allow printing VanGogh OD SCLK levels without setting dpm to manual (stable-fixes).\n- drm/amd: Restore cached power limit during resume (stable-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Avoid extra evict-restore process (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: fix incorrect vm flags to map bo (git-fixes).\n- drm/amdgpu: fix task hang from failed job submission during process kill (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdgpu: update mmhub 3.0.1 client id mappings (stable-fixes).\n- drm/amdkfd: Destroy KFD debugfs after destroy KFD wq (stable-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS (stable-fixes).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/hisilicon/hibmc: fix the hibmc loaded failed bug (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: Fix device/node reference count leaks in mtk_drm_get_all_drm_priv (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/msm/kms: move snapshot init earlier in KMS init (git-fixes).\n- drm/msm: Defer fd_install in SUBMIT ioctl (git-fixes).\n- drm/msm: use trylock for debugfs (stable-fixes).\n- drm/nouveau/disp: Always accept linear modifier (git-fixes).\n- drm/nouveau/nvif: Fix potential memory leak in nvif_vmm_ctor() (git-fixes).\n- drm/nouveau: fix error path in nvkm_gsp_fwsec_v2 (git-fixes).\n- drm/nouveau: fix typos in comments (git-fixes).\n- drm/nouveau: remove unused increment in gm200_flcn_pio_imem_wr (git-fixes).\n- drm/nouveau: remove unused memory target test (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm/ttm: Respect the shrinker core free target (stable-fixes).\n- drm/ttm: Should to return the evict error (stable-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- et131x: Add missing check after DMA map (stable-fixes).\n- exfat: add cluster chain loop check for dir (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (stable-fixes).\n- fbdev: fix potential buffer overflow in do_register_framebuffer() (stable-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/mnt_idmapping.c: Return -EINVAL when no map is written (bsc#1233120)\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- fs/orangefs: use snprintf() instead of sprintf() (git-fixes).\n- gpio: mlxbf3: use platform_get_irq_optional() (git-fixes).\n- gpio: tps65912: check the return value of regmap_update_bits() (stable-fixes).\n- gpio: wcd934x: check the return value of regmap_update_bits() (stable-fixes).\n- hfs: fix not erasing deleted b-tree node issue (git-fixes).\n- hfs: fix slab-out-of-bounds in hfs_bnode_read() (git-fixes).\n- hfsplus: do not use BUG_ON() in hfsplus_create_attributes_file() (git-fixes).\n- hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() (git-fixes).\n- hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (emc2305) Set initial PWM minimum value during probe based on thermal state (stable-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: Force DLL0945 touchpad i2c freq to 100khz (stable-fixes).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: do not fail if GETHDRCAP is unsupported (stable-fixes).\n- i3c: master: Initialize ret in i3c_i2c_notifier_call() (stable-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- ice, irdma: fix an off by one in error handling code (bsc#1247712).\n- ice, irdma: move interrupts code to irdma (bsc#1247712).\n- ice: Fix signedness bug in ice_init_interrupt_scheme() (bsc#1247712).\n- ice: count combined queues using Rx/Tx count (bsc#1247712).\n- ice: devlink PF MSI-X max and min parameter (bsc#1247712).\n- ice: enable_rdma devlink param (bsc#1247712).\n- ice: get rid of num_lan_msix field (bsc#1247712).\n- ice: init flow director before RDMA (bsc#1247712).\n- ice: remove splitting MSI-X between features (bsc#1247712).\n- ice: simplify VF MSI-X managing (bsc#1247712).\n- ice: treat dyn_allowed only as suggestion (bsc#1247712).\n- iio: adc: ad7768-1: Ensure SYNC_IN pulse minimum timing requirement (stable-fixes).\n- iio: adc: ad_sigma_delta: do not overallocate scan buffer (stable-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: imu: inv_icm42600: switch timestamp type from int64_t __aligned(8) to aligned_s64 (stable-fixes).\n- iio: imu: inv_icm42600: use = { } instead of memset() (stable-fixes).\n- iio: pressure: bmp280: Use IS_ERR() in bmp280_common_probe() (git-fixes).\n- iio: proximity: isl29501: fix buffered read on big-endian systems (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- integrity/platform_certs: Allow loading of keys in the static key management mode (jsc#PED-13345 jsc#PED-13343).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- iosys-map: Fix undefined behavior in iosys_map_clear() (git-fixes).\n- ipmi: Fix strcpy source and destination the same (stable-fixes).\n- ipmi: Use dev_warn_ratelimited() for incorrect message warnings (stable-fixes).\n- irdma: free iwdev-\u003erf after removing MSI-X (bsc#1247712).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- jfs: Regular file corruption check (git-fixes).\n- jfs: truncate good inode pages when hard link is 0 (git-fixes).\n- jfs: upper bound check of tree index in dbAllocAG (git-fixes).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for 'netfilter: nf_tables: Audit log rule reset' (git-fixes).\n- kABI workaround for 'drm/dp: Add an EDID quirk for the DPCD register access probe' (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: PCI/ACPI: Fix runtime PM ref imbalance on Hot-Plug Capable ports (git-fixes).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kselftest/arm64: Fix check for setting new VLs in sve-ptrace (git-fixes).\n- leds: leds-lp50xx: Handle reg to get correct multi_index (stable-fixes).\n- loop: use kiocb helpers to fix lockdep warning (git-fixes).\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- mISDN: hfcpci: Fix warning when deleting uninitialized timer (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- md/md-cluster: handle REMOVE message earlier (bsc#1247057).\n- md/raid1,raid10: strip REQ_NOWAIT from member bios (git-fixes).\n- md: allow removing faulty rdev during resync (git-fixes).\n- md: make rdev_addable usable for rcu mode (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: dvb-frontends: dib7090p: fix null-ptr-deref in dib7090p_rw_on_apb() (stable-fixes).\n- media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar (stable-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: tc358743: Check I2C succeeded during probe (stable-fixes).\n- media: tc358743: Increase FIFO trigger level to 374 (stable-fixes).\n- media: tc358743: Return an appropriate colorspace from tc358743_set_fmt (stable-fixes).\n- media: usb: hdpvr: disable zero-length read messages (stable-fixes).\n- media: uvcvideo: Fix bandwidth issue for Alcor camera (stable-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-common: Reduce warnings about missing V4L2_CID_LINK_FREQ control (stable-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- mei: bus: Check for still connected devices in mei_cl_bus_dev_release() (stable-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- memstick: Fix deadlock by moving removing flag earlier (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() (git-fixes)\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: rtsx_usb_sdmmc: Fix error-path in sd_set_power_mode() (stable-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mmc: sdhci-msm: Ensure SD card power isn't ON when card removed (stable-fixes).\n- mmc: sdhci-pci-gli: GL9763e: Rename the gli_set_gl9763e() for consistency (git-fixes).\n- most: core: Drop device reference after usage in get_channel() (git-fixes).\n- mptcp: fallback when MPTCP opts are dropped after 1st data (git-fixes).\n- mptcp: reset when MPTCP opts are dropped after join (git-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: phy: micrel: Add ksz9131_resume() (stable-fixes).\n- net: phy: smsc: add proper reset flags for LAN8710A (stable-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: thunderbolt: Enable end-to-end flow control also in transmit (stable-fixes).\n- net: thunderbolt: Fix the parameter passing of tb_xdomain_enable_paths()/tb_xdomain_disable_paths() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization (git-fixes).\n- net: usb: asix_devices: add phy_mask for ax88772 mdio bus (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pNFS: Fix disk addr range check in block/scsi layout (git-fixes).\n- pNFS: Fix stripe mapping in block/scsi layout (git-fixes).\n- pNFS: Fix uninited ptr deref in block/scsi layout (git-fixes).\n- pNFS: Handle RPC size limit for layoutcommits (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: mscc: Fix parsing of unicast frames (git-fixes).\n- phy: rockchip-pcie: Properly disable TEST_WRITE strobe signal (stable-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: STMFX: add missing HAS_IOMEM dependency (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- pinctrl: stm32: Manage irq affinity settings (stable-fixes).\n- platform/chrome: cros_ec_typec: Defer probe on missing EC parent (stable-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86/amd: pmc: Add Lenovo Yoga 6 13ALC6 to pmc quirk list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- pm: cpupower: Fix the snapshot-order of tsc,mperf, clock in mperf_stop() (stable-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- power: supply: qcom_battmgr: Add lithium-polymer entry (stable-fixes).\n- powerpc/eeh: Export eeh_unfreeze_pe() (bsc#1215199).\n- powerpc/eeh: Make EEH driver device hotplug safe (bsc#1215199).\n- powerpc/eeh: Rely on dev-\u003elink_active_reporting (bsc#1215199).\n- powerpc/kernel: Fix ppc_save_regs inclusion in build (bsc#1215199).\n- powerpc/pseries: Correct secvar format representation for static key management (jsc#PED-13345 jsc#PED-13343).\n- powerpc/secvar: Expose secvars relevant to the key management mode (jsc#PED-13345 jsc#PED-13343).\n- powerpc: do not build ppc_save_regs.o always (bsc#1215199).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: mediatek: Fix duty and period setting (git-fixes).\n- pwm: mediatek: Handle hardware enable and clock enable separately (stable-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- reset: brcmstb: Enable reset drivers for ARCH_BCM2835 (stable-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186)\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186)\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- rtc: ds1307: handle oscillator stop flag (OSF) for ds1341 (stable-fixes).\n- rtc: ds1307: remove clear of oscillator stop flag (OSF) in probe (stable-fixes).\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- samples/bpf: Fix compilation errors with cf-protection option (git-fixes).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- scsi: Revert 'scsi: iscsi: Fix HW conn removal use after free' (git-fixes).\n- scsi: core: Fix kernel doc for scsi_track_queue_full() (git-fixes).\n- scsi: elx: efct: Fix dma_unmap_sg() nents value (git-fixes).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: ibmvscsi_tgt: Fix dma_unmap_sg() nents value (git-fixes).\n- scsi: isci: Fix dma_unmap_sg() nents value (git-fixes).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: mpi3mr: Fix kernel-doc issues in mpi3mr_app.c (git-fixes).\n- scsi: mpi3mr: Fix race between config read submit and interrupt completion (git-fixes).\n- scsi: mpi3mr: Serialize admin queue BAR writes on 32-bit systems (git-fixes).\n- scsi: mpt3sas: Fix a fw_event memory leak (git-fixes).\n- scsi: mvsas: Fix dma_unmap_sg() nents value (git-fixes).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- scsi: sd: Make sd shutdown issue START STOP UNIT appropriately (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/bpf: fexit_sleep: Fix stack allocation for arm64 (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests/tracing: Fix false failure of subsystem event test (git-fixes).\n- selftests: Fix errno checking in syscall_user_dispatch test (git-fixes).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- selftests: rtnetlink.sh: remove esp4_offload after test (git-fixes).\n- serial: 8250: fix panic due to PSLVERR (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- slab: Decouple slab_debug and no_hash_pointers (bsc#1249022).\n- soc/tegra: pmc: Ensure power-domains are in a known state (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- soundwire: amd: serialize amd manager resume sequence during pm_prepare (stable-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- squashfs: fix memory leak in squashfs_fill_super (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- sunvdc: Balance device refcount in vdc_port_mpgroup_check (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom-spmi-temp-alarm: Enable stage 2 shutdown when required (stable-fixes).\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thermal: sysfs: Return ENODATA instead of EAGAIN for reads (stable-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- ublk: sanity check add_dev input for underflow (git-fixes).\n- ublk: use vmalloc for ublk_device's __queues (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: core: config: Prevent OOB read in SS endpoint companion parsing (stable-fixes).\n- usb: core: hcd: fix accessing unmapped memory in SINGLE_STEP_SET_FEATURE test (git-fixes).\n- usb: core: usb_submit_urb: downgrade type check (stable-fixes).\n- usb: dwc3: Ignore late xferNotReady event to prevent halt timeout (git-fixes).\n- usb: dwc3: Remove WARN_ON for device endpoint command timeouts (stable-fixes).\n- usb: dwc3: core: Fix system suspend on TI AM62 platforms (git-fixes).\n- usb: dwc3: fix fault at system suspend if device was already runtime suspended (git-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: pci: add support for the Intel Wildcat Lake (stable-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: quirks: Add DELAY_INIT quick for another SanDisk 3.2Gen1 Flash Drive (stable-fixes).\n- usb: renesas-xhci: Fix External ROM access timeouts (git-fixes).\n- usb: storage: realtek_cr: Use correct byte order for bcs-\u003eResidue (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: intel_pmc_mux: Defer probe if SCU IPC isn't present (stable-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: typec: ucsi: psy: Set current max to 100mA for BC 1.2 and Default (stable-fixes).\n- usb: xhci: Avoid showing errors during surprise removal (stable-fixes).\n- usb: xhci: Avoid showing warnings for dying controller (stable-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- usb: xhci: Fix slot_id resource race conflict (git-fixes).\n- usb: xhci: Set avg_trb_len = 8 for EP0 during Address Device Command (stable-fixes).\n- usb: xhci: print xhci-\u003exhc_state when queue_command failed (stable-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: dw_wdt: Fix default timeout (stable-fixes).\n- watchdog: iTCO_wdt: Report error if timeout configuration fails (stable-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- watchdog: sbsa: Adjust keepalive timeout to avoid MediaTek WS0 race condition (stable-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: ath12k: Add memset and update default rate value in wmi tx completion (stable-fixes).\n- wifi: ath12k: Correct tid cleanup when tid setup fails (stable-fixes).\n- wifi: ath12k: Decrement TID on RX peer frag setup error handling (stable-fixes).\n- wifi: ath12k: Enable REO queue lookup table feature on QCN9274 hw2.0 (stable-fixes).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: Fix interface type validation (stable-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: reject HTC bit for management frames (stable-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlegacy: Check rate_idx range after addition (stable-fixes).\n- wifi: iwlwifi: dvm: fix potential overflow in rs_fill_link_cmd() (stable-fixes).\n- wifi: iwlwifi: fw: Fix possible memory leak in iwl_fw_dbg_collect (stable-fixes).\n- wifi: iwlwifi: mvm: fix scan request validation (stable-fixes).\n- wifi: iwlwifi: mvm: set gtk id also in older FWs (stable-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: do not complete management TX on SAE commit (stable-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: fix rx link assignment for non-MLO stations (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mac80211: update radar_required in channel context after channel switch (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7915: mcu: re-init MCU before loading FW patch (stable-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtlwifi: fix possible skb memory leak in _rtl_pci_init_one_rxdesc() (stable-fixes).\n- wifi: rtlwifi: fix possible skb memory leak in `_rtl_pci_rx_interrupt()` (stable-fixes).\n- wifi: rtw89: Disable deep power saving for USB/SDIO (stable-fixes).\n- wifi: rtw89: Fix rtw89_mac_power_switch() for USB (stable-fixes).\n- wifi: rtw89: Lower the timeout in rtw89_fw_read_c2h_reg() for USB (stable-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-17T14:32:52Z","modified":"2026-03-23T04:50:37.829997Z","updated_at":"2026-11-02T15:53:58.883365Z"},{"id":"SUSE-SU-2025:20851-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- !CONFIG \u0026 reference -\u003e this is bug, immediate fail\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Correct typos of References tags in some patches\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- Drop PCI patches that broke kdump capture boot (bsc#1246509)\n- Drop arm64 patches that may lead to module load failure (bsc#1250057)\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- Fix BPF selftests compilation error in bpf_iter.c (git-fixes)\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for \"spurious\" preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb \"force_immediate_exit\" into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186)\n- Limit patch filenames to 100 characters (bsc#1249604).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free \"ks-pcie-error-irq\" on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert \"SUNRPC: Do not allow waiting for exiting tasks\" (git-fixes).\n- Revert \"drm/amdgpu: fix incorrect vm flags to map bo\" (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- Update config files. (bsc#1249186) Plain run_oldconfig after Kconfig update.\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- config.sh: Use Step repository for building Leap kernel bs-upload-kernel does not understand the Leap repository layout\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for \"netfilter: nf_tables: Audit log rule reset\" (git-fixes).\n- kABI workaround for \"drm/dp: Add an EDID quirk for the DPCD register access probe\" (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: drop kvm_x86_ops from kabi relevant symbols.\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source.spec: Depend on python3-base for build Both kernel-binary and kernel-docs already have this dependency.\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186)\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186)\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-15T16:17:22Z","modified":"2026-03-23T04:51:03.213873Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20861-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- !CONFIG \u0026 reference -\u003e this is bug, immediate fail\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Correct typos of References tags in some patches\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- Drop PCI patches that broke kdump capture boot (bsc#1246509)\n- Drop arm64 patches that may lead to module load failure (bsc#1250057)\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- Fix BPF selftests compilation error in bpf_iter.c (git-fixes)\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for \"spurious\" preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb \"force_immediate_exit\" into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186)\n- Limit patch filenames to 100 characters (bsc#1249604).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free \"ks-pcie-error-irq\" on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert \"SUNRPC: Do not allow waiting for exiting tasks\" (git-fixes).\n- Revert \"drm/amdgpu: fix incorrect vm flags to map bo\" (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- Update config files. (bsc#1249186) Plain run_oldconfig after Kconfig update.\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- config.sh: Use Step repository for building Leap kernel bs-upload-kernel does not understand the Leap repository layout\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for \"netfilter: nf_tables: Audit log rule reset\" (git-fixes).\n- kABI workaround for \"drm/dp: Add an EDID quirk for the DPCD register access probe\" (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: drop kvm_x86_ops from kabi relevant symbols.\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source.spec: Depend on python3-base for build Both kernel-binary and kernel-docs already have this dependency.\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186)\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186)\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-15T15:17:40Z","modified":"2026-03-23T04:50:18.219314Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20870-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- !CONFIG \u0026 reference -\u003e this is bug, immediate fail\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- Fix BPF selftests compilation error in bpf_iter.c (git-fixes).\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for \"spurious\" preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb \"force_immediate_exit\" into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free \"ks-pcie-error-irq\" on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert \"SUNRPC: Do not allow waiting for exiting tasks\" (git-fixes).\n- Revert \"drm/amdgpu: fix incorrect vm flags to map bo\" (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- Update config files. (bsc#1249186) Plain run_oldconfig after Kconfig update.\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- config.sh: Use Step repository for building Leap kernel bs-upload-kernel does not understand the Leap repository layout\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for \"netfilter: nf_tables: Audit log rule reset\" (git-fixes).\n- kABI workaround for \"drm/dp: Add an EDID quirk for the DPCD register access probe\" (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: drop kvm_x86_ops from kabi relevant symbols.\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source.spec: Depend on python3-base for build Both kernel-binary and kernel-docs already have this dependency.\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- sched: add a sched_ttwu_queue sysctl (bsc#1247963, jsc#PED-13659).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-23T16:01:09Z","modified":"2026-03-23T04:49:08.555395Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:20898-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- !CONFIG \u0026 reference -\u003e this is bug, immediate fail\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- CONFIG \u0026 no reference -\u003e OK temporarily, must be resolved eventually\n- Do not self obsolete older kernel variants\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- Fix BPF selftests compilation error in bpf_iter.c (git-fixes).\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for \"spurious\" preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb \"force_immediate_exit\" into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free \"ks-pcie-error-irq\" on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert \"SUNRPC: Do not allow waiting for exiting tasks\" (git-fixes).\n- Revert \"drm/amdgpu: fix incorrect vm flags to map bo\" (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- Update config files. (bsc#1249186) Plain run_oldconfig after Kconfig update.\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- config.sh: Use Step repository for building Leap kernel bs-upload-kernel does not understand the Leap repository layout\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for \"netfilter: nf_tables: Audit log rule reset\" (git-fixes).\n- kABI workaround for \"drm/dp: Add an EDID quirk for the DPCD register access probe\" (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: drop kvm_x86_ops from kabi relevant symbols.\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source.spec: Depend on python3-base for build Both kernel-binary and kernel-docs already have this dependency.\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- sched: add a sched_ttwu_queue sysctl (bsc#1247963, jsc#PED-13659).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-23T13:59:20Z","modified":"2026-03-23T04:47:09.901155Z","updated_at":"2026-11-02T15:53:59.92114Z"},{"id":"SUSE-SU-2025:3716-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49980: USB: gadget: fix use-after-free read in usb_udc_uevent() (bsc#1245110).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).\n- CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).\n- CVE-2025-38084: mm/hugetlb: unshare page tables during VMA split, not before (bsc#1245498).\n- CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).\n- CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).\n- CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).\n- CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).\n- CVE-2025-38470: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime (bsc#1247288).\n- CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).\n- CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).\n- CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).\n\nThe following non-security bugs were fixed:\n\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- Revert backported patches for bsc#1238160.\n- btrfs: avoid NULL pointer dereference if no valid extent tree (bsc#1249158).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522). \n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- net/sched: ets: use old 'nbands' while purging unused classes (git-fixes).\n- netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337)\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- use uniform permission checks for all mount propagation changes (git-fixes).\n","status":"published","published":"2025-10-22T07:11:59Z","modified":"2026-02-04T02:18:54.554396Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:3751-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP6 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-53261: coresight: Fix memory leak in acpi_buffer-\u003epointer (bsc#1249770).\n- CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).\n- CVE-2025-22022: usb: xhci: Apply the link chain quirk on NEC isoc endpoints (bsc#1241292).\n- CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).\n- CVE-2025-38234: sched/rt: Fix race in push_rt_task (bsc#1246057).\n- CVE-2025-38263: bcache: fix NULL pointer in cache_set_flush() (bsc#1246248).\n- CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush (bsc#1246782).\n- CVE-2025-38402: idpf: return 0 size for RSS key if not supported (bsc#1247262).\n- CVE-2025-38408: genirq/irq_sim: Initialize work context pointers properly (bsc#1247126).\n- CVE-2025-38418: remoteproc: core: Release rproc-\u003eclean_table after rproc_attach() fails (bsc#1247137).\n- CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() (bsc#1247136).\n- CVE-2025-38456: ipmi:msghandler: Fix potential memory corruption in ipmi_create_user() (bsc#1247099).\n- CVE-2025-38466: perf: Revert to requiring CAP_SYS_ADMIN for uprobes (bsc#1247442).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct (bsc#1248202).\n- CVE-2025-38526: ice: add NULL check in eswitch lag check (bsc#1248192).\n- CVE-2025-38527: smb: client: fix use-after-free in cifs_oplock_break (bsc#1248199).\n- CVE-2025-38533: net: libwx: fix the using of Rx buffer DMA (bsc#1248200).\n- CVE-2025-38544: rxrpc: Fix bug due to prealloc collision (bsc#1248225).\n- CVE-2025-38556: HID: core: Harden s32ton() against conversion to 0 bits (bsc#1248296).\n- CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit() (bsc#1248365).\n- CVE-2025-38584: padata: Fix pd UAF once and for all (bsc1248343).\n- CVE-2025-38590: net/mlx5e: Remove skb secpath if xfrm state is not found (bsc#1248360).\n- CVE-2025-38593: kABI workaround for bluetooth discovery_state change (bsc#1248357).\n- CVE-2025-38595: xen: fix UAF in dmabuf_exp_from_pages() (bsc#1248380).\n- CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port (bsc#1248378).\n- CVE-2025-38605: wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type() (bsc#1248334).\n- CVE-2025-38614: eventpoll: Fix semi-unbounded recursion (bsc#1248392).\n- CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1248512).\n- CVE-2025-38622: net: drop UFO packets in udp_rcv_segment() (bsc#1248619).\n- CVE-2025-38623: PCI: pnv_php: Fix surprise plug detection and recovery (bsc#1248610).\n- CVE-2025-38639: netfilter: xt_nfacct: do not assume acct name is null-terminated (bsc#1248674).\n- CVE-2025-38640: bpf: Disable migration in nf_hook_run_bpf() (bsc#1248622).\n- CVE-2025-38643: wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (bsc#1248681).\n- CVE-2025-38645: net/mlx5: Check device memory pointer before usage (bsc#1248626).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38660: [ceph] parse_longname(): strrchr() expects NUL-terminated string (bsc#1248634).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data (bsc#1248647).\n- CVE-2025-38676: iommu/amd: Avoid stack buffer overflow from kernel cmdline (bsc#1248775).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check (bsc#1249202).\n- CVE-2025-38684: net/sched: ets: use old 'nbands' while purging unused classes (bsc#1249156).\n- CVE-2025-38701: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr (bsc#1249258).\n- CVE-2025-38705: drm/amd/pm: fix null pointer access (bsc#1249334).\n- CVE-2025-38709: loop: Avoid updating block size under exclusive owner (bsc#1249199).\n- CVE-2025-38721: netfilter: ctnetlink: fix refcount leak on table dump (bsc#1249176).\n- CVE-2025-38722: habanalabs: fix UAF in export_dmabuf() (bsc#1249163).\n- CVE-2025-38730: io_uring/net: commit partial buffers on retry (bsc#1249172).\n- CVE-2025-38732: netfilter: nf_reject: do not leak dst refcount for loopback packets (bsc#1249262).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal (bsc#1249300).\n- CVE-2025-39678: platform/x86/amd/hsmp: Ensure sock-\u003emetric_tbl_addr is non-NULL (bsc#1249290).\n- CVE-2025-39681: x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper (bsc#1249303).\n- CVE-2025-39682: tls: fix handling of zero-length records on the rx_list (bsc#1249284).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39705: drm/amd/display: fix a Null pointer dereference vulnerability (bsc#1249295).\n- CVE-2025-39718: vsock/virtio: Validate length in packet header before skb_put() (bsc#1249305).\n- CVE-2025-39738: btrfs: do not allow relocation of partially dropped subvolumes (bsc#1249540).\n- CVE-2025-39744: rcu: Fix rcu_read_unlock() deadloop due to IRQ work (bsc#1249494).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39749: rcu: Protect -\u003edefer_qs_iw_pending from data race (bsc#1249533).\n- CVE-2025-39754: mm/smaps: fix race between smaps_hugetlb_range and migration (bsc#1249524).\n- CVE-2025-39764: netfilter: ctnetlink: remove refcounting in expectation dumpers (bsc#1249513).\n- CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit (bsc#1249510).\n- CVE-2025-39770: net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM (bsc#1249508).\n- CVE-2025-39773: net: bridge: fix soft lockup in br_multicast_query_expired() (bsc#1249504).\n- CVE-2025-39782: jbd2: prevent softlockup in jbd2_log_do_checkpoint() (bsc#1249526).\n- CVE-2025-39787: soc: qcom: mdt_loader: Deal with zero e_shentsize (bsc#1249545).\n- CVE-2025-39797: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI (bsc#1249608).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2) (bsc#1250179).\n- CVE-2025-39832: net/mlx5: Fix lockdep assertion on sync reset unload event (bsc#1249901).\n- CVE-2025-39835: xfs: do not propagate ENODATA disk errors into xattr code (bsc#1250025).\n- CVE-2025-39838: cifs: prevent NULL pointer dereference in UTF16 conversion (bsc#1250365).\n- CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown (bsc#1250267).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39857: net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() (bsc#1250251).\n- CVE-2025-39865: tee: fix NULL pointer dereference in tee_shm_put (bsc#1250294).\n- CVE-2025-39885: ocfs2: fix recursive semaphore deadlock in fiemap call (bsc#1250407).\n- CVE-2025-40300: x86/vmscape: Warn when STIBP is disabled with SMT (bsc#1247483).\n\nThe following non-security bugs were fixed:\n\n- 9p/xen: fix init sequence (git-fixes).\n- ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).\n- ACPI: EC: Add device to acpi_ec_no_wakeup[] qurik list (stable-fixes).\n- ACPI: NFIT: Fix incorrect ndr_desc being reportedin dev_err message (git-fixes).\n- ACPI: TAD: Add missing sysfs_remove_group() for ACPI_TAD_RT (git-fixes).\n- ACPI: debug: fix signedness issues in read/write helpers (git-fixes).\n- ACPI: processor: idle: Fix memory leak when register cpuidle device failed (git-fixes).\n- ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).\n- ACPICA: Fix largest possible resource descriptor index (git-fixes).\n- ALSA: firewire-motu: drop EPOLLOUT from poll return values as write is not supported (stable-fixes).\n- ALSA: hda/hdmi: Add pin fix for another HP EliteDesk 800 G4 model (stable-fixes).\n- ALSA: hda/realtek - Add new HP ZBook laptop with micmute led fixup (stable-fixes).\n- ALSA: hda/realtek: Add ALC295 Dell TAS2781 I2C fixup (git-fixes).\n- ALSA: hda/realtek: Add support for HP Agusta using CS35L41 HDA (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6[AF]R5xxY (stable-fixes).\n- ALSA: hda/realtek: Fix mute led for HP Laptop 15-dw4xx (stable-fixes).\n- ALSA: hda: intel-dsp-config: Prevent SEGFAULT if ACPI_HANDLE() is NULL (git-fixes).\n- ALSA: lx_core: use int type to store negative error codes (git-fixes).\n- ALSA: usb-audio: Add DSD support for Comtrue USB Audio device (stable-fixes).\n- ALSA: usb-audio: Add mixer quirk for Sony DualSense PS5 (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on more devices (stable-fixes).\n- ALSA: usb-audio: Add mute TLV for playback volumes on some devices (stable-fixes).\n- ALSA: usb-audio: Avoid multiple assignments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Convert comma to semicolon (git-fixes).\n- ALSA: usb-audio: Drop unnecessary parentheses in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix block comments in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Fix build with CONFIG_INPUT=n (git-fixes).\n- ALSA: usb-audio: Remove unneeded wmb() in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: Simplify NULL comparison in mixer_quirks (stable-fixes).\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (git-fixes).\n- ALSA: usb-audio: move mixer_quirks' min_mute into common quirk (stable-fixes).\n- ASoC: Intel: bytcht_es8316: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (git-fixes).\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (git-fixes).\n- ASoC: SOF: Intel: hda-stream: Fix incorrect variable used in error message (git-fixes).\n- ASoC: codecs: tx-macro: correct tx_macro_component_drv name (stable-fixes).\n- ASoC: imx-hdmi: remove cpu_pdev related code (git-fixes).\n- ASoC: qcom: audioreach: Fix lpaif_type configuration for the I2S interface (git-fixes).\n- ASoC: qcom: audioreach: fix potential null pointer dereference (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix NULL pointer dereference if source graph failed (git-fixes).\n- ASoC: qcom: q6apm-lpass-dais: Fix missing set_fmt DAI op for I2S (git-fixes).\n- ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data() (git-fixes).\n- ASoC: wm8940: Correct PLL rate rounding (git-fixes).\n- ASoC: wm8940: Correct typo in control name (git-fixes).\n- ASoC: wm8974: Correct PLL rate rounding (git-fixes).\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (git-fixes).\n- Bluetooth: ISO: Fix possible UAF on iso_conn_free (git-fixes).\n- Bluetooth: ISO: do not leak skb in ISO_CONT RX (git-fixes).\n- Bluetooth: MGMT: Fix not exposing debug UUID on MGMT_OP_READ_EXP_FEATURES_INFO (git-fixes).\n- Bluetooth: MGMT: Fix possible UAFs (git-fixes).\n- Bluetooth: compute LE flow credits based on recvbuf space (git-fixes).\n- Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Avoid adding default advertising on startup (stable-fixes).\n- Bluetooth: hci_sync: Fix hci_resume_advertising_sync (git-fixes).\n- Bluetooth: qca: fix invalid device address check (git-fixes).\n- Bluetooth: qca: fix wcn3991 device address check (git-fixes).\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early (git-fixes).\n- Drivers: hv: Always select CONFIG_SYSFB for Hyper-V guests (git-fixes).\n- Drivers: hv: Select CONFIG_SYSFB only if EFI is enabled (git-fixes).\n- arch: arm64: Drop arm64 patches that may lead to module load failure (bsc#1250057).\n- wrt: Regression fix for  wrt s2idle on AMD laptops (bsc#1243112).\n- EDAC/i10nm: Skip DIMM enumeration on a disabled memory controller (git-fixes).\n- HID: hid-ntrig: fix unable to handle page fault in ntrig_report_version() (stable-fixes).\n- HID: input: rename hidinput_set_battery_charge_status() (stable-fixes).\n- HID: input: report battery status changes immediately (git-fixes).\n- HID: intel-ish-ipc: Remove redundant ready check after timeout function (git-fixes).\n- HID: mcp2221: Do not set bus speed on every transfer (stable-fixes).\n- HID: mcp2221: Handle reads greater than 60 bytes (stable-fixes).\n- HID: quirks: add support for Legion Go dual dinput modes (stable-fixes).\n- HID: wacom: Add a new Art Pen 2 (stable-fixes).\n- IB/mlx5: Fix obj_type mismatch for SRQ event subscriptions (git-fixes)\n- IB/sa: Fix sa_local_svc_timeout_ms read race (git-fixes)\n- Input: i8042 - add TUXEDO InfinityBook Pro Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: iqs7222 - avoid enabling unused interrupts (stable-fixes).\n- KVM: SVM: Clear current_vmcb during vCPU free for all *possible* CPUs (git-fixes).\n- KVM: SVM: Disable interception of SPEC_CTRL iff the MSR exists for the guest (git-fixes).\n- KVM: SVM: Sync TPR from LAPIC into VMCB::V_TPR even if AVIC is active (git-fixes).\n- KVM: VMX: Extract checking of guest's DEBUGCTL into helper (git-fixes).\n- KVM: VMX: Flush shadow VMCS on emergency reboot (git-fixes).\n- KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (git-fixes).\n- KVM: VMX: Handle forced exit due to preemption timer in fastpath (git-fixes).\n- KVM: VMX: Re-enter guest in fastpath for 'spurious' preemption timer exits (git-fixes).\n- KVM: arm64: vgic: fix incorrect spinlock API usage (git-fixes).\n- KVM: s390: Fix incorrect usage of mmu_notifier_register() (git-fixes bsc#1250336).\n- KVM: x86/xen: Allow 'out of range' event channel ports in IRQ routing table (git-fixes).\n- KVM: x86: Drop pending_smi vs. INIT_RECEIVED check when setting MP_STATE (git-fixes).\n- KVM: x86: Fully defer to vendor code to decide how to force immediate exit (git-fixes).\n- KVM: x86: Move handling of is_guest_mode() into fastpath exit handlers (git-fixes).\n- KVM: x86: Plumb 'force_immediate_exit' into kvm_entry() tracepoint (git-fixes).\n- KVM: x86: avoid underflow when scaling TSC frequency (git-fixes).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- NFSv4.1: fix backchannel max_resp_sz verification check (git-fixes).\n- NFSv4/flexfiles: Fix layout merge mirror check (git-fixes).\n- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set (git-fixes).\n- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server (git-fixes).\n- NFSv4: Do not clear capabilities that won't be reset (git-fixes).\n- PCI/AER: Fix missing uevent on recovery when a reset is requested (git-fixes).\n- PCI/ERR: Fix uevent on failure to recover (git-fixes).\n- PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (git-fixes).\n- PCI/sysfs: Ensure devices are powered for config reads (git-fixes).\n- PCI: Extend isolated function probing to LoongArch (git-fixes).\n- PCI: keystone: Use devm_request_irq() to free 'ks-pcie-error-irq' on exit (git-fixes).\n- PCI: rcar-host: Drop PMSR spinlock (git-fixes).\n- PCI: tegra194: Fix broken tegra_pcie_ep_raise_msi_irq() (git-fixes).\n- PCI: tegra194: Fix duplicate PLL disable in pex_ep_event_pex_rst_assert() (git-fixes).\n- PCI: tegra194: Handle errors in BPMP response (git-fixes).\n- PCI: tegra: Convert struct tegra_msi mask_lock into raw spinlock (git-fixes).\n- PCI: tegra: Fix devm_kcalloc() argument order for port-\u003ephys allocation (git-fixes).\n- PM / devfreq: mtk-cci: Fix potential error pointer dereference in probe() (git-fixes).\n- PM: sleep: core: Clear power.must_resume in noirq suspend error path (git-fixes).\n- RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes)\n- RDMA/core: Resolve MAC of next-hop device without ARP support (git-fixes)\n- RDMA/mlx5: Better estimate max_qp_wr to reflect WQE count (git-fixes)\n- RDMA/mlx5: Fix vport loopback forcing for MPV device (git-fixes)\n- RDMA/rxe: Fix race in do_task() when draining (git-fixes)\n- RDMA/siw: Always report immediate post SQ errors (git-fixes)\n- Revert 'SUNRPC: Do not allow waiting for exiting tasks' (git-fixes).\n- Revert 'drm/amdgpu: fix incorrect vm flags to map bo' (stable-fixes).\n- SUNRPC: call xs_sock_process_cmsg for all cmsg (git-fixes).\n- Squashfs: add additional inode sanity checking (git-fixes).\n- Squashfs: fix uninit-value in squashfs_get_parent (git-fixes).\n- Squashfs: reject negative file sizes in squashfs_read_inode() (git-fixes).\n- USB: gadget: dummy-hcd: Fix locking bug in RT-enabled kernels (git-fixes).\n- USB: serial: option: add Telit Cinterion FN990A w/audio compositions (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910C4-WWX new compositions (stable-fixes).\n- Update config files. (bsc#1249186) Plain run_oldconfig after Kconfig update.\n- afs: Fix potential null pointer dereference in afs_put_server (git-fixes).\n- arm64: Handle KCOV __init vs inline mismatches (git-fixes)\n- arm64: Mark kernel as tainted on SAE and SError panic (git-fixes)\n- arm64: dts: apple: Add ethernet0 alias for J375 template (git-fixes)\n- arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map (git-fixes)\n- arm64: dts: imx8mp-tqma8mpql: fix LDO5 power off (git-fixes)\n- arm64: dts: imx8mp: Correct thermal sensor index (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on DH electronics (git-fixes)\n- arm64: dts: imx8mp: Fix missing microSD slot vqmmc on Data Modul (git-fixes)\n- arm64: dts: rockchip: Add vcc-supply to SPI flash on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on (git-fixes)\n- arm64: dts: rockchip: disable unrouted USB controllers and PHY on RK3399 Puma with Haikou (git-fixes).\n- arm64: dts: rockchip: fix internal USB hub instability on RK3399 Puma (git-fixes)\n- arm64: dts: rockchip: use cs-gpios for spi1 on ringneck (git-fixes)\n- arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module (git-fixes)\n- ax25: properly unshare skbs in ax25_kiss_rcv() (git-fixes).\n- batman-adv: fix OOB read/write in network-coding decode (git-fixes).\n- bpf, bpftool: Fix incorrect disasm pc (git-fixes).\n- bpf: Adjust free target to avoid global starvation of LRU map (git-fixes).\n- bpf: Fix iter/task tid filtering (git-fixes).\n- bpf: Fix link info netfilter flags to populate defrag flag (git-fixes).\n- bpf: Make reg_not_null() true for CONST_PTR_TO_MAP (git-fixes).\n- bpf: Properly test iter/task tid filtering (git-fixes).\n- bpf: bpftool: Setting error code in do_loader() (git-fixes).\n- bpf: handle implicit declaration of function gettid in bpf_iter.c\n- bpf: skip non exist keys in generic_map_lookup_batch (git-fixes).\n- bpftool: Fix JSON writer resource leak in version command (git-fixes).\n- bpftool: Fix memory leak in dump_xx_nlmsg on realloc failure (git-fixes).\n- bpftool: Fix readlink usage in get_fd_type (git-fixes).\n- bpftool: Mount bpffs when pinmaps path not under the bpffs (git-fixes).\n- bpftool: fix potential NULL pointer dereferencing in prog_dump() (git-fixes).\n- btrfs: abort transaction during log replay if walk_log_tree() failed (git-fixes).\n- btrfs: abort transaction on unexpected eb generation at btrfs_copy_root() (git-fixes).\n- btrfs: add cancellation points to trim loops (git-fixes).\n- btrfs: always abort transaction on failure to add block group to free space tree (git-fixes).\n- btrfs: always update fstrim_range on failure in FITRIM ioctl (git-fixes).\n- btrfs: avoid load/store tearing races when checking if an inode was logged (git-fixes).\n- btrfs: fix data overwriting bug during buffered write when block size \u0026lt; page size (git-fixes).\n- btrfs: fix invalid extref key setup when replaying dentry (git-fixes).\n- btrfs: fix race between logging inode and checking if it was logged before (git-fixes).\n- btrfs: fix race between setting last_dir_index_offset and inode logging (git-fixes).\n- btrfs: make found_logical_ret parameter mandatory for function queue_scrub_stripe() (git-fixes).\n- btrfs: move transaction aborts to the error site in add_block_group_free_space() (git-fixes).\n- btrfs: qgroup: fix race between quota disable and quota rescan ioctl (git-fixes).\n- btrfs: scrub: avoid unnecessary csum tree search preparing stripes (git-fixes).\n- btrfs: scrub: avoid unnecessary extent tree search preparing stripes (git-fixes).\n- btrfs: scrub: fix grouping of read IO (git-fixes).\n- btrfs: scrub: remove scrub_ctx::csum_list member (git-fixes).\n- btrfs: split remaining space to discard in chunks (git-fixes).\n- btrfs: tree-checker: fix the incorrect inode ref size check (git-fixes).\n- btrfs: use SECTOR_SHIFT to convert physical offset to LBA (git-fixes).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- bus: fsl-mc: Check return value of platform_get_resource() (git-fixes).\n- bus: mhi: host: Do not use uninitialized 'dev' pointer in mhi_init_irq_setup() (git-fixes).\n- can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: hi311x: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: j1939: implement NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: j1939_local_ecu_get(): undo increment when j1939_local_ecu_get() fails (git-fixes).\n- can: j1939: j1939_sk_bind(): call j1939_priv_put() immediately when j1939_local_ecu_get() failed (git-fixes).\n- can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: peak_usb: fix shift-out-of-bounds issue (git-fixes).\n- can: rcar_can: rcar_can_resume(): fix s2ram with PSCI (stable-fixes).\n- can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow (git-fixes).\n- can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB (git-fixes).\n- cdc_ncm: Flag Intel OEM version of Fibocom L850-GL as WWAN (stable-fixes).\n- ceph: fix possible integer overflow in ceph_zero_objects() (git-fixes).\n- ceph: validate snapdirname option length when mounting (git-fixes).\n- cgroup/cpuset: Use static_branch_enable_cpuslocked() on cpusets_insane_config_key (bsc#1241166).\n- cgroup/rstat: Optimize cgroup_rstat_updated_list() (bsc#1247963).\n- cgroup/rstat: Reduce cpu_lock hold time in cgroup_rstat_flush_locked() (bsc#1247963).\n- cgroup: llist: avoid memory tears for llist_node (bsc#1247963).\n- cgroup: make css_rstat_updated nmi safe (bsc#1247963).\n- cgroup: remove cgroup_rstat_flush_atomic() (bsc#1247963).\n- cgroup: remove per-cpu per-subsystem locks (bsc#1247963).\n- cgroup: support to enable nmi-safe css_rstat_updated (bsc#1247963).\n- compiler-clang.h: define __SANITIZE_*__ macros only when undefined (stable-fixes).\n- compiler: remove __ADDRESSABLE_ASM{_STR,}() again (git-fixes).\n- cpufreq: CPPC: Mark driver with NEED_UPDATE_LIMITS flag (stable-fixes).\n- cpufreq: Exit governor when failed to start old governor (stable-fixes).\n- cpufreq: Init policy-\u003erwsem before it may be possibly used (git-fixes).\n- cpufreq: Initialize cpufreq-based frequency-invariance later (git-fixes).\n- cpufreq: Initialize cpufreq-based invariance before subsys (git-fixes).\n- cpufreq: Use the fixed and coherent frequency for scaling capacity (stable-fixes).\n- cpufreq: cppc: Fix invalid return value in .get() callback (git-fixes).\n- cpufreq: governor: Fix negative 'idle_time' handling in dbs_update() (git-fixes).\n- cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode (git-fixes).\n- cpufreq: intel_pstate: Unchecked MSR aceess in legacy mode (git-fixes).\n- cpufreq: scpi: compare kHz instead of Hz (git-fixes).\n- cpufreq: tegra186: Share policy per cluster (stable-fixes).\n- cpupower: Fix a bug where the -t option of the set subcommand was not working (stable-fixes).\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg (git-fixes).\n- crypto: aspeed - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: atmel - Fix dma_unmap_sg() direction (git-fixes).\n- crypto: hisilicon/qm - check whether the input function and PF are on the same device (git-fixes).\n- crypto: hisilicon/qm - set NULL to qm-\u003edebug.qm_diff_regs (git-fixes).\n- crypto: keembay - Add missing check after sg_nents_for_len() (git-fixes).\n- crypto: qat - add shutdown handler to qat_c3xxx (git-fixes).\n- crypto: qat - add shutdown handler to qat_c62x (git-fixes).\n- crypto: qat - add shutdown handler to qat_dh895xcc (git-fixes).\n- dma/pool: Ensure DMA_DIRECT_REMAP allocations are decrypted (stable-fixes).\n- dmaengine: Fix dma_async_tx_descriptor-\u003etx_submit documentation (git-fixes).\n- dmaengine: dw: dmamux: Fix device reference leak in rzn1_dmamux_route_allocate (git-fixes).\n- dmaengine: idxd: Fix double free in idxd_setup_wqs() (git-fixes).\n- dmaengine: idxd: Fix refcount underflow on module unload (git-fixes).\n- dmaengine: idxd: Remove improper idxd_free (git-fixes).\n- dmaengine: mediatek: Fix a flag reuse error in mtk_cqdma_tx_status() (git-fixes).\n- dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (git-fixes).\n- dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (git-fixes).\n- docs: admin-guide: update to current minimum pipe size default (git-fixes).\n- drivers/base/node: fix double free in register_one_node() (git-fixes).\n- drivers/base/node: handle error properly in register_one_node() (git-fixes).\n- drivers/base/node: optimize memory block registration to reduce boot time (bsc#1241866).\n- drivers/base/node: remove register_mem_block_under_node_early() (bsc#1241866).\n- drivers/base/node: remove register_memory_blocks_under_node() function call from register_one_node (bsc#1241866).\n- drivers/base/node: rename __register_one_node() to register_one_node() (bsc#1241866).\n- drivers/base/node: rename register_memory_blocks_under_node() and remove context argument (bsc#1241866).\n- drm/amd/amdgpu: Fix missing error return on kzalloc failure (git-fixes).\n- drm/amd/display: Disable DPCD Probe Quirk (bsc#1248121).\n- drm/amd/display: Do not warn when missing DCE encoder caps (stable-fixes).\n- drm/amd/display: Remove redundant semicolons (git-fixes).\n- drm/amd/display: use udelay rather than fsleep (git-fixes).\n- drm/amd/pm: Adjust si_upload_smc_data register programming (v3) (git-fixes).\n- drm/amd/pm: Disable MCLK switching with non-DC at 120 Hz+ (v2) (git-fixes).\n- drm/amd/pm: Disable SCLK switching on Oland with high pixel clocks (v3) (git-fixes).\n- drm/amd/pm: Disable ULV even if unsupported (v3) (git-fixes).\n- drm/amd/pm: Fix si_upload_smc_data (v3) (git-fixes).\n- drm/amd/pm: Treat zero vblank time as too short in si_dpm (v3) (git-fixes).\n- drm/amdgpu/vcn4: Fix IB parsing with multiple engine info packages (stable-fixes).\n- drm/amdgpu/vcn: Allow limiting ctx to instance 0 for AV1 at any time (stable-fixes).\n- drm/amdgpu: Power up UVD 3 for FW validation (v2) (git-fixes).\n- drm/amdgpu: drop hw access in non-DC audio fini (stable-fixes).\n- drm/amdgpu: fix a memory leak in fence cleanup when unloading (git-fixes).\n- drm/amdgpu: remove the redeclaration of variable i (git-fixes).\n- drm/amdkfd: Fix error code sign for EINVAL in svm_ioctl() (git-fixes).\n- drm/ast: Use msleep instead of mdelay for edid read (bsc#1250530).\n- drm/bridge: it6505: select REGMAP_I2C (git-fixes).\n- drm/bridge: ti-sn65dsi86: fix REFCLK setting (git-fixes).\n- drm/dp: Add an EDID quirk for the DPCD register access probe (bsc#1248121).\n- drm/dp: Change AUX DPCD probe address from LANE0_1_STATUS to TRAINING_PATTERN_SET (bsc#1248121).\n- drm/edid: Add support for quirks visible to DRM core and drivers (bsc#1248121).\n- drm/edid: Define the quirks in an enum list (bsc#1248121).\n- drm/gma500: Fix null dereference in hdmi teardown (git-fixes).\n- drm/i915/backlight: Return immediately when scale() finds invalid parameters (stable-fixes).\n- drm/i915/power: fix size for for_each_set_bit() in abox iteration (git-fixes).\n- drm/mediatek: fix potential OF node use-after-free (git-fixes).\n- drm/msm/dpu: fix incorrect type for ret (git-fixes).\n- drm/panel: novatek-nt35560: Fix invalid return value (git-fixes).\n- drm/radeon/r600_cs: clean up of dead code in r600_cs (git-fixes).\n- drm/rcar-du: dsi: Fix 1/2/3 lane support (git-fixes).\n- drm: bridge: anx7625: Fix NULL pointer dereference with early IRQ (git-fixes).\n- drm: bridge: cdns-mhdp8546: Fix missing mutex unlock on error path (git-fixes).\n- erofs: fix atomic context detection when !CONFIG_DEBUG_LOCK_ALLOC (git-fixes).\n- ext4: remove writable userspace mappings before truncating page cache (bsc#1247223).\n- fbcon: Fix OOB access in font allocation (git-fixes).\n- fbcon: fix integer overflow in fbcon_do_set_font (git-fixes).\n- firewire: core: fix overlooked update of subsystem ABI version (git-fixes).\n- firmware: meson_sm: fix device leak at probe (git-fixes).\n- flexfiles/pNFS: fix NULL checks on result of ff_layout_choose_ds_for_read (git-fixes).\n- fs/nfs/io: make nfs_start_io_*() killable (git-fixes).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- hv_netvsc: Set VF priv_flags to IFF_NO_ADDRCONF before open to prevent IPv6 addrconf (git-fixes).\n- hwmon: (mlxreg-fan) Separate methods of fan setting coming from different subsystems (git-fixes).\n- hwmon: mlxreg-fan: Prevent fans from getting stuck at 0 RPM (git-fixes).\n- hwrng: ks-sa - fix division by zero in ks_sa_rng_init (git-fixes).\n- hwrng: nomadik - add ARM_AMBA dependency (git-fixes).\n- hypfs_create_cpu_files(): add missing check for hypfs_mkdir() failure (git-fixes bsc#1249122).\n- i2c: designware: Add disabling clocks when probe fails (git-fixes).\n- i2c: i801: Hide Intel Birch Stream SoC TCO WDT (git-fixes).\n- i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD (git-fixes).\n- i2c: riic: Allow setting frequencies lower than 50KHz (git-fixes).\n- i2c: tegra: Use internal reset when reset property is not available (bsc#1249143)\n- i3c: Fix default I2C adapter timeout value (git-fixes).\n- i3c: master: svc: Recycle unused IBI slot (git-fixes).\n- iio: consumers: Fix offset handling in iio_convert_raw_to_processed() (git-fixes).\n- iio: dac: ad5360: use int type to store negative error codes (git-fixes).\n- iio: dac: ad5421: use int type to store negative error codes (git-fixes).\n- iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE (git-fixes).\n- iio: frequency: adf4350: Fix prescaler usage (git-fixes).\n- iio: imu: inv_icm42600: Drop redundant pm_runtime reinitialization in resume (git-fixes).\n- iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK (git-fixes).\n- iio: xilinx-ams: Unmask interrupts after updating alarms (git-fixes).\n- iommu/vt-d: Fix __domain_mapping()'s usage of switch_to_super_page() (git-fixes).\n- isolcpus: add missing hunk back (bsc#1236897 bsc#1249206).\n- kABI fix after vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- kABI fix for 'netfilter: nf_tables: Audit log rule reset' (git-fixes).\n- kABI workaround for 'drm/dp: Add an EDID quirk for the DPCD register access probe' (bsc#1248121).\n- kABI workaround for RCU tasks exit tracking (bsc#1246298).\n- kABI: adjust new field on ip_ct_sctp struct (git-fixes).\n- kABI: arm64: ftrace: Restore init_module behavior (git-fixes).\n- kABI: arm64: ftrace: Restore struct mod_arch_specific layout (git-fixes).\n- kABI: make nft_trans_gc_catchall() public again (git-fixes).\n- kABI: netfilter flowtable move gc operation to bottom (git-fixes).\n- kabi: Restore layout of parallel_data (bsc1248343).\n- kabi: add struct cgroup_extra (bsc#1247963).\n- kabi: restore layout of struct cgroup_rstat_cpu (bsc#1247963).\n- kbuild/modpost: Continue processing all unresolved symbols when KLP_SYM_RELA is found (bsc#1218644, bsc#1250655).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- mISDN: Fix memory leak in dsp_hwec_enable() (git-fixes).\n- maple_tree: fix MAPLE_PARENT_RANGE32 and parent pointer docs (git-fixes).\n- media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove (git-fixes).\n- media: cx18: Add missing check after DMA map (git-fixes).\n- media: i2c: mt9v111: fix incorrect type for ret (git-fixes).\n- media: lirc: Fix error handling in lirc_register() (git-fixes).\n- media: pci: ivtv: Add missing check after DMA map (git-fixes).\n- media: rc: fix races with imon_disconnect() (git-fixes).\n- media: rj54n1cb0c: Fix memleak in rj54n1_probe() (git-fixes).\n- media: st-delta: avoid excessive stack usage (git-fixes).\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID (git-fixes).\n- media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (git-fixes).\n- media: zoran: Remove zoran_fh structure (git-fixes).\n- memory: samsung: exynos-srom: Fix of_iomap leak in exynos_srom_probe (git-fixes).\n- mfd: rz-mtu3: Fix MTU5 NFCR register offset (git-fixes).\n- mfd: vexpress-sysreg: Check the return value of devm_gpiochip_add_data() (git-fixes).\n- misc: genwqe: Fix incorrect cmd field being reported in error (git-fixes).\n- mm/hwpoison: do not send SIGBUS to processes with recovered clean pages (git-fixes).\n- mm/memory-failure: fix infinite UCE for VM_PFNMAP pfn (git-fixes).\n- mm: introduce and use {pgd,p4d}_populate_kernel() (git-fixes).\n- mm: move page table sync declarations to linux/pgtable.h (git-fixes).\n- mmc: core: Use GFP_NOIO in ACMD22 (git-fixes).\n- mmc: mvsdio: Fix dma_unmap_sg() nents value (git-fixes).\n- mmc: sdhci-cadence: add Mobileye eyeQ support (stable-fixes).\n- mtd: nand: raw: atmel: Fix comment in timings preparation (stable-fixes).\n- mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing (git-fixes).\n- mtd: rawnand: omap2: fix device leak on probe failure (git-fixes).\n- mtd: rawnand: stm32_fmc2: avoid overlapping mappings on ECC buffer (git-fixes).\n- mtd: rawnand: stm32_fmc2: fix ECC overwrite (git-fixes).\n- net: hv_netvsc: fix loss of early receive events from host during channel open (git-fixes).\n- net: nfc: nci: Add parameter validation for packet data (git-fixes).\n- net: phy: fix phy_uses_state_machine() (git-fixes).\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer (git-fixes).\n- net: rose: convert 'use' field to refcount_t (git-fixes).\n- net: rose: fix a typo in rose_clear_routes() (git-fixes).\n- net: rose: include node references in rose_neigh refcount (git-fixes).\n- net: rose: split remove and free operations in rose_remove_neigh() (stable-fixes).\n- net: usb: Remove disruptive netif_wake_queue in rtl8150_set_multicast (git-fixes).\n- net: usb: cdc-ncm: check for filtering capability (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion LE910C4-WWX new compositions (git-fixes).\n- netfilter: conntrack: fix extension size table (git-fixes).\n- netfilter: flowtable: GC pushes back packets to classic path (git-fixes).\n- netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp (git-fixes).\n- netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses (git-fixes).\n- netfilter: nf_conntrack_bridge: initialize err to 0 (git-fixes).\n- netfilter: nf_tables: A better name for nft_obj_filter (git-fixes).\n- netfilter: nf_tables: Audit log rule reset (git-fixes).\n- netfilter: nf_tables: Carry reset boolean in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Carry s_idx in nft_obj_dump_ctx (git-fixes).\n- netfilter: nf_tables: Deduplicate nft_register_obj audit logs (git-fixes).\n- netfilter: nf_tables: Drop pointless memset in nf_tables_dump_obj (git-fixes).\n- netfilter: nf_tables: Drop pointless memset when dumping rules (git-fixes).\n- netfilter: nf_tables: Fix entries val in rule reset audit log (git-fixes).\n- netfilter: nf_tables: Introduce nf_tables_getrule_single() (git-fixes).\n- netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() (git-fixes).\n- netfilter: nf_tables: Unbreak audit log reset (git-fixes).\n- netfilter: nf_tables: Unconditionally allocate nft_obj_filter (git-fixes).\n- netfilter: nf_tables: audit log object reset once per table (git-fixes).\n- netfilter: nf_tables: bogus ENOENT when destroying element which does not exist (git-fixes).\n- netfilter: nf_tables: disallow element removal on anonymous sets (git-fixes).\n- netfilter: nf_tables: do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: nft_obj_filter fits into cb-\u003ectx (git-fixes).\n- netfilter: nf_tables: remove catchall element in GC sync path (git-fixes).\n- netfilter: nf_tables: revert do not remove elements if set backend implements .abort (git-fixes).\n- netfilter: nf_tables: split async and sync catchall in two functions (git-fixes).\n- netfilter: nfnetlink_log: silence bogus compiler warning (git-fixes).\n- netfilter: nft_payload: fix wrong mac header matching (git-fixes).\n- netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration (git-fixes).\n- netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC (git-fixes).\n- netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails (git-fixes).\n- netfilter: nft_set_rbtree: prefer sync gc to async worker (git-fixes).\n- netfilter: nft_set_rbtree: rename gc deactivate+erase function (git-fixes).\n- netfilter: xt_recent: fix (increase) ipv6 literal buffer length (git-fixes).\n- nilfs2: fix CFI failure when accessing /sys/fs/nilfs2/features/* (git-fixes).\n- nouveau: fix disabling the nonstall irq due to storm code (git-fixes).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-pci: try function level reset on init failure (git-fixes).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- orangefs: Remove unused type in macro fill_default_sys_attrs (git-fixes).\n- pcmcia: Add error handling for add_interval() in do_validate_mem() (git-fixes).\n- pcmcia: Fix a NULL pointer dereference in __iodyn_find_io_region() (git-fixes).\n- pcmcia: omap: Add missing check for platform_get_resource (git-fixes).\n- phy: rockchip: naneng-combphy: Enable U3 OTG port for RK3568 (git-fixes).\n- phy: tegra: xusb: fix device and OF node leak at probe (git-fixes).\n- phy: ti-pipe3: fix device leak at unbind (git-fixes).\n- pinctrl: equilibrium: Remove redundant semicolons (git-fixes).\n- pinctrl: meson-gxl: add missing i2c_d pinmux (git-fixes).\n- pinctrl: renesas: Use int type to store negative error codes (git-fixes).\n- pinctrl: samsung: Drop unused S3C24xx driver data (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove newline char from event name input (git-fixes).\n- platform/mellanox: mlxbf-pmc: Validate event/enable input (git-fixes).\n- platform/x86/amd/pmc: Add TUXEDO IB Pro Gen10 AMD to spurious 8042 quirks list (stable-fixes).\n- platform/x86: dell-wmi-sysman: Fix class device unregistration (git-fixes).\n- platform/x86: think-lmi: Fix class device unregistration (git-fixes).\n- platform/x86: thinkpad_acpi: Handle KCOV __init vs inline mismatches (git-fixes).\n- power: supply: bq27xxx: fix error return in case of no bq27000 hdq battery (git-fixes).\n- power: supply: bq27xxx: restrict no-battery detection to bq27000 (git-fixes).\n- power: supply: cw2015: Fix a alignment coding style issue (git-fixes).\n- power: supply: max77976_charger: fix constant current reporting (git-fixes).\n- pptp: fix pptp_xmit() error path (git-fixes).\n- pwm: berlin: Fix wrong register in suspend/resume (git-fixes).\n- pwm: tiehrpwm: Fix corner case in clock divisor calculation (git-fixes).\n- pwm: tiehrpwm: Make code comment in .free() more useful (git-fixes).\n- rcu-tasks: Add data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Eliminate deadlocks involving do_exit() and RCU (bsc#1246298)\n- rcu-tasks: Initialize callback lists at rcu_init() time (bsc#1246298)\n- rcu-tasks: Initialize data to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() (bsc#1246298)\n- rcu-tasks: Maintain real-time response in (bsc#1246298)\n- rcu/exp: Fix RCU expedited parallel grace period kworker (git-fixes)\n- rcu/exp: Handle RCU expedited grace period kworker allocation (git-fixes)\n- rcu: Fix racy re-initialization of irq_work causing hangs (git-fixes)\n- regmap: Remove superfluous check for !config in __regmap_init() (git-fixes).\n- regulator: scmi: Use int type to store negative error codes (git-fixes).\n- regulator: sy7636a: fix lifecycle of power good gpio (git-fixes).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- s390/cpum_cf: Deny all sampling events by counter PMU (git-fixes bsc#1249481).\n- s390/hypfs: Avoid unnecessary ioctl registration in debugfs (git-fixes bsc#1248733 LTC#214881).\n- s390/hypfs: Enable limited access during lockdown (git-fixes bsc#1248733 LTC#214881).\n- s390/ism: fix concurrency management in ism_cmd() (git-fixes bsc#1248735).\n- s390/pai: Deny all events not handled by this PMU (git-fixes bsc#1249482).\n- s390/pci: Allow automatic recovery with minimal driver support (git-fixes bsc#1248734 LTC#214880).\n- s390/sclp: Fix SCCB present check (git-fixes bsc#1249123).\n- s390/stp: Remove udelay from stp_sync_clock() (git-fixes bsc#1249124).\n- s390/time: Use monotonic clock in get_cycles() (git-fixes bsc#1249125).\n- s390/vfio-ap: Fix no AP queue sharing allowed message written to kernel log (git-fixes bsc#1249488).\n- sched/deadline: Collect sched_dl_entity initialization (git-fixes)\n- sched/fair: Remove unused parameter from sched_asym() (git-fixes)\n- sched/fair: Take the scheduling domain into account in (git-fixes)\n- sched/isolation: Fix boot crash when maxcpus \u0026lt; first (git-fixes)\n- sched/numa, mm: do not try to migrate memory to memoryless (git-fixes)\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- scsi: qla2xxx: Avoid stack frame size warning in qla_dfs (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in START_SP_W_RETRIES() (git-fixes).\n- scsi: qla2xxx: Fix incorrect sign of error code in qla_nvme_xmt_ls_rsp() (git-fixes).\n- scsi: qla2xxx: Remove firmware URL (git-fixes).\n- scsi: qla2xxx: Use secs_to_jiffies() instead of msecs_to_jiffies() (git-fixes).\n- scsi: qla2xxx: edif: Fix incorrect sign of error code (git-fixes).\n- seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast (git-fixes).\n- selftests/bpf: Add asserts for netfilter link info (git-fixes).\n- selftests/bpf: Add cmp_map_pointer_with_const test (git-fixes).\n- selftests/bpf: Add test cases with CONST_PTR_TO_MAP null checks (git-fixes).\n- selftests/bpf: adapt one more case in test_lru_map to the new target_free (git-fixes).\n- selftests/cpufreq: Fix cpufreq basic read and update testcases (bsc#1250344).\n- selftests: bpf: test batch lookup on array of maps with holes (git-fixes).\n- serial: max310x: Add error checking in probe() (git-fixes).\n- serial: sc16is7xx: fix bug in flow control levels init (git-fixes).\n- soc: qcom: rpmh-rsc: Unconditionally clear _TRIGGER bit for TCS (git-fixes).\n- spi: bcm2835: Remove redundant semicolons (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before DAC access (git-fixes).\n- spi: cadence-quadspi: Flush posted register writes before INDAC access (git-fixes).\n- spi: mtk-snfi: Remove redundant semicolons (git-fixes).\n- spi: spi-fsl-lpspi: Fix transmissions when using CONT (git-fixes).\n- spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort (git-fixes).\n- spi: spi-fsl-lpspi: Set correct chip-select polarity bit (git-fixes).\n- struct cdc_ncm_ctx: hide new member filtering_supported (git-fixes).\n- struct ci_hdrc: new member has_short_pkt_limit to end (git-fixes).\n- struct l2cap_chan: shift new member rx_avail to end (git-fixes).\n- supported.conf: mark hyperv_drm as external\n- thermal/drivers/qcom/lmh: Add missing IRQ includes (git-fixes).\n- thunderbolt: Compare HMAC values in constant time (git-fixes).\n- tty: hvc_console: Call hvc_kick in hvc_write unconditionally (bsc#1230062).\n- tty: n_gsm: Do not block input queue by waiting MSC (git-fixes).\n- uio: uio_pdrv_genirq: Remove MODULE_DEVICE_TABLE (git-fixes).\n- usb: chipidea: add CI_HDRC_HAS_SHORT_PKT_LIMIT flag (git-fixes).\n- usb: core: Add 0x prefix to quirks debug output (stable-fixes).\n- usb: dwc3: imx8mp: fix device leak at unbind (git-fixes).\n- usb: dwc3: qcom: Do not leave BCR asserted (git-fixes).\n- usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup (git-fixes).\n- usb: misc: qcom_eud: Access EUD_MODE_MANAGER2 through secure calls (git-fixes).\n- usb: typec: fusb302: cache PD RX state (git-fixes).\n- usb: typec: maxim_contaminant: disable low power mode when reading comparator values (git-fixes).\n- usb: typec: maxim_contaminant: re-enable cc toggle if cc is open and port is clean (git-fixes).\n- usb: typec: tcpci: use GENMASK() for TCPC_ROLE_CTRL_CC[12] (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: fix non-contaminant CC handling (git-fixes).\n- usb: typec: tcpm/tcpci_maxim: use GENMASK() for TCPC_VENDOR_CC_CTRL2 register (git-fixes).\n- usb: xhci: Fix invalid pointer dereference in Etron workaround (git-fixes).\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- vhost-scsi: Fix log flooding with target does not exist errors (git-fixes).\n- vhost-scsi: Return queue full for page alloc failures during copy (git-fixes).\n- vhost/net: Protect ubufs with rcu read lock in vhost_net_ubuf_put() (git-fixes).\n- vhost/vsock: Avoid allocating arbitrarily-sized SKBs (git-fixes).\n- vhost: fail early when __vhost_add_used() fails (git-fixes).\n- vsock/virtio: Resize receive buffers so that each SKB fits in a 4K page (git-fixes).\n- vsock/virtio: fix `rx_bytes` accounting for stream sockets (git-fixes).\n- vsock: Allow retrying on connect() failure (git-fixes).\n- vsock: Fix IOCTL_VM_SOCKETS_GET_LOCAL_CID to check also `transport_local` (git-fixes).\n- vsock: avoid timeout during connect() if the socket is closing (git-fixes).\n- watchdog: mpc8xxx_wdt: Reload the watchdog timer when enabling the watchdog (git-fixes).\n- wifi: ath10k: avoid unnecessary wait for service ready message (git-fixes).\n- wifi: ath11k: HAL SRNG: do not deinitialize and re-initialize again (git-fixes).\n- wifi: ath11k: fix NULL dereference in ath11k_qmi_m3_load() (git-fixes).\n- wifi: ath11k: fix group data packet drops during rekey (git-fixes).\n- wifi: ath12k: Add MODULE_FIRMWARE() entries (bsc#1250952).\n- wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work (git-fixes).\n- wifi: cfg80211: fix use-after-free in cmp_bss() (git-fixes).\n- wifi: cfg80211: remove cfg80211_inform_single_bss_frame_data() (git-fixes).\n- wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (git-fixes).\n- wifi: cw1200: cap SSID length in cw1200_do_join() (git-fixes).\n- wifi: iwlwifi: uefi: check DSM item validity (git-fixes).\n- wifi: libertas: cap SSID len in lbs_associate() (git-fixes).\n- wifi: mac80211: fix Rx packet handling when pubsta information is not available (git-fixes).\n- wifi: mac80211: fix incorrect type for ret (stable-fixes).\n- wifi: mac80211: increase scan_ies_len for S1G (stable-fixes).\n- wifi: mt76: fix potential memory leak in mt76_wmac_probe() (git-fixes).\n- wifi: mt76: mt7996: Initialize hdr before passing to skb_put_data() (git-fixes).\n- wifi: mwifiex: Initialize the chan_stats array to zero (git-fixes).\n- wifi: mwifiex: send world regulatory domain to driver (git-fixes).\n- wifi: rtw89: avoid circular locking dependency in ser_state_run() (git-fixes).\n- wifi: virt_wifi: Fix page fault on connect (stable-fixes).\n- wifi: wilc1000: avoid buffer overflow in WID string configuration (stable-fixes).\n- wireless: purelifi: plfxlc: fix memory leak in plfxlc_usb_wreq_asyn() (git-fixes).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (bsc#1237776).\n- writeback: Avoid contention on wb-\u003elist_lock when switching inodes (kABI fixup) (bsc#1237776).\n- writeback: Avoid excessively long inode switching times (bsc#1237776).\n- writeback: Avoid softlockup when switching many inodes (bsc#1237776).\n- x86/CPU/AMD: WARN when setting EFER.AUTOIBRS if and only if the WRMSR fails (git-fixes).\n- x86/Kconfig: Always enable ARCH_SPARSEMEM_ENABLE (git-fixes).\n- x86/amd_nb: Restrict init function to AMD-based systems (git-fixes).\n- x86/cpu: Add model number for Intel Clearwater Forest processor (git-fixes).\n- x86/fpu: Delay instruction pointer fixup until after warning (git-fixes).\n- x86/microcode/AMD: Handle the case of no BIOS microcode (git-fixes).\n- x86/mm/64: define ARCH_PAGE_TABLE_SYNC_MASK and arch_sync_kernel_mappings() (git-fixes).\n- x86/rdrand: Disable RDSEED on AMD Cyan Skillfish (git-fixes).\n- xen/gntdev: remove struct gntdev_copy_batch from stack (git-fixes).\n- xen/netfront: Fix TX response spurious interrupts (git-fixes).\n- xen: Add support for XenServer 6.1 platform device (git-fixes).\n- xenbus: Allow PVH dom0 a non-local xenstore (git-fixes).\n- xfs: rearrange code in xfs_inode_item_precommit (bsc#1237449).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n- xhci: Fix control transfer error on Etron xHCI host (git-fixes).\n- xhci: dbc: Fix full DbC transfer ring after several reconnects (git-fixes).\n- xhci: fix memory leak regression when freeing xhci vdev devices depth first (git-fixes).\n- xirc2ps_cs: fix register access when enabling FullDuplex (git-fixes).\n","status":"published","published":"2025-10-23T10:25:37Z","modified":"2026-02-04T03:34:51.587918Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:3761-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP5 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2022-49138: Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt (bsc#1238160).\n- CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev-\u003e{dev_name,short_name} (bsc#1246968).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50409: net: If sock is dead do not access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53178: mm: fix zswap writeback race condition (bsc#1249827).\n- CVE-2023-53257: wifi: mac80211: check S1G action frame size (bsc#1249869).\n- CVE-2023-53321: wifi: mac80211_hwsim: drop short frames (bsc#1250313).\n- CVE-2023-53438: x86/MCE: Always save CS register on AMD Zen IF Poison errors (bsc#1250180).\n- CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).\n- CVE-2025-37958: mm/huge_memory: fix dereferencing invalid pmd migration entry (bsc#1243539).\n- CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).\n- CVE-2025-38111: net/mdiobus: Fix potential out-of-bounds read/write access (bsc#1245666).\n- CVE-2025-38380: i2c/designware: Fix an initialization issue (bsc#1247028).\n- CVE-2025-38488: smb: client: fix use-after-free in crypt_message when using async crypto (bsc#1247239).\n- CVE-2025-38553: net/sched: Restrict conditions for adding duplicating netems to qdisc tree (bsc#1248255).\n- CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment() (bsc#1248399).\n- CVE-2025-38659: gfs2: No more self recovery (bsc#1248639).\n- CVE-2025-38664: ice: Fix a null pointer dereference in ice_copy_and_init_pkg() (bsc#1248628).\n- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249126).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38706: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() (bsc#1249195).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-39691: fs/buffer: fix use-after-free when call bh_read() helper (bsc#1249374).\n- CVE-2025-39703: net, hsr: reject HSR frame if skb can't hold tag (bsc#1249315).\n- CVE-2025-39726: s390/ism: fix concurrency management in ism_cmd() (bsc#1249266).\n- CVE-2025-39746: wifi: ath10k: shutdown driver when hardware is unreliable (bsc#1249516).\n- CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control (bsc#1249538).\n- CVE-2025-39790: bus: mhi: host: Detect events pointing to unexpected TREs (bsc#1249548).\n- CVE-2025-39823: KVM: x86: use array_index_nospec with indices that come from guest (bsc#1250002).\n- CVE-2025-39824: HID: asus: fix UAF via HID_CLAIMED_INPUT validation (bsc#1250007).\n- CVE-2025-39860: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() (bsc#1250247).\n- CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map (bsc#1250406).\n\nThe following non-security bugs were fixed:\n\n- Kconfig.suse: Add KABI checkiness macro (config) (bsc#1249186).\n- Limit patch filenames to 100 characters (bsc#1249604).\n- Move pesign-obs-integration requirement from kernel-syms to kernel devel subpackage (bsc#1248108).\n- Revert selinux patches that caused regressions (bsc#1249353).\n- btrfs: avoid NULL pointer dereference if no valid extent tree (bsc#1249158).\n- build_bug.h: Add KABI assert (bsc#1249186).\n- hv_netvsc: Fix panic during namespace deletion with VF (bsc#1248111).\n- kabi/severities: ignore kABI for atheros helper modules The symbols are used only internally by atheros drivers.\n- kernel-binary: Another installation ordering fix (bsc#1241353).\n- kernel-source: Do not list mkspec and its inputs as sources (bsc#1250522).\n- kernel-subpackage-build: Decompress ghost file when compressed version exists (bsc#1249346)\n- kernel-syms.spec: Drop old rpm release number hack (bsc#1247172).\n- net/sched: ets: use old 'nbands' while purging unused classes (git-fixes).\n- rpm/kernel-subpackage-spec: Skip brp-strip-debug to avoid file truncation (bsc#1246879).\n- rpm/mkspec: Fix missing kernel-syms-rt creation (bsc#1244337).\n- rpm: Configure KABI checkingness macro (bsc#1249186).\n- rpm: Drop support for kabi/arch/ignore-flavor (bsc#1249186).\n- rpm: Link arch-symbols script from scripts directory.\n- rpm: Link guards script from scripts directory.\n- supported.conf: mark hyperv_drm as external\n- use uniform permission checks for all mount propagation changes (git-fixes).\n- xfs: rework datasync tracking and execution (bsc#1237449).\n","status":"published","published":"2025-10-23T15:04:37Z","modified":"2026-02-04T03:42:49.757429Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4057-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).\n- CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).\n- CVE-2025-38552: mptcp: plug races between subflow fail and subflow creation (bsc#1248230).\n- CVE-2025-38653: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (bsc#1248630).\n- CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).\n- CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn-\u003edd_data only if memory is allocated (bsc#1249182).\n- CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39673: ppp: fix race conditions in ppp_fill_forward_path (bsc#1249320).\n- CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).\n- CVE-2025-39683: tracing: Limit access to parser-\u003ebuffer when trace_get_user failed (bsc#1249286).\n- CVE-2025-39697: nfs: remove dead code for the old swap over NFS implementation (bsc#1249319).\n- CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).\n- CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).\n- CVE-2025-39794: ARM: tegra: Use I/O memcpy to write to IRAM (bsc#1249595).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).\n- CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).\n- CVE-2025-39828: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control() (bsc#1250205).\n- CVE-2025-39832: net/mlx5: Add sync reset drop mode support (bsc#1249901).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39851: vxlan: Fix NPD when refreshing an FDB entry with a nexthop object (bsc#1250296).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).\n- CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).\n- CVE-2025-39881: kernfs: Fix UAF in polling when open file is released (bsc#1250379).\n- CVE-2025-39895: sched: Fix sched_numa_find_nth_cpu() if mask offline (bsc#1250721).\n- CVE-2025-39898: e1000e: fix heap overflow in e1000_set_eeprom (bsc#1250742).\n- CVE-2025-39900: net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y (bsc#1250758).\n- CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (bsc#1250702).\n- CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).\n- CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).\n- CVE-2025-39946: tls: make sure to abort the stream if headers are bogus (bsc#1251114).\n- CVE-2025-39947: net/mlx5e: Harden uplink netdev access against device unbind (bsc#1251232).\n- CVE-2025-39948: ice: fix Rx page leak on multi-buffer frames (bsc#1251233).\n- CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).\n- CVE-2025-39955: tcp: Clear tcp_sk(sk)-\u003efastopen_rsk in tcp_disconnect() (bsc#1251804).\n- CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).\n- CVE-2025-39969: i40e: fix validation of VF state in get resources (bsc#1252044).\n- CVE-2025-39970: i40e: fix input validation logic for action_meta (bsc#1252051).\n- CVE-2025-39971: i40e: fix idx validation in config queues msg (bsc#1252052).\n- CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).\n- CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).\n- CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).\n- CVE-2025-39984: net: tun: Update napi-\u003eskb after XDP process (bsc#1252081).\n- CVE-2025-40000: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() (bsc#1252062).\n- CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy (bsc#1252349).\n- CVE-2025-40012: net/smc: fix warning in smc_rx_splice() when calling get_page() (bsc#1252330).\n- CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).\n- CVE-2025-40051: vhost: vringh: Modify the return value check (bsc#1252858).\n- CVE-2025-40056: vhost: vringh: Fix copy_to_iter return value check (bsc#1252826).\n- CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures (bsc#1252848).\n- CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).\n- CVE-2025-40100: btrfs: do not assert we found block group item when creating free space tree (bsc#1252918).\n\nThe following non security issues were fixed:\n\n- ACPI/processor_idle: Add FFH state handling (jsc#PED-13815).\n- ACPI/processor_idle: Export acpi_processor_ffh_play_dead() (jsc#PED-13815).\n- ACPI: battery: Add synchronization between interface updates (git-fixes).\n- ACPI: processor: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- KVM: PPC: Fix misleading interrupts comment in kvmppc_prepare_to_enter() (bsc#1215199).\n- KVM: x86: Plumb in the vCPU to kvm_x86_ops.hwapic_isr_update() (git-fixes).\n- KVM: x86: Process 'guest stopped request' once per guest time update (git-fixes).\n- PM: hibernate: Add pm_hibernation_mode_is_suspend() (bsc#1243112).\n- PM: hibernate: Add stub for pm_hibernate_is_recovering() (bsc#1243112).\n- PM: hibernate: Fix pm_hibernation_mode_is_suspend() build breakage (bsc#1243112).\n- PM: hibernate: add new api pm_hibernate_is_recovering() (bsc#1243112).\n- bpf: Allow helper bpf_get_[ns_]current_pid_tgid() for all prog types (bsc#1252364).\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() (stable-fixes git-fixes).\n- cpuidle: Do not return from cpuidle_play_dead() on callback failures (jsc#PED-13815).\n- dpll: Make ZL3073X invisible (bsc#1252253).\n- dpll: zl3073x: Add firmware loading functionality (bsc#1252253).\n- dpll: zl3073x: Add functions to access hardware registers (bsc#1252253).\n- dpll: zl3073x: Add low-level flash functions (bsc#1252253).\n- dpll: zl3073x: Add support to get fractional frequency offset (bsc#1252253).\n- dpll: zl3073x: Add support to get phase offset on connected input pin (bsc#1252253).\n- dpll: zl3073x: Add support to get/set esync on pins (bsc#1252253).\n- dpll: zl3073x: Fix build failure (bsc#1252253).\n- dpll: zl3073x: Fix double free in zl3073x_devlink_flash_update() (bsc#1252253).\n- dpll: zl3073x: Handle missing or corrupted flash configuration (bsc#1252253).\n- dpll: zl3073x: Implement devlink flash callback (bsc#1252253).\n- dpll: zl3073x: Increase maximum size of flash utility (bsc#1252253).\n- dpll: zl3073x: Refactor DPLL initialization (bsc#1252253).\n- dpll: zl3073x: ZL3073X_I2C and ZL3073X_SPI should depend on NET (bsc#1252253).\n- drm/amd : Update MES API header file for v11 \u0026 v12 (stable-fixes).\n- drm/amd/amdgpu: Implement MES suspend/resume gang functionality for v12 (bsc#1243112).\n- drm/amd/display: Add NULL check for stream before dereference in 'dm_vupdate_high_irq' (bsc#1243112).\n- drm/amd/display: Enable Dynamic DTBCLK Switch (bsc#1243112).\n- drm/amd/display: Fix vupdate_offload_work doc (bsc#1243112).\n- drm/amd/display: fix dmub access race condition (bsc#1243112).\n- drm/amd/display: more liberal vmin/vmax update for freesync (bsc#1243112).\n- drm/amd/include : MES v11 and v12 API header update (stable-fixes).\n- drm/amd/include : Update MES v12 API for fence update (stable-fixes).\n- drm/amd/pm: fix smu table id bound check issue in smu_cmn_update_table() (git-fixes).\n- drm/amd: Avoid evicting resources at S5 (bsc#1243112).\n- drm/amd: Check whether secure display TA loaded successfully (bsc#1243112).\n- drm/amd: Fix hybrid sleep (bsc#1243112).\n- drm/amd: Only restore cached manual clock settings in restore if OD enabled (bsc#1243112).\n- drm/amd: Restore cached manual clock settings during resume (bsc#1243112).\n- drm/amdgpu/mes11: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes12: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes: add front end for detect and reset hung queue (bsc#1243112).\n- drm/amdgpu/vpe: cancel delayed work in hw_fini (bsc#1243112).\n- drm/amdgpu: Avoid rma causes GPU duplicate reset (bsc#1243112).\n- drm/amdgpu: Fix for GPU reset being blocked by KIQ I/O (bsc#1243112).\n- drm/amdgpu: Report individual reset error (bsc#1243112).\n- drm/amdgpu: do not resume device in thaw for normal hibernation (bsc#1243112).\n- drm/amdgpu: fix link error for !PM_SLEEP (bsc#1243112).\n- drm/amdkfd: Fix mmap write lock not release (bsc#1243112).\n- drm/xe/guc: Prepare GuC register list and update ADS size for error capture (stable-fixes).\n- ext4: fix checks for orphan inodes (bsc#1250119).\n- hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat() (git-fixes).\n- intel_idle: Provide the default enter_dead() handler (jsc#PED-13815).\n- intel_idle: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- intel_idle: Use subsys_initcall_sync() for initialization (jsc#PED-13815).\n- ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd (bsc#1247222).\n- ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation (bsc#1247222).\n- ixgbevf: fix getting link speed data for E610 devices (bsc#1247222).\n- ixgbevf: fix mailbox API compatibility by negotiating supported features (bsc#1247222).\n- kdb: Replace deprecated strcpy() with memmove() in vkdb_printf() (bsc#1252939).\n- net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency (bsc#1248754).\n- netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).\n- nvme-auth: update bi_directional flag (git-fixes bsc#1249735).\n- nvme-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-tcp: send only permitted commands for secure concat (git-fixes bsc#1247683).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- perf/x86/intel: Allow to update user space GPRs from PEBS records (git-fixes).\n- perf/x86/intel: Fix crash in icl_update_topdown_event() (git-fixes).\n- phy: cadence: cdns-dphy: Update calibration wait time for startup state machine (git-fixes).\n- platform/x86/amd/pmc: Add 1Ah family series to STB support list (bsc#1243112).\n- platform/x86/amd/pmc: Add MECHREVO Yilong15Pro to spurious_8042 list (bsc#1243112).\n- platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list (bsc#1243112).\n- platform/x86/amd/pmc: Add VPE information for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Add idlemask support for 1Ah family (bsc#1243112).\n- platform/x86/amd/pmc: Extend support for PMC features on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Fix SMU command submission path on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Modify SMU message port for latest AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Notify user when platform does not support s0ix transition (bsc#1243112).\n- platform/x86/amd/pmc: Remove unnecessary line breaks (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Update IP information structure for newer SoCs (bsc#1243112).\n- platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information (bsc#1243112).\n- platform/x86/amd/pmc: call amd_pmc_get_ip_info() during driver probe (bsc#1243112).\n- platform/x86/amd: pmc: Add new ACPI ID AMDI000B (bsc#1243112).\n- platform/x86/amd: pmc: Drop SMU F/W match for Cezanne (bsc#1243112).\n- platform/x86/amd: pmc: Use guard(mutex) (bsc#1243112).\n- powerpc/boot: Fix build with gcc 15 (bsc#1215199).\n- powerpc/fadump: skip parameter area allocation when fadump is disabled (jsc#PED-9891 git-fixes).\n- powerpc/kvm: Fix ifdef to remove build warning (bsc#1215199).\n- powerpc/powernv/pci: Fix underflow and leak issue (bsc#1215199).\n- powerpc/pseries/msi: Fix potential underflow and leak issue (bsc#1215199).\n- powerpc: floppy: Add missing checks after DMA map (bsc#1215199).\n- proc: fix missing pde_set_flags() for net proc files (bsc#1248630)\n- proc: fix type confusion in pde_set_flags() (bsc#1248630)\n- sched/idle: Conditionally handle tick broadcast in default_idle_call() (bsc#1248517).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- serial: sc16is7xx: rename Kconfig CONFIG_SERIAL_SC16IS7XX_CORE (bsc#1252469) Re-enable CONFIG_SERIAL_SC16IS7X for aarch64 and x86_64 default configurations, but keep it disabled for kvmsmall configurations. For ppc64 and s390x drivers was not enabled, so keep it that way. Add sc16is7xx_spi and sc16is7xx_i2c drivers to supported list.\n- skmsg: Return copied bytes in sk_msg_memcopy_from_iter (bsc#1250650).\n- smb: client: fix crypto buffers in non-linear memory (bsc#1250491, bsc#1239206).\n- smb: client: fix potential cfid UAF in smb2_query_info_compound (bsc#1248886).\n- tcp_bpf: Fix copied value in tcp_bpf_sendmsg (bsc#1250650).\n- tracing: Remove unneeded goto out logic (bsc#1249286).\n- x86/idle: Sanitize X86_BUG_AMD_E400 handling (bsc#1248517).\n- x86/resctrl: Fix miscount of bandwidth event when reactivating previously unavailable RMID (bsc#1252734).\n- x86/resctrl: Refactor resctrl_arch_rmid_read() (bsc#1252734).\n- x86/smp: Allow calling mwait_play_dead with an arbitrary hint (jsc#PED-13815).\n- x86/smp: Fix mwait_play_dead() and acpi_processor_ffh_play_dead() noreturn behavior (jsc#PED-13815).\n- x86/smp: PM/hibernate: Split arch_resume_nosmt() (jsc#PED-13815).\n- x86/topology: Implement topology_is_core_online() to address SMT regression (jsc#PED-13815).\n","status":"published","published":"2025-11-11T18:36:09Z","modified":"2026-02-04T02:23:19.824916Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4132-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 Azure kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).\n- CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).\n- CVE-2025-38552: mptcp: plug races between subflow fail and subflow creation (bsc#1248230).\n- CVE-2025-38653: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (bsc#1248630).\n- CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).\n- CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn-\u003edd_data only if memory is allocated (bsc#1249182).\n- CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39673: ppp: fix race conditions in ppp_fill_forward_path (bsc#1249320).\n- CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).\n- CVE-2025-39683: tracing: Limit access to parser-\u003ebuffer when trace_get_user failed (bsc#1249286).\n- CVE-2025-39697: nfs: remove dead code for the old swap over NFS implementation (bsc#1249319).\n- CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).\n- CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).\n- CVE-2025-39794: ARM: tegra: Use I/O memcpy to write to IRAM (bsc#1249595).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).\n- CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).\n- CVE-2025-39828: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control() (bsc#1250205).\n- CVE-2025-39832: net/mlx5: Add sync reset drop mode support (bsc#1249901).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39851: vxlan: Fix NPD when refreshing an FDB entry with a nexthop object (bsc#1250296).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).\n- CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).\n- CVE-2025-39881: kernfs: Fix UAF in polling when open file is released (bsc#1250379).\n- CVE-2025-39895: sched: Fix sched_numa_find_nth_cpu() if mask offline (bsc#1250721).\n- CVE-2025-39900: net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y (bsc#1250758).\n- CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (bsc#1250702).\n- CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).\n- CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).\n- CVE-2025-39946: tls: make sure to abort the stream if headers are bogus (bsc#1251114).\n- CVE-2025-39947: net/mlx5e: Harden uplink netdev access against device unbind (bsc#1251232).\n- CVE-2025-39948: ice: fix Rx page leak on multi-buffer frames (bsc#1251233).\n- CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).\n- CVE-2025-39955: tcp: Clear tcp_sk(sk)-\u003efastopen_rsk in tcp_disconnect() (bsc#1251804).\n- CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).\n- CVE-2025-39969: i40e: fix validation of VF state in get resources (bsc#1252044).\n- CVE-2025-39970: i40e: fix input validation logic for action_meta (bsc#1252051).\n- CVE-2025-39971: i40e: fix idx validation in config queues msg (bsc#1252052).\n- CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).\n- CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).\n- CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).\n- CVE-2025-39984: net: tun: Update napi-\u003eskb after XDP process (bsc#1252081).\n- CVE-2025-40000: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() (bsc#1252062).\n- CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy (bsc#1252349).\n- CVE-2025-40012: net/smc: fix warning in smc_rx_splice() when calling get_page() (bsc#1252330).\n- CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).\n- CVE-2025-40051: vhost: vringh: Modify the return value check (bsc#1252858).\n- CVE-2025-40056: vhost: vringh: Fix copy_to_iter return value check (bsc#1252826).\n- CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures (bsc#1252848).\n- CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).\n- CVE-2025-40080: nbd: restrict sockets to TCP and UDP (bsc#1252774).\n- CVE-2025-40100: btrfs: do not assert we found block group item when creating free space tree (bsc#1252918).\n\nThe following non security issues were fixed:\n\n- ACPI/processor_idle: Add FFH state handling (jsc#PED-13815).\n- ACPI/processor_idle: Export acpi_processor_ffh_play_dead() (jsc#PED-13815).\n- ACPI: battery: Add synchronization between interface updates (git-fixes).\n- ACPI: processor: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- KVM: PPC: Fix misleading interrupts comment in kvmppc_prepare_to_enter() (bsc#1215199).\n- KVM: x86: Plumb in the vCPU to kvm_x86_ops.hwapic_isr_update() (git-fixes).\n- KVM: x86: Process 'guest stopped request' once per guest time update (git-fixes).\n- PM: hibernate: Add pm_hibernation_mode_is_suspend() (bsc#1243112).\n- PM: hibernate: Add stub for pm_hibernate_is_recovering() (bsc#1243112).\n- PM: hibernate: Fix pm_hibernation_mode_is_suspend() build breakage (bsc#1243112).\n- PM: hibernate: add new api pm_hibernate_is_recovering() (bsc#1243112).\n- bpf: Allow helper bpf_get_[ns_]current_pid_tgid() for all prog types (bsc#1252364).\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() (stable-fixes git-fixes).\n- cpuidle: Do not return from cpuidle_play_dead() on callback failures (jsc#PED-13815).\n- dpll: Make ZL3073X invisible (bsc#1252253).\n- dpll: zl3073x: Add firmware loading functionality (bsc#1252253).\n- dpll: zl3073x: Add functions to access hardware registers (bsc#1252253).\n- dpll: zl3073x: Add low-level flash functions (bsc#1252253).\n- dpll: zl3073x: Add support to get fractional frequency offset (bsc#1252253).\n- dpll: zl3073x: Add support to get phase offset on connected input pin (bsc#1252253).\n- dpll: zl3073x: Add support to get/set esync on pins (bsc#1252253).\n- dpll: zl3073x: Fix build failure (bsc#1252253).\n- dpll: zl3073x: Fix double free in zl3073x_devlink_flash_update() (bsc#1252253).\n- dpll: zl3073x: Handle missing or corrupted flash configuration (bsc#1252253).\n- dpll: zl3073x: Implement devlink flash callback (bsc#1252253).\n- dpll: zl3073x: Increase maximum size of flash utility (bsc#1252253).\n- dpll: zl3073x: Refactor DPLL initialization (bsc#1252253).\n- dpll: zl3073x: ZL3073X_I2C and ZL3073X_SPI should depend on NET (bsc#1252253).\n- drm/amd : Update MES API header file for v11 \u0026 v12 (stable-fixes).\n- drm/amd/amdgpu: Implement MES suspend/resume gang functionality for v12 (bsc#1243112).\n- drm/amd/display: Add NULL check for stream before dereference in 'dm_vupdate_high_irq' (bsc#1243112).\n- drm/amd/display: Enable Dynamic DTBCLK Switch (bsc#1243112).\n- drm/amd/display: Fix vupdate_offload_work doc (bsc#1243112).\n- drm/amd/display: fix dmub access race condition (bsc#1243112).\n- drm/amd/display: more liberal vmin/vmax update for freesync (bsc#1243112).\n- drm/amd/include : MES v11 and v12 API header update (stable-fixes).\n- drm/amd/include : Update MES v12 API for fence update (stable-fixes).\n- drm/amd/pm: fix smu table id bound check issue in smu_cmn_update_table() (git-fixes).\n- drm/amd: Avoid evicting resources at S5 (bsc#1243112).\n- drm/amd: Check whether secure display TA loaded successfully (bsc#1243112).\n- drm/amd: Fix hybrid sleep (bsc#1243112).\n- drm/amd: Only restore cached manual clock settings in restore if OD enabled (bsc#1243112).\n- drm/amd: Restore cached manual clock settings during resume (bsc#1243112).\n- drm/amdgpu/mes11: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes12: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes: add front end for detect and reset hung queue (bsc#1243112).\n- drm/amdgpu/vpe: cancel delayed work in hw_fini (bsc#1243112).\n- drm/amdgpu: Avoid rma causes GPU duplicate reset (bsc#1243112).\n- drm/amdgpu: Fix for GPU reset being blocked by KIQ I/O (bsc#1243112).\n- drm/amdgpu: Report individual reset error (bsc#1243112).\n- drm/amdgpu: do not resume device in thaw for normal hibernation (bsc#1243112).\n- drm/amdgpu: fix link error for !PM_SLEEP (bsc#1243112).\n- drm/amdkfd: Fix mmap write lock not release (bsc#1243112).\n- drm/xe/guc: Prepare GuC register list and update ADS size for error capture (stable-fixes).\n- ext4: fix checks for orphan inodes (bsc#1250119).\n- hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat() (git-fixes).\n- intel_idle: Provide the default enter_dead() handler (jsc#PED-13815).\n- intel_idle: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- intel_idle: Use subsys_initcall_sync() for initialization (jsc#PED-13815).\n- ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd (bsc#1247222).\n- ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation (bsc#1247222).\n- ixgbevf: fix getting link speed data for E610 devices (bsc#1247222).\n- ixgbevf: fix mailbox API compatibility by negotiating supported features (bsc#1247222).\n- kdb: Replace deprecated strcpy() with memmove() in vkdb_printf() (bsc#1252939).\n- module: Prevent silent truncation of module name in delete_module(2) (git-fixes).\n- net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency (bsc#1248754).\n- netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).\n- nvme-auth: update bi_directional flag (git-fixes bsc#1249735).\n- nvme-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-tcp: send only permitted commands for secure concat (git-fixes bsc#1247683).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- perf/x86/intel: Allow to update user space GPRs from PEBS records (git-fixes).\n- perf/x86/intel: Fix crash in icl_update_topdown_event() (git-fixes).\n- phy: cadence: cdns-dphy: Update calibration wait time for startup state machine (git-fixes).\n- platform/x86/amd/pmc: Add 1Ah family series to STB support list (bsc#1243112).\n- platform/x86/amd/pmc: Add MECHREVO Yilong15Pro to spurious_8042 list (bsc#1243112).\n- platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list (bsc#1243112).\n- platform/x86/amd/pmc: Add VPE information for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Add idlemask support for 1Ah family (bsc#1243112).\n- platform/x86/amd/pmc: Extend support for PMC features on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Fix SMU command submission path on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Modify SMU message port for latest AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Notify user when platform does not support s0ix transition (bsc#1243112).\n- platform/x86/amd/pmc: Remove unnecessary line breaks (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Update IP information structure for newer SoCs (bsc#1243112).\n- platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information (bsc#1243112).\n- platform/x86/amd/pmc: call amd_pmc_get_ip_info() during driver probe (bsc#1243112).\n- platform/x86/amd: pmc: Add new ACPI ID AMDI000B (bsc#1243112).\n- platform/x86/amd: pmc: Drop SMU F/W match for Cezanne (bsc#1243112).\n- platform/x86/amd: pmc: Use guard(mutex) (bsc#1243112).\n- powerpc/boot: Fix build with gcc 15 (bsc#1215199).\n- powerpc/fadump: skip parameter area allocation when fadump is disabled (jsc#PED-9891 git-fixes).\n- powerpc/kvm: Fix ifdef to remove build warning (bsc#1215199).\n- powerpc/powernv/pci: Fix underflow and leak issue (bsc#1215199).\n- powerpc/pseries/msi: Fix potential underflow and leak issue (bsc#1215199).\n- powerpc: floppy: Add missing checks after DMA map (bsc#1215199).\n- proc: fix missing pde_set_flags() for net proc files (bsc#1248630)\n- proc: fix type confusion in pde_set_flags() (bsc#1248630)\n- sched/idle: Conditionally handle tick broadcast in default_idle_call() (bsc#1248517).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- serial: sc16is7xx: rename Kconfig CONFIG_SERIAL_SC16IS7XX_CORE (bsc#1252469).\n- skmsg: Return copied bytes in sk_msg_memcopy_from_iter (bsc#1250650).\n- smb: client: fix crypto buffers in non-linear memory (bsc#1250491, bsc#1239206).\n- smb: client: fix potential cfid UAF in smb2_query_info_compound (bsc#1248886).\n- tcp_bpf: Fix copied value in tcp_bpf_sendmsg (bsc#1250650).\n- tracing: Remove unneeded goto out logic (bsc#1249286).\n- x86/idle: Sanitize X86_BUG_AMD_E400 handling (bsc#1248517).\n- x86/resctrl: Fix miscount of bandwidth event when reactivating previously unavailable RMID (bsc#1252734).\n- x86/resctrl: Refactor resctrl_arch_rmid_read() (bsc#1252734).\n- x86/smp: Allow calling mwait_play_dead with an arbitrary hint (jsc#PED-13815).\n- x86/smp: Fix mwait_play_dead() and acpi_processor_ffh_play_dead() noreturn behavior (jsc#PED-13815).\n- x86/smp: PM/hibernate: Split arch_resume_nosmt() (jsc#PED-13815).\n- x86/topology: Implement topology_is_core_online() to address SMT regression (jsc#PED-13815).\n","status":"published","published":"2025-11-18T16:45:55Z","modified":"2026-02-04T02:24:43.256655Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4141-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 RT kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).\n- CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).\n- CVE-2025-38552: mptcp: plug races between subflow fail and subflow creation (bsc#1248230).\n- CVE-2025-38653: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al (bsc#1248630).\n- CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).\n- CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn-\u003edd_data only if memory is allocated (bsc#1249182).\n- CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).\n- CVE-2025-38734: net/smc: fix UAF on smcsk after smc_listen_out() (bsc#1249324).\n- CVE-2025-38735: gve: prevent ethtool ops after shutdown (bsc#1249288).\n- CVE-2025-39673: ppp: fix race conditions in ppp_fill_forward_path (bsc#1249320).\n- CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).\n- CVE-2025-39683: tracing: Limit access to parser-\u003ebuffer when trace_get_user failed (bsc#1249286).\n- CVE-2025-39697: nfs: remove dead code for the old swap over NFS implementation (bsc#1249319).\n- CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).\n- CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).\n- CVE-2025-39794: ARM: tegra: Use I/O memcpy to write to IRAM (bsc#1249595).\n- CVE-2025-39810: bnxt_en: Fix memory corruption when FW resources change during ifdown (bsc#1249975).\n- CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).\n- CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).\n- CVE-2025-39828: atm: atmtcp: Prevent arbitrary write in atmtcp_recv_control() (bsc#1250205).\n- CVE-2025-39832: net/mlx5: Add sync reset drop mode support (bsc#1249901).\n- CVE-2025-39847: ppp: fix memory leak in pad_compress_skb (bsc#1250292).\n- CVE-2025-39850: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects (bsc#1250276).\n- CVE-2025-39851: vxlan: Fix NPD when refreshing an FDB entry with a nexthop object (bsc#1250296).\n- CVE-2025-39853: i40e: Fix potential invalid access when MAC list is empty (bsc#1250275).\n- CVE-2025-39854: ice: fix NULL access of tx-\u003ein_use in ice_ll_ts_intr (bsc#1250297).\n- CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).\n- CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).\n- CVE-2025-39881: kernfs: Fix UAF in polling when open file is released (bsc#1250379).\n- CVE-2025-39895: sched: Fix sched_numa_find_nth_cpu() if mask offline (bsc#1250721).\n- CVE-2025-39900: net_sched: gen_estimator: fix est_timer() vs CONFIG_PREEMPT_RT=y (bsc#1250758).\n- CVE-2025-39902: mm/slub: avoid accessing metadata when pointer is invalid in object_err() (bsc#1250702).\n- CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).\n- CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).\n- CVE-2025-39946: tls: make sure to abort the stream if headers are bogus (bsc#1251114).\n- CVE-2025-39947: net/mlx5e: Harden uplink netdev access against device unbind (bsc#1251232).\n- CVE-2025-39948: ice: fix Rx page leak on multi-buffer frames (bsc#1251233).\n- CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).\n- CVE-2025-39955: tcp: Clear tcp_sk(sk)-\u003efastopen_rsk in tcp_disconnect() (bsc#1251804).\n- CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).\n- CVE-2025-39969: i40e: fix validation of VF state in get resources (bsc#1252044).\n- CVE-2025-39970: i40e: fix input validation logic for action_meta (bsc#1252051).\n- CVE-2025-39971: i40e: fix idx validation in config queues msg (bsc#1252052).\n- CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).\n- CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).\n- CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).\n- CVE-2025-39984: net: tun: Update napi-\u003eskb after XDP process (bsc#1252081).\n- CVE-2025-40000: wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait() (bsc#1252062).\n- CVE-2025-40005: spi: cadence-quadspi: Implement refcount to handle unbind during busy (bsc#1252349).\n- CVE-2025-40012: net/smc: fix warning in smc_rx_splice() when calling get_page() (bsc#1252330).\n- CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).\n- CVE-2025-40051: vhost: vringh: Modify the return value check (bsc#1252858).\n- CVE-2025-40056: vhost: vringh: Fix copy_to_iter return value check (bsc#1252826).\n- CVE-2025-40060: coresight: trbe: Return NULL pointer for allocation failures (bsc#1252848).\n- CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).\n- CVE-2025-40100: btrfs: do not assert we found block group item when creating free space tree (bsc#1252918).\n\nThe following non security issues were fixed:\n\n- ACPI/processor_idle: Add FFH state handling (jsc#PED-13815).\n- ACPI/processor_idle: Export acpi_processor_ffh_play_dead() (jsc#PED-13815).\n- ACPI: battery: Add synchronization between interface updates (git-fixes).\n- ACPI: processor: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- KVM: PPC: Fix misleading interrupts comment in kvmppc_prepare_to_enter() (bsc#1215199).\n- KVM: x86: Plumb in the vCPU to kvm_x86_ops.hwapic_isr_update() (git-fixes).\n- KVM: x86: Process 'guest stopped request' once per guest time update (git-fixes).\n- PM: hibernate: Add pm_hibernation_mode_is_suspend() (bsc#1243112).\n- PM: hibernate: Add stub for pm_hibernate_is_recovering() (bsc#1243112).\n- PM: hibernate: Fix pm_hibernation_mode_is_suspend() build breakage (bsc#1243112).\n- PM: hibernate: add new api pm_hibernate_is_recovering() (bsc#1243112).\n- Reapply 'x86/smp: Eliminate mwait_play_dead_cpuid_hint()' (jsc#PED-13815).\n- bpf: Allow helper bpf_get_[ns_]current_pid_tgid() for all prog types (bsc#1252364).\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() (stable-fixes git-fixes).\n- cpuidle: Do not return from cpuidle_play_dead() on callback failures (jsc#PED-13815).\n- dpll: Make ZL3073X invisible (bsc#1252253).\n- dpll: zl3073x: Add firmware loading functionality (bsc#1252253).\n- dpll: zl3073x: Add functions to access hardware registers (bsc#1252253).\n- dpll: zl3073x: Add low-level flash functions (bsc#1252253).\n- dpll: zl3073x: Add support to get fractional frequency offset (bsc#1252253).\n- dpll: zl3073x: Add support to get phase offset on connected input pin (bsc#1252253).\n- dpll: zl3073x: Add support to get/set esync on pins (bsc#1252253).\n- dpll: zl3073x: Fix build failure (bsc#1252253).\n- dpll: zl3073x: Fix double free in zl3073x_devlink_flash_update() (bsc#1252253).\n- dpll: zl3073x: Handle missing or corrupted flash configuration (bsc#1252253).\n- dpll: zl3073x: Implement devlink flash callback (bsc#1252253).\n- dpll: zl3073x: Increase maximum size of flash utility (bsc#1252253).\n- dpll: zl3073x: Refactor DPLL initialization (bsc#1252253).\n- dpll: zl3073x: ZL3073X_I2C and ZL3073X_SPI should depend on NET (bsc#1252253).\n- drm/amd : Update MES API header file for v11 \u0026 v12 (stable-fixes).\n- drm/amd/amdgpu: Implement MES suspend/resume gang functionality for v12 (bsc#1243112).\n- drm/amd/display: Add NULL check for stream before dereference in 'dm_vupdate_high_irq' (bsc#1243112).\n- drm/amd/display: Enable Dynamic DTBCLK Switch (bsc#1243112).\n- drm/amd/display: Fix vupdate_offload_work doc (bsc#1243112).\n- drm/amd/display: fix dmub access race condition (bsc#1243112).\n- drm/amd/display: more liberal vmin/vmax update for freesync (bsc#1243112).\n- drm/amd/include : MES v11 and v12 API header update (stable-fixes).\n- drm/amd/include : Update MES v12 API for fence update (stable-fixes).\n- drm/amd/pm: fix smu table id bound check issue in smu_cmn_update_table() (git-fixes).\n- drm/amd: Avoid evicting resources at S5 (bsc#1243112).\n- drm/amd: Check whether secure display TA loaded successfully (bsc#1243112).\n- drm/amd: Fix hybrid sleep (bsc#1243112).\n- drm/amd: Only restore cached manual clock settings in restore if OD enabled (bsc#1243112).\n- drm/amd: Restore cached manual clock settings during resume (bsc#1243112).\n- drm/amdgpu/mes11: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes12: implement detect and reset callback (bsc#1243112).\n- drm/amdgpu/mes: add front end for detect and reset hung queue (bsc#1243112).\n- drm/amdgpu/vpe: cancel delayed work in hw_fini (bsc#1243112).\n- drm/amdgpu: Avoid rma causes GPU duplicate reset (bsc#1243112).\n- drm/amdgpu: Fix for GPU reset being blocked by KIQ I/O (bsc#1243112).\n- drm/amdgpu: Report individual reset error (bsc#1243112).\n- drm/amdgpu: do not resume device in thaw for normal hibernation (bsc#1243112).\n- drm/amdgpu: fix link error for !PM_SLEEP (bsc#1243112).\n- drm/amdkfd: Fix mmap write lock not release (bsc#1243112).\n- drm/xe/guc: Prepare GuC register list and update ADS size for error capture (stable-fixes).\n- ext4: fix checks for orphan inodes (bsc#1250119).\n- hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat() (git-fixes).\n- intel_idle: Provide the default enter_dead() handler (jsc#PED-13815).\n- intel_idle: Rescan 'dead' SMT siblings during initialization (jsc#PED-13815).\n- intel_idle: Use subsys_initcall_sync() for initialization (jsc#PED-13815).\n- ixgbe: handle IXGBE_VF_FEATURES_NEGOTIATE mbox cmd (bsc#1247222).\n- ixgbe: handle IXGBE_VF_GET_PF_LINK_STATE mailbox operation (bsc#1247222).\n- ixgbevf: fix getting link speed data for E610 devices (bsc#1247222).\n- ixgbevf: fix mailbox API compatibility by negotiating supported features (bsc#1247222).\n- kdb: Replace deprecated strcpy() with memmove() in vkdb_printf() (bsc#1252939).\n- module: Prevent silent truncation of module name in delete_module(2) (git-fixes).\n- net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency (bsc#1248754).\n- netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).\n- nvme-auth: update bi_directional flag (git-fixes bsc#1249735).\n- nvme-auth: update sc_c in host response (git-fixes bsc#1249397).\n- nvme-fc: use lock accessing port_state and rport state (bsc#1245193 bsc#1247500).\n- nvme-tcp: send only permitted commands for secure concat (git-fixes bsc#1247683).\n- nvmet-fc: avoid scheduling association deletion twice (bsc#1245193 bsc#1247500).\n- nvmet-fc: move lsop put work to nvmet_fc_ls_req_op (bsc#1245193 bsc#1247500).\n- nvmet-fcloop: call done callback even when remote port is gone (bsc#1245193 bsc#1247500).\n- perf/x86/intel: Allow to update user space GPRs from PEBS records (git-fixes).\n- perf/x86/intel: Fix crash in icl_update_topdown_event() (git-fixes).\n- phy: cadence: cdns-dphy: Update calibration wait time for startup state machine (git-fixes).\n- platform/x86/amd/pmc: Add 1Ah family series to STB support list (bsc#1243112).\n- platform/x86/amd/pmc: Add MECHREVO Yilong15Pro to spurious_8042 list (bsc#1243112).\n- platform/x86/amd/pmc: Add Stellaris Slim Gen6 AMD to spurious 8042 quirks list (bsc#1243112).\n- platform/x86/amd/pmc: Add VPE information for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Add idlemask support for 1Ah family (bsc#1243112).\n- platform/x86/amd/pmc: Extend support for PMC features on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Fix SMU command submission path on new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Modify SMU message port for latest AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Notify user when platform does not support s0ix transition (bsc#1243112).\n- platform/x86/amd/pmc: Remove unnecessary line breaks (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for AMDI000A platform (bsc#1243112).\n- platform/x86/amd/pmc: Send OS_HINT command for new AMD platform (bsc#1243112).\n- platform/x86/amd/pmc: Update IP information structure for newer SoCs (bsc#1243112).\n- platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information (bsc#1243112).\n- platform/x86/amd/pmc: call amd_pmc_get_ip_info() during driver probe (bsc#1243112).\n- platform/x86/amd: pmc: Add new ACPI ID AMDI000B (bsc#1243112).\n- platform/x86/amd: pmc: Drop SMU F/W match for Cezanne (bsc#1243112).\n- platform/x86/amd: pmc: Use guard(mutex) (bsc#1243112).\n- powerpc/boot: Fix build with gcc 15 (bsc#1215199).\n- powerpc/fadump: skip parameter area allocation when fadump is disabled (jsc#PED-9891 git-fixes).\n- powerpc/kvm: Fix ifdef to remove build warning (bsc#1215199).\n- powerpc/powernv/pci: Fix underflow and leak issue (bsc#1215199).\n- powerpc/pseries/msi: Fix potential underflow and leak issue (bsc#1215199).\n- powerpc: floppy: Add missing checks after DMA map (bsc#1215199).\n- proc: fix missing pde_set_flags() for net proc files (bsc#1248630)\n- proc: fix type confusion in pde_set_flags() (bsc#1248630)\n- sched/idle: Conditionally handle tick broadcast in default_idle_call() (bsc#1248517).\n- scsi: fc: Avoid -Wflex-array-member-not-at-end warnings (bsc#1250519).\n- scsi: lpfc: Abort outstanding ELS WQEs regardless of if rmmod is in progress (bsc#1250519).\n- scsi: lpfc: Check return status of lpfc_reset_flush_io_context during TGT_RESET (bsc#1250519).\n- scsi: lpfc: Clean up allocated queues when queue setup mbox commands fail (bsc#1250519).\n- scsi: lpfc: Copyright updates for 14.4.0.11 patches (bsc#1250519).\n- scsi: lpfc: Decrement ndlp kref after FDISC retries exhausted (bsc#1250519).\n- scsi: lpfc: Ensure PLOGI_ACC is sent prior to PRLI in Point to Point topology (bsc#1250519).\n- scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250519).\n- scsi: lpfc: Fix wrong function reference in a comment (bsc#1250519).\n- scsi: lpfc: Remove ndlp kref decrement clause for F_Port_Ctrl in lpfc_cleanup (bsc#1250519).\n- scsi: lpfc: Remove redundant assignment to avoid memory leak (bsc#1250519).\n- scsi: lpfc: Remove unused member variables in struct lpfc_hba and lpfc_vport (bsc#1250519).\n- scsi: lpfc: Update lpfc version to 14.4.0.11 (bsc#1250519).\n- scsi: lpfc: Use int type to store negative error codes (bsc#1250519).\n- scsi: lpfc: use min() to improve code (bsc#1250519).\n- serial: sc16is7xx: rename Kconfig CONFIG_SERIAL_SC16IS7XX_CORE (bsc#1252469)\n- skmsg: Return copied bytes in sk_msg_memcopy_from_iter (bsc#1250650).\n- smb: client: fix crypto buffers in non-linear memory (bsc#1250491, bsc#1239206).\n- smb: client: fix potential cfid UAF in smb2_query_info_compound (bsc#1248886).\n- tcp_bpf: Fix copied value in tcp_bpf_sendmsg (bsc#1250650).\n- tracing: Remove unneeded goto out logic (bsc#1249286).\n- x86/idle: Sanitize X86_BUG_AMD_E400 handling (bsc#1248517).\n- x86/resctrl: Fix miscount of bandwidth event when reactivating previously unavailable RMID (bsc#1252734).\n- x86/resctrl: Refactor resctrl_arch_rmid_read() (bsc#1252734).\n- x86/smp: Allow calling mwait_play_dead with an arbitrary hint (jsc#PED-13815).\n- x86/smp: Fix mwait_play_dead() and acpi_processor_ffh_play_dead() noreturn behavior (jsc#PED-13815).\n- x86/smp: PM/hibernate: Split arch_resume_nosmt() (jsc#PED-13815).\n- x86/topology: Implement topology_is_core_online() to address SMT regression (jsc#PED-13815).\n","status":"published","published":"2025-11-19T14:06:18Z","modified":"2026-03-23T04:50:23.099088Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"SUSE-SU-2025:4315-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 11 SP4 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50116: Update config files. Disable N_GSM (bsc#1244824 jsc#PED-8240).\n- CVE-2022-50252: igb: Do not free q_vector unless new one was allocated (bsc#1249846).\n- CVE-2022-50381: MD: add rdev reference for super write (bsc#1250257).\n- CVE-2022-50409: net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory (bsc#1250392).\n- CVE-2023-53282: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write (bsc#1250311).\n- CVE-2023-53322: scsi: qla2xxx: Wait for io return on terminate rport (bsc#1250323).\n- CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).\n- CVE-2023-53395: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer (bsc#1250358).\n- CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).\n- CVE-2023-53722: md: raid1: fix potential OOB in raid1_remove_disk() (bsc#1252499).\n- CVE-2025-38352: posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() (bsc#1246911).\n- CVE-2025-38498: do_change_type(): refuse to operate on unmounted/not ours mounts (bsc#1247374).\n- CVE-2025-38617: net/packet: fix a race in packet_set_ring() and packet_notifier() (bsc#1248621).\n- CVE-2025-38685: fbdev: Fix vmalloc out-of-bounds write in fast_imageblit (bsc#1249220).\n- CVE-2025-38713: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1249200).\n- CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).\n","status":"published","published":"2025-12-01T10:12:39Z","modified":"2026-02-04T02:31:38.423255Z","updated_at":"2026-11-02T15:54:00.344164Z"},{"id":"USN-7909-1","title":"linux, linux-aws, linux-aws-5.15, linux-gcp-5.15, linux-hwe-5.15, linux-ibm, linux-ibm-5.15, linux-intel-iotg, linux-intel-iotg-5.15, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-nvidia-tegra, linux-nvidia-tegra-5.15, linux-nvidia-tegra-igx, linux-oracle, linux-oracle-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  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38683, CVE-2025-38684, CVE-2025-38685, CVE-2025-38687,\nCVE-2025-38691, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38711, CVE-2025-38712, CVE-2025-38713,\nCVE-2025-38714, CVE-2025-38715, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38729, CVE-2025-38732,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39693,\nCVE-2025-39697, CVE-2025-39702, CVE-2025-39703, CVE-2025-39709,\nCVE-2025-39710, CVE-2025-39713, CVE-2025-39714, CVE-2025-39724,\nCVE-2025-39730, CVE-2025-39734, CVE-2025-39736, CVE-2025-39737,\nCVE-2025-39738, CVE-2025-39742, CVE-2025-39743, CVE-2025-39749,\nCVE-2025-39752, CVE-2025-39756, CVE-2025-39757, CVE-2025-39760,\nCVE-2025-39766, CVE-2025-39772, CVE-2025-39773, CVE-2025-39776,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39798,\nCVE-2025-39801, CVE-2025-39806, CVE-2025-39808, CVE-2025-39812,\nCVE-2025-39813, CVE-2025-39817, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39828, CVE-2025-39835, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39853, CVE-2025-39860, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39902, CVE-2025-39920)\n","status":"published","published":"2025-12-04T09:26:45Z","modified":"2026-11-03T14:38:19.626869904Z","updated_at":"2026-11-03T15:14:17.286738Z"},{"id":"USN-7909-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  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38683, CVE-2025-38684, CVE-2025-38685, CVE-2025-38687,\nCVE-2025-38691, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38711, CVE-2025-38712, CVE-2025-38713,\nCVE-2025-38714, CVE-2025-38715, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38729, CVE-2025-38732,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39693,\nCVE-2025-39697, CVE-2025-39702, CVE-2025-39703, CVE-2025-39709,\nCVE-2025-39710, CVE-2025-39713, CVE-2025-39714, CVE-2025-39724,\nCVE-2025-39730, CVE-2025-39734, CVE-2025-39736, CVE-2025-39737,\nCVE-2025-39738, CVE-2025-39742, CVE-2025-39743, CVE-2025-39749,\nCVE-2025-39752, CVE-2025-39756, CVE-2025-39757, CVE-2025-39760,\nCVE-2025-39766, CVE-2025-39772, CVE-2025-39773, CVE-2025-39776,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39798,\nCVE-2025-39801, CVE-2025-39806, CVE-2025-39808, CVE-2025-39812,\nCVE-2025-39813, CVE-2025-39817, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39828, CVE-2025-39835, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39853, CVE-2025-39860, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39902, CVE-2025-39920)\n","status":"published","published":"2025-12-04T11:03:24Z","modified":"2026-11-03T14:34:07.756711944Z","updated_at":"2026-11-03T15:17:11.325641Z"},{"id":"USN-7909-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  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38683, CVE-2025-38684, CVE-2025-38685, CVE-2025-38687,\nCVE-2025-38691, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38711, CVE-2025-38712, CVE-2025-38713,\nCVE-2025-38714, CVE-2025-38715, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38729, CVE-2025-38732,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39693,\nCVE-2025-39697, CVE-2025-39702, CVE-2025-39703, CVE-2025-39709,\nCVE-2025-39710, CVE-2025-39713, CVE-2025-39714, CVE-2025-39724,\nCVE-2025-39730, CVE-2025-39734, CVE-2025-39736, CVE-2025-39737,\nCVE-2025-39738, CVE-2025-39742, CVE-2025-39743, CVE-2025-39749,\nCVE-2025-39752, CVE-2025-39756, CVE-2025-39757, CVE-2025-39760,\nCVE-2025-39766, CVE-2025-39772, CVE-2025-39773, CVE-2025-39776,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39798,\nCVE-2025-39801, CVE-2025-39806, CVE-2025-39808, CVE-2025-39812,\nCVE-2025-39813, CVE-2025-39817, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39828, CVE-2025-39835, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39853, CVE-2025-39860, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39902, CVE-2025-39920)\n","status":"published","published":"2025-12-04T11:14:34Z","modified":"2026-11-03T14:34:26.704598742Z","updated_at":"2026-11-03T15:16:59.562266Z"},{"id":"USN-7909-4","title":"linux-gcp, linux-gke, linux-gkeop 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  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38683, CVE-2025-38684, CVE-2025-38685, CVE-2025-38687,\nCVE-2025-38691, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38711, CVE-2025-38712, CVE-2025-38713,\nCVE-2025-38714, CVE-2025-38715, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38729, CVE-2025-38732,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39693,\nCVE-2025-39697, CVE-2025-39702, CVE-2025-39703, CVE-2025-39709,\nCVE-2025-39710, CVE-2025-39713, CVE-2025-39714, CVE-2025-39724,\nCVE-2025-39730, CVE-2025-39734, CVE-2025-39736, CVE-2025-39737,\nCVE-2025-39738, CVE-2025-39742, CVE-2025-39743, CVE-2025-39749,\nCVE-2025-39752, CVE-2025-39756, CVE-2025-39757, CVE-2025-39760,\nCVE-2025-39766, CVE-2025-39772, CVE-2025-39773, CVE-2025-39776,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39798,\nCVE-2025-39801, CVE-2025-39806, CVE-2025-39808, CVE-2025-39812,\nCVE-2025-39813, CVE-2025-39817, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39828, CVE-2025-39835, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39853, CVE-2025-39860, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39902, CVE-2025-39920)\n","status":"published","published":"2025-12-05T10:51:05Z","modified":"2026-11-03T14:34:24.38440229Z","updated_at":"2026-11-03T15:17:04.783338Z"},{"id":"USN-7909-5","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38683, CVE-2025-38684, CVE-2025-38685, CVE-2025-38687,\nCVE-2025-38691, CVE-2025-38693, CVE-2025-38694, CVE-2025-38695,\nCVE-2025-38696, CVE-2025-38697, CVE-2025-38698, CVE-2025-38699,\nCVE-2025-38700, CVE-2025-38701, CVE-2025-38706, CVE-2025-38707,\nCVE-2025-38708, CVE-2025-38711, CVE-2025-38712, CVE-2025-38713,\nCVE-2025-38714, CVE-2025-38715, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38724, CVE-2025-38725, CVE-2025-38729, CVE-2025-38732,\nCVE-2025-39673, CVE-2025-39675, CVE-2025-39676, CVE-2025-39681,\nCVE-2025-39683, CVE-2025-39684, CVE-2025-39685, CVE-2025-39686,\nCVE-2025-39687, CVE-2025-39689, CVE-2025-39691, CVE-2025-39693,\nCVE-2025-39697, CVE-2025-39702, CVE-2025-39703, CVE-2025-39709,\nCVE-2025-39710, CVE-2025-39713, CVE-2025-39714, CVE-2025-39724,\nCVE-2025-39730, CVE-2025-39734, CVE-2025-39736, CVE-2025-39737,\nCVE-2025-39738, CVE-2025-39742, CVE-2025-39743, CVE-2025-39749,\nCVE-2025-39752, CVE-2025-39756, CVE-2025-39757, CVE-2025-39760,\nCVE-2025-39766, CVE-2025-39772, CVE-2025-39773, CVE-2025-39776,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39798,\nCVE-2025-39801, CVE-2025-39806, CVE-2025-39808, CVE-2025-39812,\nCVE-2025-39813, CVE-2025-39817, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39828, CVE-2025-39835, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39853, CVE-2025-39860, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39902, CVE-2025-39920)\n","status":"published","published":"2025-12-15T17:04:41Z","modified":"2026-11-03T14:34:08.73328788Z","updated_at":"2026-11-03T15:17:11.325641Z"},{"id":"USN-7910-1","title":"linux-azure-fips vulnerabilities","description":"Jean-Claude Graf, Sandro Rüegge, Ali Hajiabadi, and Kaveh Razavi discovered\nthat the Linux kernel contained insufficient branch predictor isolation\nbetween a guest and a userspace hypervisor for certain processors. This\nflaw is known as VMSCAPE. An attacker in a guest VM could possibly use this\nto expose sensitive information from the host OS. (CVE-2025-40300)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38687, CVE-2025-38691,\nCVE-2025-38693, CVE-2025-38694, CVE-2025-38695, CVE-2025-38696,\nCVE-2025-38697, CVE-2025-38698, CVE-2025-38699, CVE-2025-38700,\nCVE-2025-38701, CVE-2025-38706, CVE-2025-38707, CVE-2025-38708,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38718, CVE-2025-38721, CVE-2025-38724,\nCVE-2025-38725, CVE-2025-38729, CVE-2025-38732, CVE-2025-39673,\nCVE-2025-39675, CVE-2025-39676, 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-39693, CVE-2025-39697,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39713, CVE-2025-39714, CVE-2025-39724, CVE-2025-39730,\nCVE-2025-39734, CVE-2025-39736, CVE-2025-39737, CVE-2025-39738,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39749, CVE-2025-39752,\nCVE-2025-39756, CVE-2025-39757, CVE-2025-39760, CVE-2025-39766,\nCVE-2025-39772, CVE-2025-39773, CVE-2025-39776, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39798, CVE-2025-39801,\nCVE-2025-39806, CVE-2025-39808, CVE-2025-39812, CVE-2025-39813,\nCVE-2025-39817, CVE-2025-39823, CVE-2025-39824, CVE-2025-39828,\nCVE-2025-39835, CVE-2025-39839, CVE-2025-39841, CVE-2025-39844,\nCVE-2025-39845, CVE-2025-39846, CVE-2025-39847, CVE-2025-39848,\nCVE-2025-39853, CVE-2025-39860, CVE-2025-39864, CVE-2025-39865,\nCVE-2025-39866, CVE-2025-39891, CVE-2025-39894, CVE-2025-39902,\nCVE-2025-39920)\n","status":"published","published":"2025-12-04T11:23:32Z","modified":"2026-11-03T14:34:06.747266014Z","updated_at":"2026-11-03T15:17:11.325641Z"},{"id":"USN-7910-2","title":"linux-azure vulnerabilities","description":"Jean-Claude Graf, Sandro Rüegge, Ali Hajiabadi, and Kaveh Razavi discovered\nthat the Linux kernel contained insufficient branch predictor isolation\nbetween a guest and a userspace hypervisor for certain processors. This\nflaw is known as VMSCAPE. An attacker in a guest VM could possibly use this\nto expose sensitive information from the host OS. (CVE-2025-40300)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52935, CVE-2023-53074,\nCVE-2024-50061, CVE-2024-53068, CVE-2025-37925, CVE-2025-37968,\nCVE-2025-38095, CVE-2025-38148, CVE-2025-38165, CVE-2025-38335,\nCVE-2025-38347, CVE-2025-38468, CVE-2025-38470, CVE-2025-38473,\nCVE-2025-38474, CVE-2025-38476, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38630, CVE-2025-38634,\nCVE-2025-38635, CVE-2025-38639, CVE-2025-38645, CVE-2025-38650,\nCVE-2025-38652, CVE-2025-38663, CVE-2025-38664, CVE-2025-38666,\nCVE-2025-38668, CVE-2025-38670, CVE-2025-38671, CVE-2025-38676,\nCVE-2025-38677, CVE-2025-38678, CVE-2025-38680, CVE-2025-38681,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38687, CVE-2025-38691,\nCVE-2025-38693, CVE-2025-38694, CVE-2025-38695, CVE-2025-38696,\nCVE-2025-38697, CVE-2025-38698, CVE-2025-38699, CVE-2025-38700,\nCVE-2025-38701, CVE-2025-38706, CVE-2025-38707, CVE-2025-38708,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38718, CVE-2025-38721, CVE-2025-38724,\nCVE-2025-38725, CVE-2025-38729, CVE-2025-38732, CVE-2025-39673,\nCVE-2025-39675, CVE-2025-39676, 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-39693, CVE-2025-39697,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39713, CVE-2025-39714, CVE-2025-39724, CVE-2025-39730,\nCVE-2025-39734, CVE-2025-39736, CVE-2025-39737, CVE-2025-39738,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39749, CVE-2025-39752,\nCVE-2025-39756, CVE-2025-39757, CVE-2025-39760, CVE-2025-39766,\nCVE-2025-39772, CVE-2025-39773, CVE-2025-39776, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39798, CVE-2025-39801,\nCVE-2025-39806, CVE-2025-39808, CVE-2025-39812, CVE-2025-39813,\nCVE-2025-39817, CVE-2025-39823, CVE-2025-39824, CVE-2025-39828,\nCVE-2025-39835, CVE-2025-39839, CVE-2025-39841, CVE-2025-39844,\nCVE-2025-39845, CVE-2025-39846, CVE-2025-39847, CVE-2025-39848,\nCVE-2025-39853, CVE-2025-39860, CVE-2025-39864, CVE-2025-39865,\nCVE-2025-39866, CVE-2025-39891, CVE-2025-39894, CVE-2025-39902,\nCVE-2025-39920)\n","status":"published","published":"2025-12-05T10:59:35Z","modified":"2026-11-03T14:34:07.490233902Z","updated_at":"2026-11-03T15:17:11.325641Z"},{"id":"USN-7933-1","title":"linux-kvm vulnerabilities","description":"\nJean-Claude Graf, Sandro Rüegge, Ali Hajiabadi, and Kaveh Razavi discovered\nthat the Linux kernel contained insufficient branch predictor isolation\nbetween a guest and a userspace hypervisor for certain processors. This\nflaw is known as VMSCAPE. An attacker in a guest VM could possibly use this\nto expose sensitive information from the host OS. (CVE-2025-40300)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Netlink;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-50070, CVE-2022-50327, CVE-2023-52593, CVE-2023-52935,\nCVE-2023-53074, CVE-2024-26700, CVE-2024-26896, CVE-2024-50061,\nCVE-2024-53068, CVE-2025-37925, CVE-2025-37968, CVE-2025-38095,\nCVE-2025-38148, CVE-2025-38165, CVE-2025-38335, CVE-2025-38347,\nCVE-2025-38468, CVE-2025-38470, CVE-2025-38473, CVE-2025-38474,\nCVE-2025-38476, CVE-2025-38477, CVE-2025-38478, CVE-2025-38480,\nCVE-2025-38481, CVE-2025-38482, CVE-2025-38483, CVE-2025-38487,\nCVE-2025-38488, CVE-2025-38494, CVE-2025-38495, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38502, CVE-2025-38527, CVE-2025-38528,\nCVE-2025-38529, CVE-2025-38530, CVE-2025-38535, CVE-2025-38538,\nCVE-2025-38539, CVE-2025-38548, CVE-2025-38550, CVE-2025-38553,\nCVE-2025-38555, CVE-2025-38563, CVE-2025-38565, CVE-2025-38569,\nCVE-2025-38572, CVE-2025-38574, CVE-2025-38576, CVE-2025-38577,\nCVE-2025-38578, CVE-2025-38579, CVE-2025-38581, CVE-2025-38583,\nCVE-2025-38601, CVE-2025-38602, CVE-2025-38604, CVE-2025-38608,\nCVE-2025-38609, CVE-2025-38612, CVE-2025-38614, CVE-2025-38617,\nCVE-2025-38618, CVE-2025-38622, CVE-2025-38623, CVE-2025-38624,\nCVE-2025-38630, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38645, CVE-2025-38650, CVE-2025-38652, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38666, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38676, CVE-2025-38677, CVE-2025-38678,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38683, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38687, CVE-2025-38691, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38711,\nCVE-2025-38712, CVE-2025-38713, CVE-2025-38714, CVE-2025-38715,\nCVE-2025-38718, CVE-2025-38721, CVE-2025-38724, CVE-2025-38725,\nCVE-2025-38727, CVE-2025-38729, CVE-2025-38732, CVE-2025-39673,\nCVE-2025-39675, CVE-2025-39676, 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-39693, CVE-2025-39697,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39713, CVE-2025-39714, CVE-2025-39724, CVE-2025-39730,\nCVE-2025-39734, CVE-2025-39736, CVE-2025-39737, CVE-2025-39738,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39749, CVE-2025-39752,\nCVE-2025-39756, CVE-2025-39757, CVE-2025-39760, CVE-2025-39766,\nCVE-2025-39772, CVE-2025-39773, CVE-2025-39776, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39798, CVE-2025-39801,\nCVE-2025-39806, CVE-2025-39808, CVE-2025-39812, CVE-2025-39813,\nCVE-2025-39817, CVE-2025-39823, CVE-2025-39824, CVE-2025-39828,\nCVE-2025-39835, CVE-2025-39839, CVE-2025-39841, CVE-2025-39844,\nCVE-2025-39845, CVE-2025-39846, CVE-2025-39847, CVE-2025-39848,\nCVE-2025-39853, CVE-2025-39860, CVE-2025-39864, CVE-2025-39865,\nCVE-2025-39866, CVE-2025-39891, CVE-2025-39894, CVE-2025-39902,\nCVE-2025-39920)\n","status":"published","published":"2025-12-15T17:01:57Z","modified":"2026-11-03T14:34:22.157562269Z","updated_at":"2026-11-03T15:17:04.783338Z"},{"id":"USN-7938-1","title":"linux-azure-5.15 vulnerabilities","description":"\nJean-Claude Graf, Sandro Rüegge, Ali Hajiabadi, and Kaveh Razavi discovered\nthat the Linux kernel contained insufficient branch predictor isolation\nbetween a guest and a userspace hypervisor for certain processors. This\nflaw is known as VMSCAPE. An attacker in a guest VM could possibly use this\nto expose sensitive information from the host OS. (CVE-2025-40300)\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  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Bus devices;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - PHY drivers;\n  - Power supply drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - small TFT LCD display modules;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - Framebuffer layer;\n  - AFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Networking subsytem;\n  - UDP network protocol;\n  - Perf events;\n  - RCU subsystem;\n  - Tracing infrastructure;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - Networking core;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Wireless networking;\n  - SoC audio core drivers;\n  - USB sound devices;\n(CVE-2022-49390, CVE-2022-50070, CVE-2022-50327, CVE-2023-52935,\nCVE-2023-53074, CVE-2024-47691, CVE-2024-50061, CVE-2024-50067,\nCVE-2024-53068, CVE-2024-53090, CVE-2024-53218, CVE-2025-21855,\nCVE-2025-37925, CVE-2025-37968, CVE-2025-38095, CVE-2025-38148,\nCVE-2025-38165, CVE-2025-38335, CVE-2025-38347, CVE-2025-38468,\nCVE-2025-38470, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38487, CVE-2025-38488, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38497, CVE-2025-38499, CVE-2025-38502,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38535, CVE-2025-38538, CVE-2025-38539, CVE-2025-38548,\nCVE-2025-38550, CVE-2025-38553, CVE-2025-38555, CVE-2025-38563,\nCVE-2025-38565, CVE-2025-38569, CVE-2025-38572, CVE-2025-38574,\nCVE-2025-38576, CVE-2025-38577, CVE-2025-38578, CVE-2025-38579,\nCVE-2025-38581, CVE-2025-38583, CVE-2025-38601, CVE-2025-38602,\nCVE-2025-38604, CVE-2025-38608, CVE-2025-38609, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38622, CVE-2025-38623, CVE-2025-38624,\nCVE-2025-38630, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38645, CVE-2025-38650, CVE-2025-38652, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38666, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38676, CVE-2025-38677, CVE-2025-38678,\nCVE-2025-38680, CVE-2025-38681, CVE-2025-38684, CVE-2025-38685,\nCVE-2025-38687, CVE-2025-38691, 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-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38711, CVE-2025-38712,\nCVE-2025-38713, CVE-2025-38714, CVE-2025-38715, CVE-2025-38718,\nCVE-2025-38721, CVE-2025-38724, CVE-2025-38725, CVE-2025-38729,\nCVE-2025-38732, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39681, CVE-2025-39683, CVE-2025-39684, CVE-2025-39685,\nCVE-2025-39686, CVE-2025-39687, CVE-2025-39689, CVE-2025-39691,\nCVE-2025-39693, CVE-2025-39697, CVE-2025-39702, CVE-2025-39703,\nCVE-2025-39709, CVE-2025-39710, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39724, CVE-2025-39730, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39742, CVE-2025-39743,\nCVE-2025-39749, CVE-2025-39752, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39760, CVE-2025-39766, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39782, CVE-2025-39783, CVE-2025-39787,\nCVE-2025-39788, CVE-2025-39790, CVE-2025-39794, CVE-2025-39795,\nCVE-2025-39798, CVE-2025-39801, CVE-2025-39806, CVE-2025-39808,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39817, CVE-2025-39823,\nCVE-2025-39824, CVE-2025-39828, CVE-2025-39835, CVE-2025-39839,\nCVE-2025-39841, CVE-2025-39844, CVE-2025-39845, CVE-2025-39846,\nCVE-2025-39847, CVE-2025-39848, CVE-2025-39853, CVE-2025-39860,\nCVE-2025-39864, CVE-2025-39865, CVE-2025-39866, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39902, CVE-2025-39920, CVE-2025-39964,\nCVE-2025-39993, CVE-2025-40018)\n","status":"published","published":"2025-12-16T14:52:44Z","modified":"2026-11-03T14:34:23.527664966Z","updated_at":"2026-11-03T15:17:04.783338Z"},{"id":"USN-8028-1","title":"linux, linux-raspi vulnerabilities","description":"\nIt was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-11T16:39:10Z","modified":"2026-11-03T14:34:46.341804014Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8028-2","title":"linux-realtime-6.8 vulnerabilities","description":"It was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Amlogic Meson DDR PMU;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - Overlay file system;\n  - Proc file system;\n  - SMB network file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - padata parallel execution mechanism;\n  - Networking subsytem;\n  - Bluetooth subsystem;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Maple Tree data structure library;\n  - Memory management;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Networking core;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21884, CVE-2025-21931, CVE-2025-22026, CVE-2025-22101,\nCVE-2025-22102, CVE-2025-22115, CVE-2025-22120, CVE-2025-22126,\nCVE-2025-22128, CVE-2025-23140, CVE-2025-23141, CVE-2025-23142,\nCVE-2025-23144, CVE-2025-23145, CVE-2025-23146, CVE-2025-23147,\nCVE-2025-23148, CVE-2025-23149, CVE-2025-23150, CVE-2025-23151,\nCVE-2025-23155, CVE-2025-23156, CVE-2025-23157, CVE-2025-23158,\nCVE-2025-23159, CVE-2025-23160, CVE-2025-23161, CVE-2025-23163,\nCVE-2025-37738, CVE-2025-37739, CVE-2025-37740, CVE-2025-37741,\nCVE-2025-37742, CVE-2025-37744, CVE-2025-37745, CVE-2025-37748,\nCVE-2025-37749, CVE-2025-37754, CVE-2025-37755, CVE-2025-37757,\nCVE-2025-37758, CVE-2025-37759, CVE-2025-37761, CVE-2025-37763,\nCVE-2025-37764, CVE-2025-37765, CVE-2025-37766, CVE-2025-37767,\nCVE-2025-37768, CVE-2025-37769, CVE-2025-37770, CVE-2025-37771,\nCVE-2025-37772, CVE-2025-37773, CVE-2025-37775, CVE-2025-37777,\nCVE-2025-37778, CVE-2025-37780, CVE-2025-37781, CVE-2025-37784,\nCVE-2025-37786, CVE-2025-37787, CVE-2025-37788, CVE-2025-37789,\nCVE-2025-37790, CVE-2025-37792, CVE-2025-37793, CVE-2025-37794,\nCVE-2025-37796, CVE-2025-37799, CVE-2025-37800, CVE-2025-37801,\nCVE-2025-37803, CVE-2025-37805, CVE-2025-37808, CVE-2025-37809,\nCVE-2025-37810, CVE-2025-37811, CVE-2025-37812, CVE-2025-37813,\nCVE-2025-37815, CVE-2025-37816, CVE-2025-37817, CVE-2025-37819,\nCVE-2025-37820, CVE-2025-37822, CVE-2025-37823, CVE-2025-37824,\nCVE-2025-37826, CVE-2025-37827, CVE-2025-37828, CVE-2025-37829,\nCVE-2025-37830, CVE-2025-37831, CVE-2025-37836, CVE-2025-37839,\nCVE-2025-37840, CVE-2025-37841, CVE-2025-37842, CVE-2025-37844,\nCVE-2025-37846, CVE-2025-37849, CVE-2025-37850, CVE-2025-37851,\nCVE-2025-37852, CVE-2025-37853, CVE-2025-37854, CVE-2025-37856,\nCVE-2025-37857, CVE-2025-37858, CVE-2025-37859, CVE-2025-37861,\nCVE-2025-37862, CVE-2025-37863, CVE-2025-37864, CVE-2025-37865,\nCVE-2025-37867, CVE-2025-37869, CVE-2025-37871, CVE-2025-37872,\nCVE-2025-37873, CVE-2025-37874, CVE-2025-37875, CVE-2025-37878,\nCVE-2025-37879, CVE-2025-37881, CVE-2025-37883, CVE-2025-37884,\nCVE-2025-37885, CVE-2025-37886, CVE-2025-37887, CVE-2025-37891,\nCVE-2025-37892, CVE-2025-37897, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37954, CVE-2025-37956,\nCVE-2025-37957, CVE-2025-37959, CVE-2025-37960, CVE-2025-37961,\nCVE-2025-37962, CVE-2025-37963, CVE-2025-37967, CVE-2025-37968,\nCVE-2025-37969, CVE-2025-37970, CVE-2025-37972, CVE-2025-37973,\nCVE-2025-37975, CVE-2025-37977, CVE-2025-37978, CVE-2025-37979,\nCVE-2025-37980, CVE-2025-37982, CVE-2025-37983, CVE-2025-37984,\nCVE-2025-37985, CVE-2025-37986, CVE-2025-37987, CVE-2025-37988,\nCVE-2025-37989, CVE-2025-37990, CVE-2025-37991, CVE-2025-37992,\nCVE-2025-37994, CVE-2025-37995, CVE-2025-37998, CVE-2025-38003,\nCVE-2025-38004, CVE-2025-38005, CVE-2025-38006, CVE-2025-38007,\nCVE-2025-38008, CVE-2025-38009, CVE-2025-38010, CVE-2025-38011,\nCVE-2025-38013, CVE-2025-38014, CVE-2025-38015, CVE-2025-38018,\nCVE-2025-38019, CVE-2025-38020, CVE-2025-38023, CVE-2025-38024,\nCVE-2025-38027, CVE-2025-38031, CVE-2025-38034, CVE-2025-38035,\nCVE-2025-38037, CVE-2025-38039, CVE-2025-38040, CVE-2025-38043,\nCVE-2025-38044, CVE-2025-38045, CVE-2025-38048, CVE-2025-38051,\nCVE-2025-38052, CVE-2025-38053, CVE-2025-38055, CVE-2025-38057,\nCVE-2025-38058, CVE-2025-38059, CVE-2025-38060, CVE-2025-38061,\nCVE-2025-38062, CVE-2025-38063, CVE-2025-38065, CVE-2025-38066,\nCVE-2025-38067, CVE-2025-38068, CVE-2025-38071, CVE-2025-38072,\nCVE-2025-38074, CVE-2025-38075, CVE-2025-38077, CVE-2025-38078,\nCVE-2025-38079, CVE-2025-38080, CVE-2025-38081, CVE-2025-38084,\nCVE-2025-38085, CVE-2025-38086, CVE-2025-38087, CVE-2025-38088,\nCVE-2025-38089, CVE-2025-38090, CVE-2025-38094, CVE-2025-38095,\nCVE-2025-38097, CVE-2025-38098, CVE-2025-38099, CVE-2025-38100,\nCVE-2025-38101, CVE-2025-38102, CVE-2025-38103, CVE-2025-38104,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38244, CVE-2025-38245,\nCVE-2025-38246, CVE-2025-38248, CVE-2025-38249, CVE-2025-38250,\nCVE-2025-38251, CVE-2025-38253, CVE-2025-38255, CVE-2025-38257,\nCVE-2025-38258, CVE-2025-38259, CVE-2025-38260, CVE-2025-38262,\nCVE-2025-38263, CVE-2025-38264, CVE-2025-38265, CVE-2025-38269,\nCVE-2025-38274, CVE-2025-38275, CVE-2025-38277, CVE-2025-38278,\nCVE-2025-38279, CVE-2025-38280, CVE-2025-38282, CVE-2025-38283,\nCVE-2025-38285, CVE-2025-38286, CVE-2025-38289, CVE-2025-38290,\nCVE-2025-38292, CVE-2025-38293, CVE-2025-38295, CVE-2025-38298,\nCVE-2025-38299, CVE-2025-38300, CVE-2025-38303, CVE-2025-38304,\nCVE-2025-38305, CVE-2025-38307, CVE-2025-38310, CVE-2025-38312,\nCVE-2025-38313, CVE-2025-38319, CVE-2025-38320, CVE-2025-38321,\nCVE-2025-38322, CVE-2025-38323, CVE-2025-38324, CVE-2025-38326,\nCVE-2025-38328, CVE-2025-38331, CVE-2025-38332, CVE-2025-38333,\nCVE-2025-38334, CVE-2025-38335, CVE-2025-38336, CVE-2025-38337,\nCVE-2025-38338, CVE-2025-38342, CVE-2025-38343, CVE-2025-38344,\nCVE-2025-38345, CVE-2025-38346, CVE-2025-38347, CVE-2025-38348,\nCVE-2025-38349, CVE-2025-38351, CVE-2025-38354, CVE-2025-38361,\nCVE-2025-38362, CVE-2025-38363, CVE-2025-38364, CVE-2025-38365,\nCVE-2025-38368, CVE-2025-38369, CVE-2025-38371, CVE-2025-38373,\nCVE-2025-38374, CVE-2025-38375, CVE-2025-38376, CVE-2025-38377,\nCVE-2025-38382, CVE-2025-38384, CVE-2025-38385, CVE-2025-38386,\nCVE-2025-38387, CVE-2025-38388, CVE-2025-38389, CVE-2025-38390,\nCVE-2025-38391, CVE-2025-38392, CVE-2025-38393, CVE-2025-38395,\nCVE-2025-38396, CVE-2025-38399, CVE-2025-38400, CVE-2025-38401,\nCVE-2025-38402, CVE-2025-38403, CVE-2025-38405, CVE-2025-38406,\nCVE-2025-38407, CVE-2025-38408, CVE-2025-38409, CVE-2025-38410,\nCVE-2025-38412, CVE-2025-38414, CVE-2025-38415, CVE-2025-38416,\nCVE-2025-38418, CVE-2025-38419, CVE-2025-38420, CVE-2025-38422,\nCVE-2025-38424, CVE-2025-38425, CVE-2025-38427, CVE-2025-38428,\nCVE-2025-38429, CVE-2025-38430, CVE-2025-38436, CVE-2025-38437,\nCVE-2025-38439, CVE-2025-38441, CVE-2025-38443, CVE-2025-38444,\nCVE-2025-38445, CVE-2025-38448, CVE-2025-38449, CVE-2025-38455,\nCVE-2025-38456, CVE-2025-38457, CVE-2025-38458, CVE-2025-38459,\nCVE-2025-38460, CVE-2025-38461, CVE-2025-38462, CVE-2025-38463,\nCVE-2025-38464, CVE-2025-38465, CVE-2025-38466, CVE-2025-38467,\nCVE-2025-38468, CVE-2025-38469, CVE-2025-38470, CVE-2025-38471,\nCVE-2025-38472, CVE-2025-38473, CVE-2025-38474, CVE-2025-38476,\nCVE-2025-38478, CVE-2025-38480, CVE-2025-38481, CVE-2025-38482,\nCVE-2025-38483, CVE-2025-38485, CVE-2025-38487, CVE-2025-38488,\nCVE-2025-38489, CVE-2025-38490, CVE-2025-38491, CVE-2025-38493,\nCVE-2025-38494, CVE-2025-38495, CVE-2025-38496, CVE-2025-38497,\nCVE-2025-38499, CVE-2025-38501, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38560,\nCVE-2025-38562, CVE-2025-38566, CVE-2025-38568, CVE-2025-38569,\nCVE-2025-38571, CVE-2025-38572, CVE-2025-38574, CVE-2025-38576,\nCVE-2025-38577, CVE-2025-38578, CVE-2025-38579, CVE-2025-38581,\nCVE-2025-38582, CVE-2025-38583, CVE-2025-38584, CVE-2025-38585,\nCVE-2025-38587, CVE-2025-38588, CVE-2025-38590, CVE-2025-38593,\nCVE-2025-38595, CVE-2025-38601, CVE-2025-38602, CVE-2025-38604,\nCVE-2025-38608, CVE-2025-38609, CVE-2025-38610, CVE-2025-38612,\nCVE-2025-38614, CVE-2025-38615, CVE-2025-38619, CVE-2025-38622,\nCVE-2025-38623, CVE-2025-38624, CVE-2025-38625, CVE-2025-38626,\nCVE-2025-38630, CVE-2025-38632, CVE-2025-38634, CVE-2025-38635,\nCVE-2025-38639, CVE-2025-38640, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38683,\nCVE-2025-38684, CVE-2025-38685, CVE-2025-38686, CVE-2025-38687,\nCVE-2025-38688, CVE-2025-38691, CVE-2025-38692, CVE-2025-38693,\nCVE-2025-38694, CVE-2025-38695, CVE-2025-38696, CVE-2025-38697,\nCVE-2025-38698, CVE-2025-38699, CVE-2025-38700, CVE-2025-38701,\nCVE-2025-38702, CVE-2025-38703, CVE-2025-38704, CVE-2025-38705,\nCVE-2025-38706, CVE-2025-38707, CVE-2025-38708, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39679, CVE-2025-39681, CVE-2025-39683, CVE-2025-39684,\nCVE-2025-39685, CVE-2025-39686, CVE-2025-39687, CVE-2025-39689,\nCVE-2025-39691, CVE-2025-39692, CVE-2025-39693, CVE-2025-39694,\nCVE-2025-39701, CVE-2025-39702, CVE-2025-39703, CVE-2025-39705,\nCVE-2025-39706, CVE-2025-39707, CVE-2025-39709, CVE-2025-39710,\nCVE-2025-39711, CVE-2025-39712, CVE-2025-39713, CVE-2025-39714,\nCVE-2025-39715, CVE-2025-39716, CVE-2025-39718, CVE-2025-39719,\nCVE-2025-39720, CVE-2025-39721, CVE-2025-39724, CVE-2025-39726,\nCVE-2025-39730, CVE-2025-39731, CVE-2025-39732, CVE-2025-39734,\nCVE-2025-39736, CVE-2025-39737, CVE-2025-39738, CVE-2025-39739,\nCVE-2025-39742, CVE-2025-39743, CVE-2025-39744, CVE-2025-39746,\nCVE-2025-39747, CVE-2025-39748, CVE-2025-39749, CVE-2025-39750,\nCVE-2025-39752, CVE-2025-39753, CVE-2025-39756, CVE-2025-39757,\nCVE-2025-39758, CVE-2025-39759, CVE-2025-39760, CVE-2025-39761,\nCVE-2025-39763, CVE-2025-39766, CVE-2025-39770, CVE-2025-39772,\nCVE-2025-39773, CVE-2025-39776, CVE-2025-39779, CVE-2025-39781,\nCVE-2025-39782, CVE-2025-39783, CVE-2025-39787, CVE-2025-39788,\nCVE-2025-39790, CVE-2025-39794, CVE-2025-39795, CVE-2025-39797,\nCVE-2025-39798, CVE-2025-39800, CVE-2025-39801, CVE-2025-39889,\nCVE-2025-39890, CVE-2025-39946, CVE-2025-39989, CVE-2025-40215,\nCVE-2025-40297, CVE-2025-68750)\n","status":"published","published":"2026-02-12T09:57:11Z","modified":"2026-11-03T14:34:35.34044986Z","updated_at":"2026-11-03T15:16:59.562266Z"}]},"sources_more":{"osv":14}}